From: mkr Date: Wed, 31 May 2006 07:25:45 +0000 (+0000) Subject: Fix for bug PAL12493: Latest update in "Kernel & GUI Help" documentation for 3.2... X-Git-Url: http://git.salome-platform.org/gitweb/?a=commitdiff_plain;h=ced249e2e39960ed23852521f39c14750204cb4b;p=modules%2Fgui.git Fix for bug PAL12493: Latest update in "Kernel & GUI Help" documentation for 3.2.0 version. --- diff --git a/doc/salome/gui/GUI/choicepage.png b/doc/salome/gui/GUI/choicepage.png deleted file mode 100755 index 16339d9ef..000000000 Binary files a/doc/salome/gui/GUI/choicepage.png and /dev/null differ diff --git a/doc/salome/gui/GUI/image51.jpg b/doc/salome/gui/GUI/image51.jpg deleted file mode 100755 index 05cdf229e..000000000 Binary files a/doc/salome/gui/GUI/image51.jpg and /dev/null differ diff --git a/doc/salome/gui/GUI/intropage.png b/doc/salome/gui/GUI/intropage.png deleted file mode 100755 index 5ef0ae401..000000000 Binary files a/doc/salome/gui/GUI/intropage.png and /dev/null differ diff --git a/doc/salome/gui/GUI/kernel.log b/doc/salome/gui/GUI/kernel.log index fd47b06a4..699fdfa32 100755 --- a/doc/salome/gui/GUI/kernel.log +++ b/doc/salome/gui/GUI/kernel.log @@ -147,29 +147,25 @@ robohhre.lng texture_horiz_ltbluebubbles.jpg index.glo default.css -choicepage.png -intropage.png pics\registry1.png pics\open.jpg pics\icon_about.png pics\registry3.png pics\studyproperties.png +pics\readmepage.png pics\registry4.png pics\cataloggenerator.png tip1.gif pics\pref31.png -readmepage.png pics\save.jpg pics\pref32.png pics\pref21.png image70.gif -image51.jpg pics\newsticn.jpg pics\pref33.png pics\pref22.png pics\pref11.png image71.gif -progresspage.png pics\pref34.png pics\pref23.png pics\pref12.png @@ -177,6 +173,7 @@ image94.gif closestudy.png image72.gif pics\copy-paste.jpg +pics\launch1.png pics\pref24.png pics\pref13.png pics\selectfont.png @@ -192,20 +189,22 @@ pics\pref37.png pics\pref15.png image75.gif i_blue.jpg +pics\productpage.png pics\pref38.png image65.gif note1.gif pics\pref39.png pics\import.png pics\objectbrowser1.png +pics\progresspage.png pics\objectbrowser2.png image67.gif -productpage.png pics\loadscript.png pics\geomview-alt.png pics\lockedstudy.png pics\loadstudy2.png image68.gif +pics\choicepage.png image69.gif index.ppf ehlpdhtm.js @@ -252,6 +251,7 @@ whgdata\whlstfl22.htm whgdata\whlstfl23.htm whgdata\whlstfl24.htm whgdata\whlstfl25.htm +whgdata\whlstfl26.htm whgdata\whlstf0.htm whgdata\whlstf1.htm whgdata\whlstf2.htm diff --git a/doc/salome/gui/GUI/kernel/introduction.htm b/doc/salome/gui/GUI/kernel/introduction.htm index bc57ac02b..019cc7f42 100755 --- a/doc/salome/gui/GUI/kernel/introduction.htm +++ b/doc/salome/gui/GUI/kernel/introduction.htm @@ -19,21 +19,15 @@ img_whs2 { border:none; width:550px; height:275px; float:none; border-style:none h1.whs3 { text-align:justify; } p.whs4 { font-family:'Times New Roman' , serif; text-align:justify; text-indent:48px; } p.whs5 { font-family:'Times New Roman' , serif; text-align:justify; } -table.whs6 { x-cell-content-align:top; width:100%; border-spacing:0px; } -col.whs7 { width:61.765%; } -col.whs8 { width:38.235%; } -tr.whs9 { x-cell-content-align:top; } -td.whs10 { width:61.765%; padding-right:10px; padding-left:10px; border-right-style:none; border-left-style:none; border-top-style:none; border-bottom-style:none; } -ul.whs11 { list-style:disc; } -td.whs12 { width:38.235%; padding-right:10px; padding-left:10px; border-top-style:none; border-bottom-style:none; border-right-style:none; } -p.whs13 { text-align:right; } -img_whs14 { border:none; width:270px; height:221px; border-style:none; } -p.whs15 { font-family:'Times New Roman' , serif; text-align:justify; font-weight:bold; } -col.whs16 { width:31.561%; } -col.whs17 { width:68.439%; } -td.whs18 { width:31.561%; padding-right:10px; padding-left:10px; border-right-style:none; border-left-style:none; border-top-style:none; border-bottom-style:none; } -img_whs19 { border:none; width:249px; height:221px; border-style:none; } -td.whs20 { width:68.439%; padding-right:10px; padding-left:10px; border-top-style:none; border-bottom-style:none; border-right-style:none; } +ul.whs6 { list-style:disc; } +p.whs7 { font-family:'Times New Roman' , serif; text-align:justify; font-weight:bold; } +table.whs8 { x-cell-content-align:top; width:100%; border-spacing:0px; } +col.whs9 { width:31.561%; } +col.whs10 { width:68.439%; } +tr.whs11 { x-cell-content-align:top; } +td.whs12 { width:31.561%; padding-right:10px; padding-left:10px; border-right-style:none; border-left-style:none; border-top-style:none; border-bottom-style:none; } +img_whs13 { border:none; width:249px; height:221px; border-style:none; } +td.whs14 { width:68.439%; padding-right:10px; padding-left:10px; border-top-style:none; border-bottom-style:none; border-right-style:none; } --> - + - - -

-g - + + +

-g  / +  --gui +

Runs the Installation Wizard in the GUI mode (default option). In this case only <xml-file> key is taken into account. Other parameters are ignored.   - - -

-b - + + +

-b  / +  --batch + +

Runs the Installation Wizard in command-line mode. - - -

-f <xml-file> - + + +

-f  <FILE> /  --file=<FILE> + +

The configuration file to be used by the Installation Wizard.  - If this parameter is missed then the script tries to define the Linux - version and uses corresponding xml file. For examle, for the Linux - Mandrake 10.1 config_Mandrake10_1.xml  file is supposed - to be used by default. If the appropriate file is not found, config.xml - is used by default.  This file refers to the basic target platform - which is Mandrake 10.1 for SALOME 3.0 and higher. If config.xml file is - also not found the warning message box is shown and Installation Wizard - quits. - - - -

 -t <target-dir> - -

The target directory, SALOME platform to be installed to. If used, overloads - default target directory, given in the configuration xml file (usually - /salome, see here). - - - -

-tmp <tmp-dir> - -

The directory, which is used to contain temporary files.  If used, - overloads default temporary directory, given in the configuration xml - file (usually /tmp, see here). - - - -

-h - -

Prints this help information. + If this parameter is not used then the installation script tries to define + the Linux version and + use the corresponding xml file. For example, config_Mandrake10_1.xml  + file is to be used for  Linux + Mandrake 10.1. If the appropriate file is not found, the file config.xml + will be used.  This file refers to the basic target platform which + is Linux Mandrake 10.1 for SALOME 3.0 and higher. If config.xml file is + also not found, the warning message box is shown (in GUI mode) or printed + to the console (in batch mode) and the Installation Wizard quits. + + + +

-d <DIR> / --target=<DIR> + + +

The target directory for SALOME platform to be installed to. If used, +  this option + overrides the default target directory, defined in the configuration XML + file (usually ${HOME}/salome_<version>). + + + +

 -t <DIR> / --tmp=<DIR> + + +

The directory, which is used for temporary files. If used, this option + overrides the default temporary directory, given in the configuration + xml file (usually /tmp, see here). + + + +

-h /  --help + + +

Prints help information about available options. + + + +

-v / --version + +

Prints version information (Note: this is the Installation Wizard's + version number, not of SALOME platform).   -

   -      
- 

- -

So, to run the Installation Wizard in the GUI mode, just type runInstall. +

    +    
+To run the Installation Wizard in the GUI mode, just type runInstall.

 

@@ -260,11 +277,11 @@ if ((navigator.appName == "Netscape") && (parseInt(navigator.appVersion) == 4))

 

-

+

 

-

Figure 1: "Introduction" +

Figure 1: "Introduction" page

 

@@ -324,14 +341,14 @@ If you want to use native products (like gcc -

+

-

 

+

 

-

Figure 2: "Installation +

Figure 2: "Installation settings" page in the advanced mode

-

 

+

 

The "Total disk space required:" field displays how much disk space on the hard drive is required for installation of selected @@ -341,8 +358,8 @@ If you want to use native products (like gcc   -

Please, take into account +

Please, take into account that the displayed amount of required disk space is approximate and may differ when you install products on your hard drive.

@@ -357,8 +374,8 @@ If you want to use native products (like gcc

 

-

In fact, temporary files +

In fact, temporary files are not stored in the directory entered by user. The Installation Wizard creates in this directory an additional folder named something like INSTALLWORKXXXXX where XXXXX is a unique number. @@ -374,8 +391,8 @@ If you want to use native products (like gcc

 

-

Unfortunately, the configure +

Unfortunately, the configure procedure has a very annoying bug under Linux platform. The directory should be obligatory entered without spaces. For example, the configure procedure for gcc won't work if you pass the following parameter: @@ -392,17 +409,15 @@ If you want to use native products (like gcc corresponding warning message box. Otherwise the wizard will follow to the next page:

-

 

- -


-

+


+

-

 

+

 

-

Figure 3: "Check +

Figure 3: "Check your choice" page

-

 

+

 

This page summarizes the installation settings you've made on the previous pages. You can check again your choice to change it if necessary.

@@ -410,20 +425,18 @@ If you want to use native products (like gcc  

When you are sure that everything is OK, press the "Next" - button to follow to the next page.

+ button to follow to the next page.

 

- - -

 

+

 

-

 

+

 

-

Figure 4: "Installation +

Figure 4: "Installation progress" page

-

 

+

 

To start installation of the selected products click "Start" button. It launches the shell installation script and you will be able @@ -435,8 +448,8 @@ If you want to use native products (like gcc

 

-

press [Enter] when you finish +

press [Enter] when you finish typing data.

 

@@ -462,15 +475,15 @@ If you want to use native products (like gcc successfully) you can go back to the previous pages to start a new installation or click the "Next" button to go the Readme page:

-


-

+


+

-

 

+

 

-

Figure 5: "Finish +

Figure 5: "Finish installation" page

-

 

+

 

In this page you can read some important information about the Instalation Wizard itself and some hints: how to run and test SALOME or how to build @@ -496,8 +509,8 @@ You can also launch SALOME Desktop from this page by clicking the "Launc   -

salome.(c)sh and env_products.(c)sh +

salome.(c)sh and env_products.(c)sh files are slightly different: env_products.* files are optimized to be used for the building of SALOME modules from the sources (see README file provided with the installation @@ -522,60 +535,60 @@ You can also launch SALOME Desktop from this page by clicking the "Launc

 

- +
- - + - + + - + - - - + + - - - - - - + + + + + - - +It is recommended to use the native tcl/tk for Mandrake 10.1. - - - + - - - - - + + 4)ver="$ver_major.$ver_minor"
5) Check the existence of libStdPlugin.so in OpenCASCADE distribution, - - - - - - + + + + - - +It is recommended to use the native Python for Mandrake 10.1. - - - + + - - - - - + + - - + to 3.3.3.
+It is recommended to use the native Qt for Mandrake 10.1. - - - + + - - - - - + + - - - - - + + - - - - - + + - - - - - + + - - - - - + + - - + environment variable is set. The NETGEN version should be patched. - - + - - - - - - + + - - - - - + + - - - - - + + - - - - - - - - - - - - + + + + - - +It is recommended to use the native doxygen for Mandrake 10.1. - - - + + - - - - + - - - + + should be equal to 3.2.0. - - + - - - + version 3.2.0. +
-

Product

-

Algorithm of checking

-

Preliminary steps before launching
+

Product

+

Algorithm of checking

+

Preliminary steps before launching
the installation procedure

-

Notes

+

Notes

gcc 3.4.1ver=`gcc +
gcc 3.4.1ver=`gcc -dumpversion` -

-

ver - should be 3.4.1.
-It is recommended to use native gcc on Mandrake 10.1.
tcl 8.4.51) + +

-

It is recommended to use the native + gcc for Mandrake 10.1.
tcl 8.4.51) check if TCLHOME variable is set
2) existence of tclsh8.4
3) existence of wish8.4
4) existence of libtcl8.4.so
5) existence of libtk8.4.so		set TCLHOME +set TCLHOME if you have a preinstalled version of tcl.
add a directory where libraries can be found to the LD_LIBRARY_PATH		Unfortunately there is no strict +Unfortunately there is no strict way to check the tcl version number.
-It is recommended to use native tcl/tk on Mandrake 10.1.
boost 1.31.01) check if +boost 1.31.01) check if BOOSTDIR variable is set.
2) ver=`egrep 'BOOST_VERSION [0-9]+' ${BOOSTDIR}/boost/version.hpp | sed 's/.*BOOST_VERSION \([0-9]\+\)/\1/g'`		set BOOSTDIR if +set BOOSTDIR if you have a preinstalled version of boostwe use file version.hpp in the boost distribution to get +we use file version.hpp in the boost distribution to get the version information.
ver should be equal to 103100.
Open CASCADE 5.2.31) +
Open CASCADE +

Technology 6.1

1) check if CASROOT variable is set
2) ver_major=`grep "!define OCC_VERSION_MAJOR" ${CASROOT}/inc/Standard_Version.hxx @@ -585,267 +598,248 @@ ver should be equal to 103100.
set CASROOT +set CASROOT if you have a preinstalled version of Open CASCADECASCADE's Standard_Version.hxx file - provides the version information.
-ver should be equal to 5.2.
-
-Unfortunately it is impossible to define the release version number. Instead - we check if libStdPlugin.so library exists: it is introduced in OpenCASCADE - since version 5.2.2.
Python 2.3.41) +Open CASCADE's Standard_Version.hxx + file provides the version information.
+ver should be equal to 6.1.
Python 2.3.41) PYTHONHOME variable should be set
2) isPython=`which python`
3) ver=`python -V`		set PYTHONHOME +set PYTHONHOME to root Python distribution folder;
add the directory where python can be found to the PATH variable		Python should exist and ver +Python should exist and ver should be equal to 2.3.4
-It is recommended to use native Python on Mandrake 10.1.
Swig 1.3.24ver=`swig +
Swig 1.3.24ver=`swig -version 2>&1 | grep -i version | awk '{ print $3 }' | sed -e 's/^\([0-9.]*\)\(.*\)/\1/'`add the directory where swig binary +add the directory where swig binary can be found to the PATH variableSwig should exist and ver +Swig should exist and ver should be equal to 1.3.24.
Qt 3.3.31) +
Qt 3.3.31) QTDIR variable should be set.
2) ver=`grep "QT_VERSION_STR" ${QTDIR}/include/qglobal.h | sed -e 's%^#define QT_VERSION_STR\([[:space:]]*\)%%g' -e 's%\"%%g'`		set QTDIR +set QTDIR if you have a preinstalled version of qtQt's qglobal.h file provides version +Qt's qglobal.h file provides version information: ver should be equal - to 3.0.5.
-It is recommended to use native Qt on Mandrake 10.1.
msg2qm (Qt 3.3.3 compatible)MSG2QM_ROOT +
msg2qm (Qt 3.3.3 compatible)MSG2QM_ROOT variable should be set.set  MSG2QM_ROOT +set  MSG2QM_ROOT if you have preinstalled version of msg2qm toolmsg2qm is a Qt tool used to convert +msg2qm is a Qt tool used to convert text *.po files to *.qm resource files. Unfortunately this tool is not included in the Qt distribution and is provided only in its sources package. We distribute this tool with the Installation Wizard.
In addition there is no way to check the version number of msg2qm tool.
Qwt 4.2.0/0.4.21) +
Qwt 4.2.0/0.2.41) QWTHOME variable should be set.
2) check if libqwt.so.4.2.0 exists		set  QWTHOME +set  QWTHOME if you have a preinstalled version of qwtUnfortunately there is no strict +Unfortunately there is no strict way to check the qwt version number.
We try to find libqwt.so.4.2.0 in the ${QWTHOME}/lib folder. 
Hdf 5-1.6.31) +
Hdf 51.6.31) HDF5HOME variable should be set.
2) existence of libhdf5.so.0.0.0
3) existence of libhdf5.settings
4) ver=`grep "HDF5 Version:" ${HDF5HOME}/lib/libhdf5.settings | awk '{print $3}'`		set HDF5HOME +set HDF5HOME if you have a preinstalled version of hdfWe try to find libhdf5.so.0.0.0 and +We try to find libhdf5.so.0.0.0 and libhdf5.settings in ${HDF5HOME}/lib folder.
File libhdf5.settings contains the following version information:
HDF5 Version: 1.6.3
Med 2.2.21) +
Med 2.2.31) MED2HOME variable should be set.
2) existence of libmed.so.1.0.1		set MED2HOME +set MED2HOME if you have a preinstalled version of medUnfortunately there is no strict +Unfortunately there is no strict way to check the med version number.
We try to find libmed.so.1.0.1 in ${MED2HOME}/lib folder.
If you have a problem with the preinstalled version of med, please, reinstall it.
Vtk 4.2.61) +
Vtk 4.2.61) VTKHOME variable should be set.
2) existence of libvtkCommon.so		set VTKHOME +set VTKHOME if you have a preinstalled version of vtkUnfortunately there is no strict +Unfortunately there is no strict way to check the VTK version number.
We try to find libvtkCommon.so in ${VTKHOME}/lib/vtk folder.
If you have a problem with the preinstalled version of vtk, please, reinstall it.
Netgen 4.3NETGENROOT variable +
Netgen 4.5NETGENROOT variable should be set. set NETGENROOT if +set NETGENROOT if you have a preinstalled version of Netgen.Unfortunately we can't find anything about netgen version.
+		Unfortunately we can't find anything about NETGEN version.
We just check if the NETGENROOT - environment varible is set.
OmniORB 4.0.5,
+
OmniORB 4.0.5,
OmniORBpy 2.5,
OmniNotify 2.1		1) +1) OMNIORBDIR variable should be set.
2) existence of libomniORB4.so.0.5
-3) existence of _omnipymodule.so.2.4
+3) existence of _omnipymodule.so.2.5
4) existence of libCOSNotify4.so.0.1
5) existence of notifd		set OMNIORBDIR +set OMNIORBDIR if you have a preinstalled version of omniWe try to find several omni libraries +We try to find several omni libraries and binaries in the ${OMNIORBDIR}/lib and ${OMNIORBDIR}/bin directories.
Numeric 23.7ver=`python +
Numeric 23.7ver=`python -c 'import Numeric; print Numeric.__version__' 2>/dev/null`add the directory where you +add the directory where you have the preinstalled version of Numeric package to your PYTHONHOME variableIf you have problem with the preinstalled +If you have problem with the preinstalled version of Numeric 23.7, please, reinstall it.
Sip 4.11) +
Sip 4.11) SIPDIR variable should be set.
2) ver=`${SIPDIR}/sip -V | awk '{print $1}'`		set SIPDIR +set SIPDIR to the directory where you have sip preinstalledver +ver should be equal to 4.1.
PyQt 3.131) +
PyQt 3.131) PYQTDIR variable should be set.
2) existence of qt.so library		set PYQTDIR +set PYQTDIR to the directory where you have PyQt preinstalledUnfortunately we can't exactly check +Unfortunately we can't exactly check the PyQt version number.
We just try to find qt.so in ${PYQTDIR}. -
HappyDoc 2.11) - existence of happydoc
-2) ver=`happydoc | grep - "HappyDoc version 2.1"`		add the directory where you have - HappyDoc installed to your PATH - variable.We try to find happydoc in ${PATH}.
-ver should not be empty.
-
-Note: this product is not obligatory for SALOME compilation.
Doxygen 1.3.71) + +

Note that PyQt officially doesn't support Qt 3.3.3, but nevertheless + it can be used.

Doxygen 1.4.61) existence of doxygen
2) existence of doxytag
3) existence of doxywizard
4) ver=`doxygen --version`		add the directory where you have +add the directory where you have doxygen binaries preinstalled to the  PATH variable.doxygen, doxytag, doxywizard binaries +doxygen, doxytag, doxywizard binaries should exist; ver should be equal - to 1.3.7.
-
-If you have problem with the preinstalled version of doxygen, please, reinstall + to 1.4.6.
+If you have problems with the preinstalled version of doxygen, reinstall it.
-
-It is recommended to use native doxygen on Mandrake 10.1.
Graphviz 2.2.11) +
Graphviz 2.2.11) existence of dot binary.
2) ver=`dot -V 2>&1 | awk '{print $3}'`		add the graphviz bin directory to +add the graphviz bin directory to the PATH environment variableWe try to find dot program in the +We try to find dot program in the ${PATH}.
ver should be equal to 2.2.1.
MODULE +
MODULE binaries
(where MODULE = KERNEL, GUI, GEOM, ...)		1) +1) MODULE_ROOT_DIR variable should be set
2) existence of VERSION file
3) ver=`cat ${MODULE_ROOT_DIR}/bin/salome/VERSION | awk -F: '{print $NF}' | tr -d '[:space:]'`		set MODULE_ROOT_DIR +set MODULE_ROOT_DIR if you have preinstalled binaries of MODULE - version 3.0.0.MODULE + version 3.2.0.MODULE binaries should exist and ver - should be equal to 3.0.0.
MODULE +
MODULE sources
(where MODULE = KERNEL, GUI, GEOM, ...)		1) +1) existence of MODULE_SRC_DIR
2) existence of VERSION file
3) ver=`cat ${MODULE_SRC_DIR}/bin/VERSION | awk -F: '{print $NF}' | tr -d '[:space:]'`		set MODULE_SRC_DIR +set MODULE_SRC_DIR if you have preinstalled sources of MODULE - version 3.0.0.MODULE - sources should exist and ver should be equal to 3.0.0.
MODULE + sources should exist and ver should be equal to 3.2.0.

 

 

-

For native products the installation +

For native products the installation procedure sets proper environment variables itself, and you do not need to set such variables like, e.g. TCLHOME or PYTHONHOME.
@@ -861,8 +855,8 @@ If you have native products installed to directories different from default

 

-

For some native products (e.g. gcc, Python) the +

For some native products (e.g. gcc, Python) the rules of version checking are not so strict as described in the table. Only major and minor version numbers should coincide with the prerequisite. Release number can be larger. This is done to give a possibility to use @@ -915,13 +909,16 @@ For native products (like gcc, tcl, etc...) the installation etc., depending on the product).

In any case you may edit salome.* files after the installation - procedure finishes, as you want.
 

+ procedure finishes, as you want.
+ 

-

Note: as it was mentioned above - there are two more environment files which are generated by the installation - procedure: env_products.csh and env_products.sh. These files can be found - in the target installation root directory.

+

Note: as it was mentioned + above there are two more environment + files which are generated by the installation procedure: env_products.csh + and env_products.sh. These files can be found in the target installation + root directory.

 

@@ -943,9 +940,10 @@ For native products (like gcc, tcl, etc...) the installation configuration file.
XML tags are in bold blue, optional sections/tags are in brackets.

-

<document>
+

<document> +
    [ <config

    -
  • version: Installation - Wizard version number;
    • + color=#000000>version: + Installation Wizard version number;     -
  • caption: Installation Wizard main window title - - if this string contains the '%1' text - the title will contain a version - number in this place (see above);
    • +
  • caption: Installation + Wizard main window title - if this string contains the '%1' text - the + title will contain a version number in this place (see above);
    • -
  • copyright: Installation - Wizard copyright information (appears on the first page of the program);
    • + color=#000000>copyright: + Installation Wizard copyright information (appears on the first page of + the program);     -
  • license: Installation - Wizard license information (appears on the first page of the program);
    • + color=#000000>license: + Installation Wizard license information (appears on the first page of + the program); -
  • os: Contains directory - name (relative from ./Products/BINARIES) where the Installation Wizard - should search precompiled binaries packages. If this tag is skipped, binaries - are implied to be in the ./Products/BINARIES directory.
    • + color=#000000>os: + Contains directory name (relative from ./Products/BINARIES) where the + Installation Wizard should search precompiled binaries packages. If this + tag is skipped, binaries are implied to be in the ./Products/BINARIES + directory.
-

<path> section

+

<path> section

This is an optional section - it contains default directories.
    -
  • targetdir: Starting target - directory - path to the directory where products should be installed;
    • + color=#000000>targetdir: + Starting target directory - path to the directory where products should + be installed; -
  • tempdir: Starting temp - directory - path to the directory for the temporary files.
    • + color=#000000>tempdir: + Starting temp directory - path to the directory for the temporary files.
-

<product> section

+

<product> section

This section describes the products that are to be installed with the Installation Wizard. Products appear in the products tree and are installed in the @@ -1102,82 +1111,96 @@ This section describes the products that are to be installed with the Installati
    -
  • name: Name of the product;
    • + color=#000000>name: + Name of the product; -
  • version: Version of the - product;
    • + color=#000000>version: + Version of the product; -
  • description: Description - of the product (optional);
    • + color=#000000>description: + Description of the product (optional); -
  • context: Context of the - product (optional); the possible values are 'salome sources', 'salome - binaries' and 'prerequisite';
    • + color=#000000>context: + Context of the product (optional); the possible values are 'salome + sources', 'salome binaries' and 'prerequisite'; -
  • supported: Supported modes - of installation, should contain one or more of the following options, - separated by a comma: install sources, install binaries, + color=#000000>supported: + Supported modes of installation, should contain one or more of the following + options, separated by a comma: install sources, install binaries, use native. The Installation script should contain corresponding functions for each of supported installation modes;
    • -
  • install: Default (starting) - installation mode;
    • + color=#000000>install: + Default (starting) installation mode; -
  • disable: If this flag - has 'true' value, the corresponding product will not appear in the list - of products tree and will not be installed;
    • + color=#000000>disable: + If this flag has 'true' value, the corresponding product will not appear + in the list of products tree and will not be installed; -
  • pickupenv: This flag points that the pickup - environment procedure should be performed for this module. If this flag - is equal to true,  salome.sh and salome.csh files will  - be created in the product's installation directory. Usually this option - is set to true for SALOME KERNEL module sources and the binaries package. - This is an optional key, the default value is false.
    • +
  • pickupenv: This + flag points that the pickup environment procedure should be performed + for this module. If this flag is equal to true,  salome.sh + and salome.csh files will  be created in the product's installation + directory. Usually this option is set to true for SALOME KERNEL module + sources and the binaries package. This is an optional key, the default + value is false.
    • -
  • dependancies: list of - prerequisite products, which are necessary to build this product, separated - by a comma;
    • + color=#000000>dependancies: + list of prerequisite products, which are necessary to build this product, + separated by a comma; -
  • installdiskspace: Total - amount of space (integer, in Kbytes), which the product occupies on the - hard drive after the installation;
    • + color=#000000>installdiskspace: + Total amount of space (integer, in Kbytes), which the product occupies + on the hard drive after the installation; -
  • temporarydiskspace: Disk - space (integer, in Kbytes) for the temporary files, which are necessary + color=#000000>temporarydiskspace: + Disk space (integer, in Kbytes) for the temporary files, which are necessary to build the product from the sources;
    • -
  • script: Installation script - name. This script is in charge of installation of the product. It is called - when necessary from the main program. See the next - section for more information.
    • + color=#000000>script: + Installation script name. This script is in charge of installation of + the product. It is called when necessary from the main program. See the + next section for more information.
  -

If you add new products +

If you add new products to be installed with the Installation Wizard, you should also provide the installation script for this product. See the next section for more details.

@@ -1204,14 +1227,16 @@ File common.sh contains some service functions which can be used
    -
  • check_version():  This function allows - to check the version of the product already installed on the computer. - It should try to find the product (native or preinstalled in the target - directory) and check it version. This helps to avoid unnecessary reinstallation. - This is internal function and is not called
    • +
  • check_version():  + This function allows to check the version of the product already installed + on the computer. It should try to find the product (native or preinstalled + in the target directory) and check it version. This helps to avoid unnecessary + reinstallation. This is internal function and is not called
    • -
  • try_native()try_native(): This function is called when @@ -1222,46 +1247,52 @@ File common.sh contains some service functions which can be used function). If you do not provide the native mode installation, you can omit this function.
    • -
  • install_source(): This - function is called when the 'install sources' installation mode - is selected by the user. The function is responsible for the building + color=#000000>install_source(): + This function is called when the 'install sources' installation + mode is selected by the user. The function is responsible for the building of the product from the sources package. It should create the environment for the product in the temporary directory (see also the description of print_env() function). If you do not provide the sources mode installation, you can omit this function
    • -
  • install_binary(): This - function is called when the 'install binaries' installation mode - is selected by the user. The function is responsible for the extracting + color=#000000>install_binary(): + This function is called when the 'install binaries' installation + mode is selected by the user. The function is responsible for the extracting the product from the binaries package. Should create environment for the product in the temporary directory (see also the description of print_env() function). If you do not provide the binaries mode installation, you can omit this function.
    • -
  • try_preinstalled(): This - function is called when the 'not install' installation mode is - selected by the user. In this case the script should inspect the target - directory to try to find the already preinstalled product, pick up and - check the environment from there. See here +
  • try_preinstalled(): + This function is called when the 'not install' + installation mode is selected by the user. In this case the script should + inspect the target directory to try to find the already preinstalled product, + pick up and check the environment from there. See here for more details.
    • -
  • print_env(): This function - is in charge of the environment script creation. It should create a file - with the name env_<product_name>.sh in the temporary - directory and then copy it into the product installation directory. The - file should contain all necessary environment variables settings for the - product. It will be collected during the 'pick-up-environment' procedure.
    • +
  • print_env(): + This function is in charge of the environment script creation. It should + create a file with the name env_<product_name>.sh + in the temporary directory and then copy it into the product installation + directory. The file should contain all necessary environment variables + settings for the product. It will be collected during the 'pick-up-environment' + procedure.
    • -
  • pickup_env(): This procedure corresponds to - the pickupenv tag of the configuration xml file (see previous section). - Should call the make_env procedure to perform the pick-up environment - procedure for the product.
    • +
  • pickup_env(): This + procedure corresponds to the pickupenv tag of the configuration + xml file (see previous section). Should call the make_env procedure + to perform the pick-up environment procedure for the product.
common.sh contains some service functions which can be used

 

-

med-2.2.2.sh install_binary /tmp/work ./Products/BINARIES/Mandrake10.1 - /usr/salome 'gcc Hdf' med

+

med-2.2.2.sh install_binary + /tmp/work ./Products/BINARIES/Mandrake10.1 /usr/salome 'gcc Hdf' med +

-

Copy the created script into the <Install_Wizard_root_directory>/config_files diff --git a/doc/salome/gui/GUI/kernel/running_salome_pro.htm b/doc/salome/gui/GUI/kernel/running_salome_pro.htm index 3f0738ab4..7b1f1c070 100755 --- a/doc/salome/gui/GUI/kernel/running_salome_pro.htm +++ b/doc/salome/gui/GUI/kernel/running_salome_pro.htm @@ -27,23 +27,24 @@ p.whs10 { margin-left:40px; } p.whs11 { margin-left:40px; font-style:normal; color:#000000; font-weight:normal; font-family:'Times New Roman' , serif; } ul.whs12 { list-style:disc; } table.whs13 { x-cell-content-align:top; width:96.029%; border-left-style:Solid; border-left-width:1px; border-right-style:Solid; border-right-width:1px; border-top-style:Solid; border-top-width:1px; border-bottom-style:Solid; border-bottom-width:1px; border-left-color:#c0c0c0; border-right-color:#c0c0c0; border-top-color:#c0c0c0; border-bottom-color:#c0c0c0; border-spacing:0px; } -col.whs14 { width:214px; } -col.whs15 { width:390px; } +col.whs14 { width:645px; } +col.whs15 { width:421px; } tr.whs16 { x-cell-content-align:top; height:41px; } -td.whs17 { width:214px; padding-right:10px; padding-left:10px; background-color:#400080; border-left-color:#c0c0c0; border-top-color:#c0c0c0; border-top-style:Solid; border-bottom-color:#c0c0c0; border-bottom-width:1px; border-bottom-style:Solid; border-right-color:#c0c0c0; border-right-width:1px; border-right-style:Solid; border-left-width:1px; border-left-style:Solid; border-top-width:1px; } +td.whs17 { padding-right:10px; padding-left:10px; background-color:#400080; border-left-color:#c0c0c0; border-top-color:#c0c0c0; border-top-style:Solid; border-bottom-color:#c0c0c0; border-bottom-width:1px; border-bottom-style:Solid; border-right-color:#c0c0c0; border-right-width:1px; border-right-style:Solid; border-left-width:1px; border-left-style:Solid; border-top-width:1px; } p.whs18 { color:#ffffff; } -td.whs19 { width:390px; padding-right:10px; padding-left:10px; background-color:#400080; border-top-color:#c0c0c0; border-top-style:Solid; border-right-color:#c0c0c0; border-right-style:Solid; border-bottom-color:#c0c0c0; border-bottom-width:1px; border-bottom-style:Solid; border-top-width:1px; border-right-width:1px; } -td.whs20 { width:214px; padding-right:10px; padding-left:10px; border-left-color:#c0c0c0; border-bottom-color:#c0c0c0; border-bottom-width:1px; border-bottom-style:Solid; border-right-color:#c0c0c0; border-right-width:1px; border-right-style:Solid; border-left-width:1px; border-left-style:Solid; } -td.whs21 { width:390px; padding-right:10px; padding-left:10px; border-right-color:#c0c0c0; border-right-style:Solid; border-bottom-color:#c0c0c0; border-bottom-width:1px; border-bottom-style:Solid; border-right-width:1px; } -td.whs22 { width:214px; padding-right:10px; padding-left:10px; border-left-color:#c0c0c0; border-bottom-color:#c0c0c0; border-bottom-style:Solid; border-right-color:#c0c0c0; border-right-width:1px; border-right-style:Solid; border-left-width:1px; border-left-style:Solid; border-bottom-width:1px; } -td.whs23 { width:390px; padding-right:10px; padding-left:10px; border-right-color:#c0c0c0; border-right-style:Solid; border-bottom-color:#c0c0c0; border-bottom-style:Solid; border-bottom-width:1px; border-right-width:1px; } -td.whs24 { width:214px; padding-right:10px; padding-left:10px; border-left-style:Solid; border-left-width:1px; border-left-color:#c0c0c0; border-right-style:Solid; border-right-width:1px; border-right-color:#c0c0c0; border-bottom-width:1px; border-bottom-style:Solid; border-bottom-color:#c0c0c0; } -td.whs25 { width:390px; padding-right:10px; padding-left:10px; border-right-width:1px; border-right-style:Solid; border-right-color:#c0c0c0; border-bottom-width:1px; border-bottom-style:Solid; border-bottom-color:#c0c0c0; } -td.whs26 { width:214px; padding-right:10px; padding-left:10px; border-left-color:#c0c0c0; border-left-width:1px; border-left-style:Solid; border-right-color:#c0c0c0; border-right-width:1px; border-right-style:Solid; border-bottom-color:#c0c0c0; border-bottom-style:Solid; border-bottom-width:1px; } -td.whs27 { width:390px; padding-right:10px; padding-left:10px; border-right-color:#c0c0c0; border-right-style:Solid; border-right-width:1px; border-bottom-color:#c0c0c0; border-bottom-style:Solid; border-bottom-width:1px; } -p.whs28 { font-weight:bold; margin-left:0px; font-family:'Courier New' , monospace; background-image:url('../texture_horiz_ltbluebubbles.jpg'); } -p.whs29 { font-family:'Times New Roman' , serif; margin-left:80px; } -p.whs30 { font-family:'Courier New' , monospace; margin-left:0px; } +td.whs19 { padding-right:10px; padding-left:10px; background-color:#400080; border-top-color:#c0c0c0; border-top-style:Solid; border-right-color:#c0c0c0; border-right-style:Solid; border-bottom-color:#c0c0c0; border-bottom-width:1px; border-bottom-style:Solid; border-top-width:1px; border-right-width:1px; } +td.whs20 { padding-right:10px; padding-left:10px; border-left-color:#c0c0c0; border-bottom-color:#c0c0c0; border-bottom-width:1px; border-bottom-style:Solid; border-right-color:#c0c0c0; border-right-width:1px; border-right-style:Solid; border-left-width:1px; border-left-style:Solid; } +td.whs21 { padding-right:10px; padding-left:10px; border-right-color:#c0c0c0; border-right-style:Solid; border-bottom-color:#c0c0c0; border-bottom-width:1px; border-bottom-style:Solid; border-right-width:1px; } +td.whs22 { padding-right:10px; padding-left:10px; border-left-color:#c0c0c0; border-bottom-color:#c0c0c0; border-bottom-style:Solid; border-right-color:#c0c0c0; border-right-width:1px; border-right-style:Solid; border-left-width:1px; border-left-style:Solid; border-bottom-width:1px; } +p.whs23 { font-weight:bold; } +td.whs24 { padding-right:10px; padding-left:10px; border-right-color:#c0c0c0; border-right-style:Solid; border-bottom-color:#c0c0c0; border-bottom-style:Solid; border-bottom-width:1px; border-right-width:1px; } +td.whs25 { padding-right:10px; padding-left:10px; border-left-style:Solid; border-left-width:1px; border-left-color:#c0c0c0; border-right-style:Solid; border-right-width:1px; border-right-color:#c0c0c0; border-bottom-width:1px; border-bottom-style:Solid; border-bottom-color:#c0c0c0; } +td.whs26 { padding-right:10px; padding-left:10px; border-right-width:1px; border-right-style:Solid; border-right-color:#c0c0c0; border-bottom-width:1px; border-bottom-style:Solid; border-bottom-color:#c0c0c0; } +td.whs27 { padding-right:10px; padding-left:10px; border-left-color:#c0c0c0; border-left-width:1px; border-left-style:Solid; border-right-color:#c0c0c0; border-right-width:1px; border-right-style:Solid; border-bottom-color:#c0c0c0; border-bottom-style:Solid; border-bottom-width:1px; } +td.whs28 { padding-right:10px; padding-left:10px; border-right-color:#c0c0c0; border-right-style:Solid; border-right-width:1px; border-bottom-color:#c0c0c0; border-bottom-style:Solid; border-bottom-width:1px; } +p.whs29 { font-weight:bold; margin-left:0px; font-family:'Courier New' , monospace; background-image:url('../texture_horiz_ltbluebubbles.jpg'); } +p.whs30 { font-family:'Times New Roman' , serif; margin-left:80px; } +p.whs31 { font-family:'Courier New' , monospace; margin-left:0px; } --> @@ -257,33 +298,30 @@ if ((navigator.appName == "Netscape") && (parseInt(navigator.appVersion) == 4))

 

-

+

If the runSalome.py script is launched without prompting any options, they will be taken by default - from the xml file salome.launch, - which has been automatically created in your home directory: HOME/.salome/. + from the file SalomeApp.xml + (SALOME/GUI/share/salome/resources/SalomeApp.xml). If you are constantly launching SALOME with some specific options which are different from the defaults, you can edit this file according to your requirements. So the next time you run SALOME, you won't have to enter these numerous command console options.    

-

 

+

 

-

+

Related Topics

-

 

+

 

-

 

+

 

-

 

+