////////////////////////////////////////////////////////
  To install a binary kit :
////////////////////////////////////////////////////////

 - pick some osc_[batch,vis,g4]-<version>-<platform>.zip
 - unzip.
   In the below <kit> is for one of [osc_batch,OpenScientist,osc_g4]
 - On UNIX : 
     cd <kit>/<version>
    (chmod a+x install)
     ./install

  Note that the source kits are your number one insurance ; then 
 even if installing a binary kit, download anyway the corresponding 
 source kit.

  IMPORTANT : the binary kits contain a sys directory with
 the related material coming from the system on which the
 kit had been built. For example, for Linux, by using 
 ldd on the programs and shared libs we have traced
 the used system .so and put them under the sys directory.
 This directory is NOT put by default in the paths
 by the setup scripts. But it may be useful to have it 
 at hand in case the targeted platform is similar 
 but quite not the same than the one on which the build 
 had been done : a situation which is, helas, a common
 one for Linux where numerous "distributions" of 
 this operating system are around.

////////////////////////////////////////////////////////
  To use a binary kit :
////////////////////////////////////////////////////////
    csh> source <install_path>/<kit>/<version>/setup.csh
  (  sh> . <install_path>/<kit>/<version>/setup.sh )
  ( DOS> call <install_path>\<kit>\<version>\setup.bat )
     OS> <run application>
 for example :
     OS> aida-config        # with any kit
     OS> AIDA_example_Store # with any kit
   ( OS> onx-config         # with the osc_vis kit )
   ( OS> onxlab             # with the osc_vis kit )
   ( OS> opaw               # with the osc_vis kit )
   ( OS> g4lab-config       # with the osc_g4 kit )
   ( OS> G4Simple_session   # with the osc_g4 kit )
   ( OS> G4Examples_N02     # with the osc_g4 kit )

  The batch kits are targeted for "data capturing" in batch programs.
 Then mainly to book, fill and save histograms and tuples in files 
 at various formats by using the AIDA interfaces. There is no 
 interactivity and visualization in the batch kits. If building
 from source ; since the code is in principle ANSI C/C++ and does
 not rely on "foreign" (or "external") packages, the construction
 should be straightforward on all platforms.

  The vis/OpenScientist kits contain the batch kits plus programs 
 to do some plotting and have some interactivity over the files 
 produced by batch programs. (Obvsiouly someone can build programs, 
 through the AIDA interfaces, that book, fill histograms and tuples 
 and plot them too in one session). The vis kits contain also material 
 to do advanced visualization by using the coin3d and HEPVis libraries.

  The g4 kits are the vis kits plus Geant4 modules to do
 visualization of a Geant4 program. The g4 kits contain also
 a version of some of the Geant4 example but by using the OpenScientist
 interactivity system (G4Lab::UIOnX) instead of the Geant4 G4UIterminal.
 The g4 kits contains a version of CLHEP and Geant4. Some of the 
 examples need some "Geant4 process data file". Due to the huge
 overall size of them, they had not been put within the g4 kits but
 are delivered in a standalone G4data.zip file. Then, if needed
 you have to download this file and unzip it under the :
     Resources/Geant4
 directory of a g4 kit. Then having for example :
     Resources/Geant4/data/RadioactiveDecay<version>

////////////////////////////////////////////////////////
  To build from source :
////////////////////////////////////////////////////////
 After unzipping one of :
     osc_batch_source-<version>.zip
     osc_source-<version>.zip
 go under the directory
     OpenScientist/<vers>/<kit>/<vers>/obuild
 and follow instructions found in the README file. The build should
 produce at end something having the similar structure than a 
 binary kit. When done, simply move this new local binary kit
 where you want and follow the same upper instructions than
 for a downloadable binary kit to install it and use it.

  For the batch kit, since the code is in principle ANSI C/C++ and does
 not rely on "foreign" (or "external") packages, the construction
 should be straightforward on all platforms.

  The construction of a osc_vis or osc_g4 kit may need more tuning, 
 especially to find the "foreign" packages : Motif, Qt, CLHEP, Geant4, etc...
 There is more instructions under the osc_build section of the web pages.