Changeset 1055 for cssboy_deployment/docs/source/instructions.rst

Timestamp:

Jul 18, 2012 2:34:59 PM (11 years ago)

Author:

jemian

Message:

still working but can leave it alone for now

File:

• cssboy_deployment/docs/source/instructions.rst (modified) (3 diffs)

cssboy_deployment/docs/source/instructions.rst

@@ -5 +5 @@
 ==========================
 
-.. caution:: This documentation is under revision, thus the order may seem a bit scrambled.
+.. caution:: At this time, this documentation is a collection of notes
+        related to installation or configuration of CSS-BOY.  It needs to be 
+        set into some sort of order.
 
 Install OPI screens (and other resources such as image files, javascript,
@@ -244 +246 @@
                         /synApps/areaDetector/ADApp/op/opi | /synApps/asyn/opi/boy
 
+This might be the directory::
+
+        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
 
 
@@ -266 +271 @@
 
 
+Setting the OPI Search Path
+------------------------------
+
+from the ``plugin_customizations.ini`` file that comes with CSS-BOY, there are these notes::
+
+        # Fundamentally, the Eclipse preference mechanism works like this
+        # to allow customization at various levels:
+        # 1. Each plugin might contain default settings that are hardcoded
+        #    inside the Java sources of the plugin.
+        # 2. In addition, each plugin might have a file preferences.ini
+        #    in the root directory of the plugin directory or jar file.
+        #    When present, those values override the hardcoded settings.
+        #    Ideally, each plugin with preference settings has such a 
+        #    preferences.ini file to define the defaults because this
+        #    provides a convenient place to locate all the available
+        #    settings of a plugin in one file.
+        # 3. A plugin_customization.ini file like this one, located
+        #    in the root of the "Product" plugin directory or jar file
+        #    can override all of the above.
+        #    It is ideally used to provide site-specific defaults
+        #    (as this one does for using CSS at the SNS).
+        # 4. When starting CSS (or any Eclipse product), a customization file
+        #    with the same format can be provided via the -pluginCustomization
+        #    command line option to override settings.
+        #    NOTE: Eclipse silently ignores missing customization files.
+        #    THERE IS NO ERROR MESSAGE when the specified file does not exist! 
+        # 5. Finally, each end user can use the CSS/Preferences menu item to
+        #    interactively adjust most settings. Those changes are stored in the
+        #    workspace directory under 
+        #        {Workspace}/.metadata/.plugins/org.eclipse.core.runtime/.settings
+
+::
+                             {Workspace}\.metadata\.plugins\org.eclipse.core.runtime\.settings\org.csstudio.opibuilder.prefs
+        C:\Users\Pete\CSS-Workspaces\Default\.metadata\.plugins\org.eclipse.core.runtime\.settings\org.csstudio.opibuilder.prefs
 
 Glossary of Terms