Changeset 1061


Ignore:
Timestamp:
Aug 6, 2012 3:53:09 PM (11 years ago)
Author:
jemian
Message:

checkpoint

Location:
cssboy_deployment/docs/source
Files:
3 edited

Legend:

Unmodified
Added
Removed

  • cssboy_deployment/docs/source/configure.rst

    r1060 r1061  
    1212   
    1313       ./css &
    14    
     14
     15The remainder of this page assumes you are running CSS-BOY.
    1516
    1617Workspace
    … …  
    3738===================================
    3839
    39 
    40 :index:`color.def` file
    41 ===========================================================
    42 
    43 
    44 :index:`fonts.def` file
    45 ===========================================================
     40Add the OPI screens from synApps as a CSS project.
     41   
     42#. Select menu ``File-->Import ...``
     43#. Open ``General`` category,
     44   select ``Existing Projects into Workspace``,
     45   click ``Next`` button
     46#. Click ``Browse ...`` button (in *Import* window)
     47#. navigate to ``/APSshare/epics/synApps_5_6/support/``
     48   (or ``/usr/local/epics/synAppsSVN/support/`` or wherever)
     49#. Click ``Ok`` button
     50#. Click ``Finish`` button (in *Import* window)
     51
     52.. _synApps.project.file:
     53
     54Identify synApps as a *Project*
     55-----------------------------------
     56
     57If CSS reports that your synApps directory cannot be imported
     58since it is not a *project*, you can make it a project
     59(if you have write permission to the directory) by creating
     60a ``synApps/support/.project`` text XML file with this content:
     61
     62.. code-block:: xml
     63        :linenos:
     64       
     65        <?xml version="1.0" encoding="UTF-8"?>
     66        <projectDescription>
     67                <name>synApps</name>
     68                <comment>EPICS synApps</comment>
     69                <projects/>
     70                <buildSpec/>
     71                <natures/>
     72        </projectDescription>
     73
     74.. tip:: On line 3, the default name for the project is specified.
     75        This description says the default name will be *synApps*.
     76
     77
     78synApps default fonts and colors
     79===========================================================
     80
     81#. Select menu ``Edit-->Preferences ...``
     82#. Open item ``CSS Applications``
     83#. Open item ``Display``
     84#. Click on item ``BOY``
     85#. For Color File, replace text with ``/synApps/color.def`` or *Browse...* to it
     86#. For Font File, replace text with ``/synApps/font.def`` or *Browse...* to it
     87#. For Top OPIs, replace with OPI file of your choice
     88
     89.. note:: If you get a console message that says:
     90
     91      2012-04-30 15:59:12 ERROR: Failed to read font definition file.
     92
     93   then you've got a typo or some other error.  Repeat these steps to fix it.
     94   
     95.. tip::  If the ``color.def`` (or ``font.def``) file are not found
     96        at the root of the synApps repository, look in the synApps *xxx* module, at this path::
     97       
     98                /synApps/xxx/xxxApp/op/opi/
    4699
    47100
    … …  
    49102===========================================================
    50103
    51 add an IP for the gateway
    52 
    53 check the auto_addr_list
     104add an IP for the gateway (192.168.0.150 is an example)::
     105
     106        {Workspace}\.metadata\.plugins\org.eclipse.core.runtime\.settings\org.csstudio.platform.libs.epics.prefs
     107        addr_list=127.0.0.1 192.168.0.150
     108
     109check the auto_addr_list::
     110
     111        {Workspace}\.metadata\.plugins\org.eclipse.core.runtime\.settings\org.csstudio.platform.libs.epics.prefs
     112        auto_addr_list=true
    54113
    55114
    … …  
    60119        Do NOT forget to add the APS_sr screens, when they become available
    61120
     121Because the many screens from synApps come on many subdirectory paths, a
     122search path feature was added to CSS-BOY with version 3.1.1.  By placing each
     123of the subdirectory name on the search path, all the screens in that
     124subdirectory may be called by name, without the full path name to the file. 
     125The reason for the *OPI Search Path* feature will be demonstrated in
     126:ref:`calling.synapps.screens`.
     127
     128OPI screens may reside on the local computer, on a file server, or be
     129downloaded over an internet connection.  The *OPI Search Path* is defined
     130as a list of file directories, separated by vertical bars ("|"), such as::
     131
     132        opi_search_path=/BOY Examples/|C:\users\5hz\Desktop\|http://ics-srv-web2.sns.ornl.gov/opi/
     133
     134
     135.. note:: As it is written in the CSS-BOY Help files:
     136
     137        The path which is used to search OPI files if the given OPI path is a relative path
     138        and it doesn't exist on the made up absolute path neither.
     139        For example, you can put an OPI file name abc.opi or a relative path abc/def/my.opi
     140        for Open OPI Action, Top OPIs, Schema OPI and so on.
     141        If this OPI file cannot be found as a relative path to the OPI file, it will search the
     142        OPI Search Path and return the first one found on the search path.
     143        It supports workspace path, local file system path and URL path.
     144        The pathes are separated by the vetical bar delimiter ``|``.  For example::
     145       
     146                /synApps/areaDetector/ADApp/op/opi | /synApps/asyn/opi/boy
     147
     148This might be the directory::
     149
     150        C:\Users\Pete\Downloads\sns_css_3.1.1-win32.win32.x86_64\CSS_3.1.1\plugins\org.csstudio.sns.product_3.1.1.20120718
     151
     152As for how to set search path from .ini file, please refer to this tutorial:
     153
     154        http://ics-web.sns.ornl.gov/kasemir/CSS/Training/SLAC/2_4_HierarchicalPrefs.ppt
     155
     156The *OPI Search Path* may be set by several ways:
     157* Preferences dialog
     158* One of several configuration file possibilities.
     159
     160
     161
     162Setting ``opi_search_path`` from a Preferences Dialog
     163-----------------------------------------------------
     164
     165You will also need to get the synApps project onto your OPI search path.  Here is how::
     166
     167        Menu "CSS"
     168          -->   "Preferences:"
     169          open  "CSS Applications"
     170          open  "Display"
     171          click on  "BOY"
     172
     173.. _synApps.search.path:
     174
     175Change the text in for "OPI Search Path" to this really long string (all one line)::
     176
     177                /synApps/areaDetector/ADApp/op/opi | /synApps/asyn/opi/boy | /synApps/autosave/asApp/op/opi | /synApps/busy/busyApp/op/opi | /synApps/calc/calcApp/op/opi | /synApps/camac/camacApp/op/opi | /synApps/dac128V/dac128VApp/op/opi | /synApps/delaygen/delaygenApp/op/opi | /synApps/dxp/dxpApp/op/opi | /synApps/iocStats/op/opi | /synApps/ip/ipApp/op/opi | /synApps/ip330/ip330App/op/opi | /synApps/ipUnidig/ipUnidigApp/op/opi | /synApps/love/loveApp/op/opi | /synApps/mca/mcaApp/op/opi | /synApps/modbus/modbusApp/op/opi | /synApps/motor/motorApp/op/opi | /synApps/optics/opticsApp/op/opi | /synApps/quadEM/quadEMApp/op/opi | /synApps/softGlue/softGlueApp/op/opi | /synApps/sscan/sscanApp/op/opi | /synApps/std/stdApp/op/opi | /synApps/vac/vacApp/op/opi | /synApps/vme/vmeApp/op/opi | /synApps/xxx/xxxApp/op/opi
     178
     179Keep clicking **Ok** until you dismiss all the dialogs.
     180Now the paths should work.
     181
     182        ..note:: Broken into several lines, this string would look like::
     183       
     184                /synApps/areaDetector/ADApp/op/opi
     185                | /synApps/asyn/opi/boy
     186                | /synApps/autosave/asApp/op/opi
     187                | /synApps/busy/busyApp/op/opi
     188                | /synApps/calc/calcApp/op/opi
     189                | /synApps/camac/camacApp/op/opi
     190                | /synApps/dac128V/dac128VApp/op/opi
     191                | /synApps/delaygen/delaygenApp/op/opi
     192                | /synApps/dxp/dxpApp/op/opi
     193                | /synApps/iocStats/op/opi
     194                | /synApps/ip/ipApp/op/opi
     195                | /synApps/ip330/ip330App/op/opi
     196                | /synApps/ipUnidig/ipUnidigApp/op/opi
     197                | /synApps/love/loveApp/op/opi
     198                | /synApps/mca/mcaApp/op/opi
     199                | /synApps/modbus/modbusApp/op/opi
     200                | /synApps/motor/motorApp/op/opi
     201                | /synApps/optics/opticsApp/op/opi
     202                | /synApps/quadEM/quadEMApp/op/opi
     203                | /synApps/softGlue/softGlueApp/op/opi
     204                | /synApps/sscan/sscanApp/op/opi
     205                | /synApps/std/stdApp/op/opi
     206                | /synApps/vac/vacApp/op/opi
     207                | /synApps/vme/vmeApp/op/opi/synApps/xxx/xxxApp/op/opi         
     208
     209Setting ``opi_search_path`` from a Configuration File
     210-----------------------------------------------------
     211
     212There are several configuration files that might be used
     213to define the *OPI Search Path*.  The choice of which depends on the
     214goal of the individual.
     215
     216From the ``plugin_customizations.ini`` file that comes with CSS-BOY, there are these notes:
     217
     218Fundamentally, the Eclipse preference mechanism works like this
     219to allow customization at various levels:
     220
     2211. Each plugin might contain default settings that are hardcoded
     222   inside the Java sources of the plugin.
     2232. In addition, each plugin might have a file preferences.ini
     224   in the root directory of the plugin directory or jar file.
     225   When present, those values override the hardcoded settings.
     226   Ideally, each plugin with preference settings has such a
     227   preferences.ini file to define the defaults because this
     228   provides a convenient place to locate all the available
     229   settings of a plugin in one file.
     2303. A plugin_customization.ini file like this one, located
     231   in the root of the "Product" plugin directory or jar file
     232   can override all of the above.
     233   It is ideally used to provide site-specific defaults
     234   (as this one does for using CSS at the SNS).
     2354. When starting CSS (or any Eclipse product), a customization file
     236   with the same format can be provided via the -pluginCustomization
     237   command line option to override settings.
     238   NOTE: Eclipse silently ignores missing customization files.
     239   THERE IS NO ERROR MESSAGE when the specified file does not exist!
     2405. Finally, each end user can use the CSS/Preferences menu item to
     241   interactively adjust most settings. Those changes are stored in the
     242   workspace directory under::
     243   
     244       {Workspace}/.metadata/.plugins/org.eclipse.core.runtime/.settings
     245
     246The default preferences can be set in ``plugin_customization.ini``
     247file which is located in the root of the "Product" plugin directory
     248or jar file. It is ideally used to provide site-specific default
     249preferences. For example, you can change the default BOY preferences
     250in this file with corresponding preference keys::
     251
     252        org.csstudio.opibuilder/color_file=http://your_site.gov/color.def
     253        org.csstudio.opibuilder/font_file=http://your_site.gov/font.def
     254        org.csstudio.opibuilder/opi_gui_refresh_cycle=100
     255        org.csstudio.opibuilder/no_edit=true
     256        org.csstudio.opibuilder/macros="N","North"|"W","West"|"SYS","LLRF"|"SubSys","HPM"
     257        #popup console level, it can be NO_POP, INFO, or ALL
     258        org.csstudio.opibuilder/popup_console=NO_POP
     259
     260 You can also give a different customization file with the command line option -pluginCustomization when starting CSS.
     261
     262
     263in the Workspace
     264+++++++++++++++++++++++
     265
     266One way to set the *OPI Search Path* is to set it in the Workspace, as I show here:
     267
     268On my Windows 7 system, my default workspace is::
     269
     270        {Workspace} = C:\Users\Pete\CSS-Workspaces\Default
     271
     272and the workspace configuration file for the OPI Builder is::
     273
     274        {Workspace}\.metadata\.plugins\org.eclipse.core.runtime\.settings\org.csstudio.opibuilder.prefs
     275
     276Here is an example of the *org.csstudio.opibuilder.prefs* file on my Ubuntu system
     277(use the long, one-line :ref:`synApps search path <synApps.search.path>` given above):
     278
     279.. code-block:: text
     280        :linenos:
     281       
     282        color_file=/iocPRJ/color.def
     283        eclipse.preferences.version=1
     284        font_file=/iocPRJ/font.def
     285        opi_search_path=/synApps/areaDetector/ADApp/op/opi | ... you get the idea, it's a long line
     286        popup_console=ALL
     287        top_opis=/iocPRJ/prj.opi
     288
    62289
    63290Creating the Beam Line Project
    64291===========================================================
    65292
     293Screens for your instrument or beam line or other installation of EPICS
     294may already be available.  If so, you might import them by following the steps
     295above used to import synApps.  If you need to develop your own screens,
     296then follow these steps:
     297
     298#. Select menu ``File-->New``
     299#. Open ``General`` category,
     300   select ``Project``,
     301   click ``Next`` button
     302#. Give it a Project name, something short such as *45ID* or *iocPRJ*
     303   (try to avoid using spaces, it makes things harder later on),
     304#. In the ``Navigator`` view,
     305   open the new project by double-clicking (or any other equivalent way)
     306   
     307Create an OPI file
     308------------------------------------
     309
     310#. Select menu ``File-->New``
     311#. Open ``BOY`` category,
     312   select ``OPI File``,
     313   click ``Next`` button
     314#. Select the folder to contain your new OPI screen,
     315   type the name of the new OPI file in the box,
     316   click ``Finish`` button
     317
     318Your new screen will appear in a CSS-BOY editing window.
     319You might consider changing to the *OPI Editor* perspective
     320as this will provide much more help in editing the screen.
     321
     322Once you have setup the CSS-BOY project for your EPICS installation,
     323you might want one particular file to be the default  *main* file
     324for your CSS-BOY workspace.  Edit the menu for *Top OPIs* via:
     325``Edit --> Preferences ... --> CSS Applications --> Display``
     326
     327
     328.. _calling.synapps.screens:
    66329
    67330Calling synApps screens
    68331===========================================================
     332
     333Also, when calling a synApps .opi screen from the instrument or beam line,
     334it is not necessary to use the full path since there is an OPI search path
     335that will locate the screen.  Example, instead of::
     336
     337   /synApps/motor/motorApp/op/opi/motor3x.opi
     338
     339Instead, you just call::
     340
     341   motor3x.opi
     342
     343.. note::  If you require a specific version of synApps, for example a specific older
     344                        version of areaDetector, create a separate CSS project for it in your
     345                        workspace.
     346
     347.. TODO: could use some instructions how to create this kind of project.  An example would help.
     348
     349

  • cssboy_deployment/docs/source/index.rst

    r1060 r1061  
    4141   configure
    4242   glossary
    43    plans
    4443
    4544

  • cssboy_deployment/docs/source/thoughts.rst

    r1060 r1061  
    55============
    66
    7 
    8 
    9 
    10 
    11 add OPI screens from synApps as a CSS project
    12 --------------------------------------------------------------------------
    13 
    14 #. Open the ``CSS_EPICS_3.1.1`` (or whatever version) directory
    15 #. Start ``css`` by double-clicking it.
    16    If you use a unix or linux command line, type::
    17    
    18        ./css &
    19    
    20 #. Select menu ``File-->Import ...``
    21 #. Open ``General`` category,
    22    select ``Existing Projects into Workspace``,
    23    click ``Next`` button
    24 #. Click ``Browse ...`` button (in *Import* window),
    25    navigate to ``/APSshare/epics/synApps_5_6/support/``
    26    (or ``/usr/local/epics/synAppsSVN/support/`` or wherever)
    27 #. Click ``Ok`` button
    28 #. Click ``Finish`` button (in *Import* window)
    29 
    30 .. _synApps.project.file:
    31 
    32 .. note::  If CSS reports that your synApps directory cannot be imported
    33         since it is not a *project*, you can make it a project by creating
    34         a ``synApps/support/.project`` text XML file with this content::
    35 
    36                 <?xml version="1.0" encoding="UTF-8"?>
    37                 <projectDescription>
    38                         <name>synApps</name>
    39                         <comment>EPICS synApps</comment>
    40                         <projects/>
    41                         <buildSpec/>
    42                         <natures/>
    43                 </projectDescription>
    44 
    45 
    46 define synApps default fonts and colors
    47 ---------------------------------------------
    48 
    49 #. Select menu ``Edit-->Preferences ...``
    50 #. Open item ``CSS Applications``
    51 #. Open item ``Display``
    52 #. Click on item ``BOY``
    53 #. For Color File, replace text with ``/synApps/color.def`` or *Browse...* to it
    54 #. For Font File, replace text with ``/synApps/font.def`` or *Browse...* to it
    55 #. For Top OPIs, replace with OPI file of your choice
    56 
    57 .. note:: If you get a console message that says:
    58 
    59       2012-04-30 15:59:12 ERROR: Failed to read font definition file.
    60 
    61    then you've got a typo or some other error.  Repeat these steps to fix it.
    62    
    63 .. note::  The ``color.def`` (or ``font.def``) file might not be found
    64         at the root of the synApps repository.
    65         Another place to find it is in the *xxx* module, at this path::
    66        
    67                 /synApps/xxx/xxxApp/op/opi/
    68 
    69 .. caution::  Looks like things are here twice!  Be prepared.
    70 
    71 OPI Search Path
    72 ---------------------------------------------
    73 
    74 .. warning:: Don't rely on this section here.  A better one is up ahead!  See: :ref:`Setting the OPI Search Path`.
    75 
    76 You will also need to get the synApps project onto your OPI search path.  Here is how::
    77 
    78         Menu "CSS"
    79           -->   "Preferences:"
    80           open  "CSS Applications"
    81           open  "Display"
    82           click on  "BOY"
    83 
    84 Change the text in for "OPI Search Path" to this really long string (all one line)::
    85 
    86                 /synApps/areaDetector/ADApp/op/opi | /synApps/asyn/opi/boy | /synApps/autosave/asApp/op/opi | /synApps/busy/busyApp/op/opi | /synApps/calc/calcApp/op/opi | /synApps/camac/camacApp/op/opi | /synApps/dac128V/dac128VApp/op/opi | /synApps/delaygen/delaygenApp/op/opi | /synApps/dxp/dxpApp/op/opi | /synApps/iocStats/op/opi | /synApps/ip/ipApp/op/opi | /synApps/ip330/ip330App/op/opi | /synApps/ipUnidig/ipUnidigApp/op/opi | /synApps/love/loveApp/op/opi | /synApps/mca/mcaApp/op/opi | /synApps/modbus/modbusApp/op/opi | /synApps/motor/motorApp/op/opi | /synApps/optics/opticsApp/op/opi | /synApps/quadEM/quadEMApp/op/opi | /synApps/softGlue/softGlueApp/op/opi | /synApps/sscan/sscanApp/op/opi | /synApps/std/stdApp/op/opi | /synApps/vac/vacApp/op/opi | /synApps/vme/vmeApp/op/opi | /synApps/xxx/xxxApp/op/opi
    87 
    88 Keep clicking **Ok** until you dismiss all the dialogs.
    89 Now the paths should work.
    90 
    91         .. note:: From the CSS-BOY Help files:
    92        
    93                 The path which is used to search OPI files if the given OPI path is a relative path
    94                 and it doesn't exist on the made up absolute path neither.
    95                 For example, you can put an OPI file name abc.opi or a relative path abc/def/my.opi
    96                 for Open OPI Action, Top OPIs, Schema OPI and so on.
    97                 If this OPI file cannot be found as a relative path to the OPI file, it will search the
    98                 OPI Search Path and return the first one found on the search path.
    99                 It supports workspace path, local file system path and URL path.
    100                 The pathes are separated by the vetical bar delimiter ``|``.  For example::
    101                
    102                         /synApps/areaDetector/ADApp/op/opi | /synApps/asyn/opi/boy
    103 
    104 This might be the directory::
    105 
    106         C:\Users\Pete\Downloads\sns_css_3.1.1-win32.win32.x86_64\CSS_3.1.1\plugins\org.csstudio.sns.product_3.1.1.20120718
    107 
    108 
    109 Define a project for your EPICS installation
    110 +++++++++++++++++++++++++++++++++++++++++++++
    111 
    112 Screens for your instrument or beam line or other installation of EPICS
    113 may already be available.  If so, you might import them by following the steps
    114 above used to import synApps.  If you need to develop your own screens,
    115 then follow these steps:
    116 
    117 #. Select menu ``File-->New``
    118 #. Open ``General`` category,
    119    select ``Project``,
    120    click ``Next`` button
    121 #. Give it a Project name, something short such as *44ID* or *iocPRJ*
    122    (try to avoid using spaces, it makes things harder later on),
    123 #. In the ``Navigator`` view,
    124    open the new project by double-clicking (or any other equivalent way)
    125 
    126 Create an OPI file
    127 +++++++++++++++++++++
    128 
    129 #. Select menu ``File-->New``
    130 #. Open ``BOY`` category,
    131    select ``OPI File``,
    132    click ``Next`` button
    133 #. Select the folder to contain your new OPI screen,
    134    type the name of the new OPI file in the box,
    135    click ``Finish`` button
    136 
    137 Your new screen will appear in a CSS-BOY editing window.
    138 You might consider changing to the *OPI Editor* perspective
    139 as this will provide much more help in editing the screen.
    140 
    141 Once you have setup the CSS-BOY project for your EPICS installation,
    142 you might want one particular file to be the default  *main* file
    143 for your CSS-BOY workspace.  Edit the menu for *Top OPIs* via:
    144 ``Edit --> Preferences ... --> CSS Applications --> Display``
    145 
    146 
    147 .. _Setting the OPI Search Path:
    148 
    149 Setting the OPI Search Path
    150 ------------------------------------
    151 
    152 .. note:: This could be set in a ``.ini`` file.  Needs some research...
    153         Check the help for "Setting Preferences"
    154        
    155         The default preferences can be set in ``plugin_customization.ini``
    156         file which is located in the root of the "Product" plugin directory
    157         or jar file. It is ideally used to provide site-specific default
    158         preferences. For example, you can change the default BOY preferences
    159         in this file with corresponding preference keys::
    160 
    161                 org.csstudio.opibuilder/color_file=http://your_site.gov/color.def
    162                 org.csstudio.opibuilder/font_file=http://your_site.gov/font.def
    163                 org.csstudio.opibuilder/opi_gui_refresh_cycle=100
    164                 org.csstudio.opibuilder/no_edit=true
    165                 org.csstudio.opibuilder/macros="N","North"|"W","West"|"SYS","LLRF"|"SubSys","HPM"
    166                 #popup console level, it can be NO_POP, INFO, or ALL
    167                 org.csstudio.opibuilder/popup_console=NO_POP
    168 
    169  You can also give a different customization file with the command line option -pluginCustomization when starting CSS.
    170 
    171 .. used to show "importing synApps screens" here
    172 
    173 Calling the synApps OPI screens
    174 -------------------------------------
    175 
    176 Also, when calling a synApps .opi screen from the instrument or beam line,
    177 it is not necessary to use the full path since there is an OPI search path
    178 that will locate the screen.  Example, instead of::
    179 
    180    /synApps/motor/motorApp/op/opi/motor3x.opi
    181 
    182 Instead, you just call::
    183 
    184    motor3x.opi
    185 
    186 .. note::  If you require a specific version of synApps, for example a specific older
    187                         version of areaDetector, create a separate CSS project for it in your
    188                         workspace.
    189 
    190 .. TODO: could use some instructions how to create this kind of project.  An example would help.
    191 
    192 
    193 Setting the OPI Search Path
    194 ------------------------------
    195 
    196 from the ``plugin_customizations.ini`` file that comes with CSS-BOY, there are these notes::
    197 
    198         # Fundamentally, the Eclipse preference mechanism works like this
    199         # to allow customization at various levels:
    200         # 1. Each plugin might contain default settings that are hardcoded
    201         #    inside the Java sources of the plugin.
    202         # 2. In addition, each plugin might have a file preferences.ini
    203         #    in the root directory of the plugin directory or jar file.
    204         #    When present, those values override the hardcoded settings.
    205         #    Ideally, each plugin with preference settings has such a
    206         #    preferences.ini file to define the defaults because this
    207         #    provides a convenient place to locate all the available
    208         #    settings of a plugin in one file.
    209         # 3. A plugin_customization.ini file like this one, located
    210         #    in the root of the "Product" plugin directory or jar file
    211         #    can override all of the above.
    212         #    It is ideally used to provide site-specific defaults
    213         #    (as this one does for using CSS at the SNS).
    214         # 4. When starting CSS (or any Eclipse product), a customization file
    215         #    with the same format can be provided via the -pluginCustomization
    216         #    command line option to override settings.
    217         #    NOTE: Eclipse silently ignores missing customization files.
    218         #    THERE IS NO ERROR MESSAGE when the specified file does not exist!
    219         # 5. Finally, each end user can use the CSS/Preferences menu item to
    220         #    interactively adjust most settings. Those changes are stored in the
    221         #    workspace directory under
    222         #        {Workspace}/.metadata/.plugins/org.eclipse.core.runtime/.settings
    223 
    224 .. code-block:: text
    225     :linenos:
    226 
    227                                  {Workspace}\.metadata\.plugins\org.eclipse.core.runtime\.settings\org.csstudio.opibuilder.prefs
    228         C:\Users\Pete\CSS-Workspaces\Default\.metadata\.plugins\org.eclipse.core.runtime\.settings\org.csstudio.opibuilder.prefs
    229 
    230 
    231 Here is an example of the *org.csstudio.opibuilder.prefs* file on my Ubuntu system:
    232 
    233 .. code-block:: text
    234         :linenos:
    235        
    236         color_file=/iocPRJ/color.def
    237         eclipse.preferences.version=1
    238         font_file=/iocPRJ/font.def
    239         opi_search_path=/synApps/areaDetector/ADApp/op/opi | ... you get the idea, it's a long line
    240         popup_console=ALL
    241         top_opis=/iocPRJ/prj.opi
    242 
    243 
    244 Here is the full ``opi_search_path`` (too long to print well in the line-numbered block)::
    245 
    246         opi_search_path=/synApps/areaDetector/ADApp/op/opi | /synApps/asyn/opi/boy | /synApps/autosave/asApp/op/opi | /synApps/busy/busyApp/op/opi | /synApps/calc/calcApp/op/opi | /synApps/camac/camacApp/op/opi | /synApps/dac128V/dac128VApp/op/opi | /synApps/delaygen/delaygenApp/op/opi | /synApps/dxp/dxpApp/op/opi | /synApps/iocStats/op/opi | /synApps/ip/ipApp/op/opi | /synApps/ip330/ip330App/op/opi | /synApps/ipUnidig/ipUnidigApp/op/opi | /synApps/love/loveApp/op/opi | /synApps/mca/mcaApp/op/opi | /synApps/modbus/modbusApp/op/opi | /synApps/motor/motorApp/op/opi | /synApps/optics/opticsApp/op/opi | /synApps/quadEM/quadEMApp/op/opi | /synApps/softGlue/softGlueApp/op/opi | /synApps/sscan/sscanApp/op/opi | /synApps/std/stdApp/op/opi | /synApps/vac/vacApp/op/opi | /synApps/vme/vmeApp/op/opi | /synApps/xxx/xxxApp/op/opi
    247        
    248 
    249 Set OPI Search Path from .ini file
    250 --------------------------------------------
    251 
    252 As for how to set search path from .ini file,
    253 please refer to this tutorial:
    254 http://ics-web.sns.ornl.gov/kasemir/CSS/Training/SLAC/2_4_HierarchicalPrefs.ppt
    255 
    256 For example::
    257 
    258    opi_search_path=/BOY Examples/|C:\users\5hz\Desktop\|http://ics-srv-web2.sns.ornl.gov/opi/
    2597
    2608
Note: See TracChangeset for help on using the changeset viewer.