DISTCLEANFILES = a.out aclocal.m4 configure
-salomeinclude_DATA=GUI_version.h
+salomeinclude_DATA = GUI_version.h
-EXTRA_DIST+= \
+EXTRA_DIST += \
build_configure \
clean_configure \
LICENCE
usr_docs:
(cd doc && $(MAKE) $(AM_MAKEFLAGS) usr_docs)
-docs:usr_docs
+docs: usr_docs
dev_docs:
(cd doc && $(MAKE) $(AM_MAKEFLAGS) dev_docs)
include $(top_srcdir)/adm_local/unix/make_common_starter.am
SUBDIRS = config_files
-
-# this is for LIGHT module compatibility
-dist_admlocalunix_DATA=make_conclude.in
\ No newline at end of file
#
# Standard directory for installation
-salomeincludedir = $(includedir)/@PACKAGE@
-libdir = $(prefix)/lib@LIB_LOCATION_SUFFIX@/@PACKAGE@
-bindir = $(prefix)/bin/@PACKAGE@
+salomeincludedir = $(includedir)/salome
+libdir = $(prefix)/lib@LIB_LOCATION_SUFFIX@/salome
+bindir = $(prefix)/bin/salome
salomescriptdir = $(bindir)
+salomepythondir = $(pythondir)/salome
+salomepyexecdir = $(pyexecdir)/salome
# Directory for installing idl files
-salomeidldir = $(prefix)/idl/@PACKAGE@
+salomeidldir = $(prefix)/idl/salome
# Directory for installing resource files
-salomeresdir = $(prefix)/share/@PACKAGE@/resources/@MODULE_NAME@
+salomeresdir = $(prefix)/share/salome/resources/@MODULE_NAME@
# Directories for installing admin files
-admlocaldir = $(prefix)/adm_local
-admlocalunixdir = $(admlocaldir)/unix
-admlocalm4dir = $(admlocaldir)/unix/config_files
+admlocaldir = $(prefix)/adm_local
+admlocalunixdir = $(admlocaldir)/unix
+admlocalm4dir = $(admlocaldir)/unix/config_files
# Shared modules installation directory
-sharedpkgpythondir =$(pkgpythondir)/shared_modules
+sharedpkgpythondir = $(salomepythondir)/shared_modules
# Documentation directory
-docdir = $(datadir)/doc/@PACKAGE@
+docdir = $(datadir)/doc/salome
# common rules
-# moc-files generation
+# meta object implementation files generation (moc)
%_moc.cxx: %.h
$(MOC) $< -o $@
-# qm-files generation
+# translation (*.qm) files generation (lrelease)
%.qm: resources/%.ts
$(LRELEASE) $< -qm $@
-# resource files generation
+# resource files generation (qrcc)
qrc_%.cxx: %.qrc
$(QRCC) $< -o $@ -name $(*F)
-EXTRA_DIST=$(MOC_FILES:%_moc.cxx=%.h) $(QRC_FILES:qrc_%.cpp=%.qrc) $(nodist_salomeres_DATA:%.qm=resources/%.ts)
+# extra distributed files
+EXTRA_DIST = $(MOC_FILES:%_moc.cxx=%.h) $(QRC_FILES:qrc_%.cxx=%.qrc) $(nodist_salomeres_DATA:%.qm=resources/%.ts)
+# customize clean operation
mostlyclean-local:
rm -f @builddir@/*_moc.cxx
rm -f @builddir@/*.qm
+ rm -f @builddir@/qrc_*.cxx
# tests
tests: unittest
include $(top_srcdir)/adm_local/unix/make_common_starter.am
-#
-# ===============================================================
-# Files to be installed
-# ===============================================================
-#
-
-# These files are data, module or lib files
-nodist_salomescript_DATA= VERSION
-
-EXTRA_DIST+= VERSION.in
+# non-distributed files
+nodist_salomescript_DATA = VERSION
-# These files are executable scripts
-dist_salomescript_SCRIPTS=\
- runLightSalome.csh \
+# distributed files
+dist_salomescript_SCRIPTS = \
+ runLightSalome.csh \
runLightSalome.sh
# Modified by : Mikhail PONIKAROV (OCN) - autotools usage
#
-AC_INIT([Salome2 Project GUI module], [5.0.0], [webmaster.salome@opencascade.com], [salome])
+AC_INIT([Salome2 Project GUI module], [5.0.0], [webmaster.salome@opencascade.com], [SalomeGUI])
AC_CONFIG_AUX_DIR(salome_adm/unix/config_files)
AC_CANONICAL_HOST
AC_CANONICAL_TARGET
AM_CONDITIONAL(ENABLE_SALOMEOBJECT, [test "$DISABLE_SALOMEOBJECT" = no])
AM_CONDITIONAL(ENABLE_QXGRAPHVIEWER, [test "$DISABLE_QXGRAPHVIEWER" = no])
-echo
-echo ---------------------------------------------
-echo copying resource files, shell scripts, and
-echo xml files
-echo ---------------------------------------------
-echo
-
-
-dnl copy shells and utilities contained in the bin directory
-dnl excluding .in files (treated in AC-OUTPUT below) and CVS
-dnl directory
-
-mkdir -p bin/salome
-cd bin/salome
-
-for i in $ROOT_SRCDIR/bin/*
-do
- local_bin=`echo $i | sed -e "s,$ROOT_SRCDIR,.,"`
- case "$local_bin" in
- *.in | *~) ;;
- ./bin/CVS | ./bin/salome) ;;
- *) $INSTALL $i . ; echo $local_bin ;;
- esac
-done
-cd $ROOT_BUILDDIR
-
echo
echo ---------------------------------------------
echo generating Makefiles and configure files
echo ---------------------------------------------
echo
-AC_OUTPUT_COMMANDS([ \
- chmod +x ./bin/*; \
- chmod +x ./bin/salome/*; \
-])
+#AC_OUTPUT_COMMANDS([ \
+# chmod +x ./bin/*; \
+# chmod +x ./bin/salome/*; \
+#])
# This list is initiated using autoscan and must be updated manually
# when adding a new file <filename>.in to manage. When you execute
./doc/Makefile \
./doc/salome/Makefile \
./doc/salome/gui/Makefile \
- ./doc/salome/gui/GUI/doxyfile \
+ ./doc/salome/gui/doxyfile \
./doc/salome/tui/Makefile \
- ./doc/salome/tui/GUI/doxyfile \
+ ./doc/salome/tui/doxyfile \
./src/Makefile \
./src/CASCatch/Makefile \
./src/Qtx/Makefile \
# $Header$
#
-SUBDIRS= salome
+SUBDIRS = salome
# $Header$
#
-SUBDIRS= tui gui
-SUBDIRSTUI= tui
-SUBDIRSGUI= gui
+SUBDIRS = tui gui
+SUBDIRSTUI = tui
+SUBDIRSGUI = gui
usr_docs:
@@SETX@; for d in $(SUBDIRSGUI); do \
+++ /dev/null
-#---------------------------------------------------------------------------
-# Project related configuration options
-#---------------------------------------------------------------------------
-PROJECT_NAME = "GUI Module Reference Manual v.@VERSION@"
-OUTPUT_DIRECTORY = ./
-CREATE_SUBDIRS = NO
-OUTPUT_LANGUAGE = English
-TAB_SIZE = 5
-
-#---------------------------------------------------------------------------
-# configuration options related to warning and progress messages
-#---------------------------------------------------------------------------
-QUIET = NO
-WARNINGS = YES
-
-#---------------------------------------------------------------------------
-#Input related options
-#---------------------------------------------------------------------------
-INPUT = @srcdir@/input
-FILE_PATTERNS = *.doc
-IMAGE_PATH = @srcdir@/images
-
-#---------------------------------------------------------------------------
-#HTML related options
-#---------------------------------------------------------------------------
-GENERATE_HTML = YES
-HTML_OUTPUT = ./
-HTML_HEADER = @srcdir@/static/header.html
-HTML_FOOTER = @srcdir@/static/footer.html
-#HTML_STYLESHEET = @srcdir@/static/doxygen.css
-TOC_EXPAND = YES
-DISABLE_INDEX = NO
-GENERATE_TREEVIEW = YES
-TREEVIEW_WIDTH = 300
-
-#---------------------------------------------------------------------------
-#LaTeX related option
-#---------------------------------------------------------------------------
-GENERATE_LATEX = NO
-
-#---------------------------------------------------------------------------
-#RTF related options
-#---------------------------------------------------------------------------
-GENERATE_RTF = NO
\ No newline at end of file
+++ /dev/null
-/*!
-
-\page about_salome_page About SALOME
-
-<ul>
-<li>\subpage intro_to_salome_page</li>
-<li>\subpage salome_architecture_page</li>
-<li>\subpage installing_salome_page "Installing SALOME"</li>
-<li>\subpage running_salome_page</li>
-</ul>
-
-*/
\ No newline at end of file
+++ /dev/null
-/*!
-
-\page creating_new_study_page Creating a new study
-
-Study is a document within GUI, an abstraction layer between actual
-document data (probably, remote data available through CORBA) and data
-presentation (in the Object Browser). It contains a tree of Data
-Object instances.
-
-<em>To create a new study:</em>
-
-\par
-From the main menu select <b>File > New</b> or in the standard toolbar
-click "New document" button.
-
-\image html newsticn.jpg ""New document" button"
-
-Your study will be created with default name \b Study1. In SALOME you
-can create several studies.
-
-In addition to it, you can create several windows with different
-activated viewers (VTK, OCC, Plot2d) for each study.
-
-<em>To create a new window for a definite study:</em>
-<ol>
-<li>Make your study \b active: maximize it (if it minimized) or click on
-the top control zone of the study window.
-</li>
-<li>\n From the main menu select <b>Window > New Window</b> and from the submenu
-choose the viewer, which will be activated in a new window.
-</li>
-</ol>
-
-The window for your study will be created with a default name \b Study1.
-
-*/
\ No newline at end of file
+++ /dev/null
-/*!
-
-\page displaying_studies_page Displaying studies
-
-Starting from SALOME version 3.0.0. you are able to work in a
-multi-desktop environment, which means that you can open as many
-studies as you need, place them wherever you wish on the desktop, in
-brief, work with Salome Platform like with a normal Windows
-application.
-\n Such windows as Object Browser and Python Console are dockable and
-also can be placed at any part of the desktop.
-\n Only one study window in representation area can be active. You can
-change their size and move any windows between representation
-areas. When an area becomes empty, it is not displayed.
-\n All windows are placed inside tabs where you can switch between
-them. If there are several windows (viewers) in your current study and
-you want to display more then one at the same time, you can split
-representation area into two parts, in horizontal or vertical
-direction, to create two representation areas with windows be placed
-in them. To do this, right-click on the tab and select <b>Split
-Vertically</b> or <b>Split Horizontally</b>.
-
-For example, on this screen-shot the active zone has been split
-horizontally to be able to work with OCC and VTK viewers
-simultaneously, the one of the windows was split again, at this time
-vertically to see Plot 2d graphs.
-
-\image html neo-view2.png
-
-*/
\ No newline at end of file
+++ /dev/null
-/*!
-
-\page editing_studies_page Editing studies
-
-\b SALOME has \b Copy/Paste functionality allowing to edit your study
-within a definite component:
-
-<em>To copy/paste a definite object:</em>
-\par
-In the main toolbar click "Copy"/"Paste" button or from the main menu
-choose <b>Edit > Copy/Paste</b> option.
-
-\image html copy-paste.jpg ""Copy" and "Paste" buttons"
-
-\n The availability of \b Copy/Paste operations depends on the module and
-the nature of an operation or an object, so if the module does not
-provide this functionality, it won't be available.
-
-*/
\ No newline at end of file
+++ /dev/null
-/*!
-
-\page geometry_preferences_page Geometry preferences
-
-In the \b Geometry module you can set preferences for visualisation of
-geometrical figures which can be used in later sessions with this
-module.
-
-\image html pref15.png
-
-\par
-For all color definitions click on the respective line to access to
-the \ref select_color_and_font_page "Select Color" dialog box.
-
-<ul>
-<li><b>General</b></li>
-<ul>
-<li><b>Default Display Mode</b> - allows to choose between wireframe
-or shading.<li>
-<li><b>Default Shading Color</b> - allows to select default shading
-color.<li>
-<li><b> Default Wireframe Color</b> - allows to select default
-wireframe color (to be applied to any lines not being free boundaries
-or isolated lines).<li>
-<li><b>Color of free boundaries</b> - allows to select default color for free boundaries.<li>
-<li><b>Color of edges, vectors and wires</b> - allows to select
-default color for edges, vectors and wires (isolated lines).<li>
-<li><b>Color of points</b> - allows to select default color for
-vertices.<li>
-<li><b>Color of isolines</b> - allows to select default color for
-isolines.<li>
-<li><b>Step Value for Spin Boxes</b> - allows to define the increment
-of values set in spin boxes.<li>
-</ul>
-</ul>
-
-<ul>
-<li><b>Marker of Points</b></li>
-<ul>
-<li><b>Type</b> - allows to select the symbol for representation of
-points (cross, asterisk, etc.).</li>
-<li><b>Size</b> - allows to define the size of the marker from 1
-(smallest) to 7 (largest).</li>
-</ul>
-</ul>
-
-*/
\ No newline at end of file
+++ /dev/null
-/*!
-
-\page getting_started_page Getting started
-
-When you start the SALOME Platform, the following initial desktop window appears:
-
-\image html view2.png
-
- In general, the SALOME platform is destined
-for performance of different numerical calculations and visualization
-of the resulting data. For that purpose, in the SALOME environment the
-following notion is used - \b Study.
-<br>Study represents a working document in which you can realize all
-operations connected with the SALOME functionality.
-<br>SALOME is a multi-study platform. It means that simultaneously you can
-work with several studies.
-
-\note To proceed working in SALOME you should create or open a new study.
-
-*/
\ No newline at end of file
+++ /dev/null
-/*!
-
-\page gui_module_page GUI module
-
-<ul>
-<li>\subpage introduction_to_gui_page</li>
-<li>\subpage getting_started_page</li>
-<li>\subpage salome_desktop_page</li>
-<li>\subpage study_management_page</li>
-<ul>
-<li>\ref creating_new_study_page</li>
-<li>\ref opening_studies_page</li>
-<li>\ref saving_and_closing_studies_page</li>
-<li>\ref editing_studies_page</li>
-<li>\ref displaying_studies_page</li>
-<li>\ref working_with_python_scripts_page</li>
-<li>\ref setting_study_properties_page</li>
-</ul>
-<li>\subpage using_object_browser_page</li>
-<li>\subpage using_find_tool_page</li>
-<li>\subpage using_registry_tool_page</li>
-<li>\subpage using_catalog_generator_page "Using Catalog Generator"</li>
-<li>\subpage viewers_page</li>
-<ul>
-<li>\ref occ_3d_viewer_page</li>
-<li>\ref vtk_3d_viewer_page</li>
-<li>\ref plot2d_viewer_page</li>
-</ul>
-<li>\subpage setting_preferences_page</li>
-<ul>
-<li>\ref setting_preferences_subpage</li>
-<li>\ref select_color_and_font_page</li>
-<li>\ref salome_preferences_page</li>
-<li>\ref geometry_preferences_page</li>
-<li>\ref mesh_preferences_page</li>
-<li>\ref postpro_preferences_page</li>
-</ul>
-</ul>
-
-*/
+++ /dev/null
-/*!
-
-\mainpage GUI Module Reference Documentation
-
-<ul>
-<li>\subpage introduction_page</li>
-<li>\subpage about_salome_page</li>
-<ul>
-<li>\ref intro_to_salome_page</li>
-<li>\ref salome_architecture_page</li>
-<li>\ref installing_salome_page</li>
-<li>\ref running_salome_page</li>
-</ul>
-<li>\subpage gui_module_page "GUI module"</li>
-<ul>
-<li>\ref introduction_to_gui_page</li>
-<li>\ref getting_started_page</li>
-<li>\ref salome_desktop_page</li>
-<li>\ref study_management_page</li>
-<ul>
-<li>\ref creating_new_study_page</li>
-<li>\ref opening_studies_page</li>
-<li>\ref saving_and_closing_studies_page</li>
-<li>\ref editing_studies_page</li>
-<li>\ref displaying_studies_page</li>
-<li>\ref working_with_python_scripts_page</li>
-<li>\ref setting_study_properties_page</li>
-</ul>
-</ul>
-<li>\ref using_object_browser_page</li>
-<li>\ref using_find_tool_page</li>
-<li>\ref using_registry_tool_page</li>
-<li>\ref using_catalog_generator_page "Using Catalog Generator"</li>
-<li>\ref viewers_page</li>
-<ul>
-<li>\ref occ_3d_viewer_page</li>
-<li>\ref vtk_3d_viewer_page</li>
-<li>\ref plot2d_viewer_page</li>
-</ul>
-<li>\ref setting_preferences_page</li>
-<ul>
-<li>\ref setting_preferences_subpage</li>
-<li>\ref select_color_and_font_page</li>
-<li>\ref salome_preferences_page</li>
-<li>\ref geometry_preferences_page</li>
-<li>\ref mesh_preferences_page</li>
-<li>\ref postpro_preferences_page</li>
-</ul>
-</ul>
-
-
-*/
+++ /dev/null
-/*!
-
-\page installing_salome_page SALOME Installation Wizard Help
-
-<hr>
-<ul>
-<li>\ref installing_products "Installing products with the Installation Wizard"
-<ul>
-<li>\ref gui_mode_install "GUI mode"
-<li>\ref batch_mode_install "Batch mode"
-<li>\ref environment_files "Environment files"
-</ul>
-<li>\ref notes_on_check "Notes on check products version procedure"
-<li>\ref pick_up_env "Pick up the environment"
-<li>\ref modifying_xml "Modifying XML configuration file"
-<li>\ref installation_scripts "Implementing installation scripts for the new products"
-<li>\ref finish_buttons "Customizing Readme page buttons"
-</ul>
-<hr>
-\anchor installing_products
-<h1>Installing products with the <em>Installation Wizard</em></h1>
-
-The Installation Wizard can be launched in two modes: \b GUI and \b
-batch.
-<br>The root directory of the Installation Wizard contains Python
-script \b runInstall. To run the Installation Wizard just type \b runInstall.
-in the terminal window:
-<br><br>[ python ] \b runInstall [options]
-
-Without options this script will launch the SALOME Installation
-Wizard in the default mode (GUI). \n The default installation settings
-can be overridden by using command line options. Each option has a
-short and a long notation:
-
-<b>-g / --gui</b>
-\par
-Runs the Installation Wizard in the GUI mode (this is the default
-mode).
-
-<b>-b / --batch</b>
-\par
-Runs the Installation Wizard in the terminal mode.
-
-<b>-f FILE / --file=FILE</b>
-\par
-The XML configuration file to be used by the Installation Wizard. If
-this option is not used then the installation script tries to define
-the \e Linux version and use the corresponding XML file if it exists. For
-examle, for <em>Linux Mandrake 10.1</em> the <b>config_Mandrake_10.1.xml</b> file
-will be used by default. If no appropriate file is found, the file
-<b>config.xml</b> will be used. This file refers to the basic target platform
-which is <em>Linux Mandrake 10.1</em> for SALOME 3.0 and newer. If <b>config.xml</b>
-file is not found either, a warning message box is shown (in GUI mode)
-or printed to the console (in batch mode) and the Installation Wizard
-quits.
-
-<b>-d DIR / --target=DIR</b>
-\par
-The target directory SALOME platform is to be installed to.
-If used, this option overrides the default target directory, given in
-the configuration XML file (usually <b>${HOME}/salome_\<version\></b>,
-see \ref modifying_xml "here" for more details).
-
-<b>-t DIR / --tmp=DIR</b>
-\par
-The directory, which should be used for temporary files. If given,
-this option overrides the default temporary directory, given in the
-configuration xml file (usually \b /tmp, see \ref modifying_xml "here"
-for more information).
-
-<b>-a / --all-from-sources</b>
-\par
-Forces all the products to be installed from sources (including all
-SALOME modules). If this option is used, all default installation
-modes for all products are ignored.
-\n This option is helpful when the user wants to install SALOME on the
-platform which is not officially supported. In this case, the user can
-try to run the SALOME Installation Wizard with the \b -a option in order
-to build all the products from sources.
-\n <b>Note, that this is a time-consuming operation which can take
-more than 24 hours depending on the computer.</b>
-
-<b>-h / --help</b>
-\par
-Prints help information on the Installation Wizard's use.
-
-<b>-v / --version</b>
-\par
-Prints version information (\b Note: this is the Installation Wizard's
-version number, not the number of SALOME platform version).
-
-The installation procedure supports different \em Linux platforms and
-installs various installation 3d-party prerequisite products which are
-required by SALOME platform. As it was mentioned above, the basic
-target platform for SALOME 3.0 and newer is <em>Linux Mandrake 10.1</em>.
-Use of configuration XML files gives a flexible way to modify the list
-of products to be installed by the Installation Wizard without
-changing the program source code. Just create your own XML
-configuration file and implement installation scripts for the
-prerequisite products you need and then use this XML file with the
-Installation Wizard. This can be done, for example, for some Linux
-platform which is not supported directly by the Installation
-Wizard. See \ref modifying_xml "Modifying XML configuration file" and
-\ref installation_scripts "Implementing installation scripts for the new products"
-sections for more information.
-
-<br>
-\anchor gui_mode_install
-<h2>GUI mode</h2>
-
-The <b>Installation Wizard</b> GUI has been developed using
-Trolltech's <b>Qt 3.0.5</b> toolkit. After launching the Installation
-Wizard in the GUI mode the wizard window is shown to the user. This
-wizard guides the user through several subsequent pages. To navigate
-between the pages use \em "Next" and \em "Back" buttons in the lower
-part of the wizard window. The \em "Cancel" button closes the wizard
-window and quits the installation procedure after the user's
-confirmation. The \em "Help" button opens an additional window to show
-help information.
-
-The first \em "Introduction" page is shown in \ref figure_1 "Figure 1".
-Skip this page by clicking \em "Next":
-
-\anchor figure_1
-\image html intropage.png
-\n <center><b>Figure 1:</b> "Introduction" page</center>
-
-In the second page you are proposed to enter the target directory
-where the SALOME platform should be installed to. You can also click
-<em>"Browse..."</em> and choose the destination folder using the standard
-browse directory dialog box.
-\n If the directory you want to install products to does not exist you
-are prompted to confirm directory creation. If you type a wrong
-directory path, or if you do not have write permissions
-for the directory you use, the corresponding message box is shown.
-
-You can also change the temporary directory (which is used to store
-temporary files required for the installation).
-\n In the bottom part of the window the total disk space required for
-the installation and for the temporary files is displayed (see below
-for more details).
-
-In the GUI mode the Installation Wizard provides two different options
-to install the SALOME platform: \b basic (default option) and
-\b advanced. In the \b basic mode the user should enter the target
-installation directory and temporary folder. All other installation
-options are taken from the XML configuration file (see \ref figure_2 "Figure 2"):
-
-\anchor figure_2
-\image html productpage1.png
-\n <center><b>Figure 2:</b> "Installation settings"</center>
-
-In addition, you have a choice to use "Install all products from
-sources" check box. If this option is turned on, all the products will
-be installed from the sources (using their own build procedures). This
-check box corresponds to the <b>--all-from-sources (-a)</b> option of
-the \b runInstall script (see \ref installing_products "here").
-
-\Note <b>Installation of all products from sources is a long-time
-operation.</b>
-
-To switch to the \b advanced option, click <em>"More..."</em> (see
-\ref figure_3 "Figure 3" ).
-
-In the advanced mode you have a possibility to select products to be
-installed. Each product can have several options of installation: you
-have a possibility to use the native product (provided with Linux
-distribution and installed in the system folders), install already
-precompiled binaries, build the product from sources or not install it
-at all. Available options and default option are taken from the XML
-configuration file. You can mark the products you want to install by
-clicking the corresponding radio-buttons in the list view in the left
-part of the page.
-\n Note, that some products may require some other pre-requisite
-products to be installed (or these prerequisite products should be
-already available on your computer). The installation procedure has a
-special feature to automatically mark these products in the list
-view. For example, in order to install \b PyQt it is necessary to have
-<b>gcc, Python, Qt</b> and \b Sip installed. Therefore all these
-products will also be turned on when you check on \b PyQt. This
-feature can be switched off by clicking the <em>"Automatic
-dependencies"</em> checkbox. Turn on this checkbox if you want all
-prerequisite products to be automatically checked when you select some
-product to be installed. Turn off this checkbox if you want to disable
-this feature.
-
-\anchor figure_3
-\image html productpage.png
-\n <center><b>Figure 3:</b> "Installation settings" page in the 'advanced' mode</center>
-
-If you want to use native products (like \b gcc, \b tcl, etc.), select <em>"use
-native"</em> option.
-\n Special button in the right part of the page - <em>"Unselect All"</em> -
-allows to reset quickly all products to the <em>"not install"</em> state.
-<br><br>
-There are also two checkboxes on this page: <em>"SALOME sources"</em>
-and <em>"SALOME binaries"</em>. These three-state checkboxes allow
-quick selecting/unselecting sources/binaries packages of SALOME
-modules for installation.
-<br><br>
-In addition, when some SALOME sources are selected, one more check box
-becomes available: <em>"Build SALOME sources"</em>. If this option is
-turned on, the selected SALOME modules will be built and installed
-from sources.
-
-\note <b>If this check box is turned on, the corresponding SALOME
-module binaries package installation is disabled, because of SALOME
-module sources and binaries packages conflict</b> (see \ref figure_4 "Figure 4" below).
-
-\anchor figure_4
-\image html productpage2.png
-\n <center><b>Figure 4:</b> "Build SALOME sources" check box
-usage</center>
-
-The box at the right side of the page displays the information about
-currently highlighted product: name, version and short description,
-required disk space, disk space required for temporary files, list of
-prerequisites (this information is provided in the XML file) and
-current user choice.
-<br><br>
-The <em>"Disk space required:"</em> field displays how much disk space
-on the hard drive is required for installation of selected products.
-
-\note <b>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.</b>
-
-The installation procedure uses a special directory to store temporary
-files. The <em>"Space for temporary files:"</em> field shows the information
-about required disk space on the hard drive for extracting and
-compiling the selected products. You can change the temporary
-directory - just type a path to the folder you want to use or click on
-the corresponding <em>"Browse..."</em> button.
-
-\note Actually, temporary files are not stored directly in the
-directory entered by the user. The Installation Wizard creates an
-additional folder in this directory named something like
-INSTALLWORK<b>XXXXX</b> where XXXXX is a unique number. This allows to launch
-several Installation Wizards simultaneously. This temporary directory
-is removed automatically when the installation finishes.
-
-The installation procedure also checks the available disk space. If
-there is not enough disk space on your hard drive you will see a
-corresponding error message box.
-
-\note <b>You are strongly recommended not to use directory names
-containing spaces</b>. Otherwise you can experience
-some troubles with the installation.
-
-To proceed further click <em>"Next"</em>. At this moment the program will make
-some tests to check installation settings: if there is enough disk
-space on the hard drive, check for native products installation,
-dependencies (prerequisites) for each product you have selected to be
-installed. If any test fails you will see the corresponding warning
-message box. Otherwise the wizard will proceed to the next page:
-
-\anchor figure_5
-\image html choicepage.png
-\n <center><b>Figure 5:</b> "Check your choice" page</center>
-
-This page summarizes the installation options you've made on the
-previous pages. You can check again your choice and change it if
-necessary by getting back to the previous page.
-\n When you are sure that everything is OK, click <em>"Next"</em> to
-follow to the \ref figure_6 "next page".
-
-\anchor figure_6
-\image html progresspage1.png
-\n <center><b>Figure 6:</b> "Installation progress" page</center>
-
-To start installation of the selected products click "Start". It
-launches the shell installation script and you will be able to see the
-output of the script in the dialog topmost frame. If any errors occur
-during the installation progress the corresponding messages will be
-printed to the log window in bold red font.
-
-It is possible to break the installation at any time by clicking
-"Stop". Then you can get back to the previous pages if you wish to
-change installation settings or restart installation by pressing again
-"Start" button.
-
-\note <b>In the current implementation it is not possible to resume
-the stopped installation process; it will be re-started from the very
-beginning.</b>
-
-\anchor figure_7
-\image html progresspage.png
-\n <center><b>Figure 7:</b> "Installation progress" page: installation in progress</center>
-
-The <em>"Installation Status"</em> frame window shows you the progress of
-installation. \c "Waiting" status means that installation of this product
-has not been started yet. The product currently being installed is
-marked as \c "Processing". All installed products have \c "Completed"
-status.
-
-You can abort installation and close the installation procedure using
-\em "Cancel" button.
-
-\note <b>This button sends the signal "SIGTERM" to the shell
-script. The script tries to clear all temporary files. The process of
-removing temporary files can take some time, so the installation
-wizard will wait 3 seconds before closing.</b>
-
-At the end of installation (all selected products have been installed
-successfully) you can go back to the previous pages to start a new
-installation or click \em "Next" to go the Readme page:
-
-\anchor figure_8
-\image html readmepage.png
-\n <center><b>Figure 8:</b> "Finish installation" page</center>
-
-In this page you can read important information about the Instalation
-Wizard itself and some tips: how to run and test SALOME or how to
-build SALOME from the sources. This is the contents of the README file
-which you can find in the root directory of the Installation Wizard.
-
-You can also launch SALOME Desktop from this page or read the Release
-Notes file by clicking on the corresponding buttons in the lower part
-of the page (see \ref modifying_xml "here" and \ref finish_buttons
-"here" for more information about customizing these buttons).
-
-<br>
-\anchor batch_mode_install
-<h2>Batch mode</h2>
-
-To launch the Installation Wizard in the batch mode use -\b b (--\b batch)
-parameter.
-\n In this mode the GUI wizard is not shown but all the installation
-status is displayed directly in the console. In the batch mode the
-user does not have a possibility to change installation settings which
-are given in the configuration file, except target and temporary
-directories which can be overridden by the corresponding command line
-options.
-\n The only exception is --\b all-from-sources (-\b a) option which enables
-special installation mode in which all the products (including SALOME
-modules) are installed from sources, ignoring the default mode defined
-in the XML configuration file (see \ref installing_products "here" for details).
-
-\anchor figure_9
-\image html batchmode.png
-\n <center><b>Figure 9:</b> Batch mode</center>
-
-<br>
-\anchor environment_files
-<h2>Environment files</h2>
-
-During the process of installation the script creates some environment
-files to simplify the procedure of launching SALOME. These shell
-scripts set all necessary environment variables for all products you
-have installed. To learn how installation scripts collects the
-environment, see \ref pick_up_env "here". These files are: \b
-salome.csh + \b salome.sh in the <b><em>KERNEL module sources</em></b>
-and <b><em>KERNEL module binaries</em></b> root directories and
-\b env_products.csh + \b env_products.sh and \b env_build.csh +
-\b env_build.sh in the target installation directory.
-
-\note there is some difference between these files: \b env_build.*
-files are optimized to be used for building SALOME modules from
-sources (see \b README file provided with the installation procedure
-on the CD). The \b env_products.* (and \b salome.*) files are
-optimized for SALOME launching. The behavior is defined by the
-environment variable \b ENV_FOR_LAUNCH which is set to \b 0 in
-env_build.* files and to \b 1 in env_products.* (salome.*) files.
-
-<br>
-<hr>
-\anchor notes_on_check
-<h2>Notes on <em>check products version</em> procedure</h2>
-
-Unfortunately there is no exact algorithm to identify the product
-version under Linux platform. The information in this section gives an
-idea how the version is checked for the native/preinstalled products
-(this information refers to the base platform <em>Linux Mandrake
-10.1</em>; and the same algorithms are used for other platforms).
-
-The general rule for all products is that the path to the binaries
-should be set via the \b PATH environment variable, path to the libraries
-should be set via the \b LD_LIBRARY_PATH variable and the python modules
-should be available via the \b PYTHONPATH variable.
-
-\note the information given in this section refers to the prerequisite
-products for SALOME version 3.2.4.
-
-<ul>
-<li>gcc 3.4.1
-\n\n Version number is checked by <b>gcc -dumpversion</b> command. The \b gcc
-executable should be in the \b PATH environment variable. Version should
-be equal to "3.4.1". It is recommended to use native gcc on Mandrake
-10.1.<br><br>
-</li>
-<li>tcl/tk 8.4.5
-\n\n Version number for \b tcl/tk can be found in tclConfig.sh and
-tkConfig.sh files (\b TCL_VERSION and \b TK_VERSION variables
-correspondingly). Version number should be equal to "8.4" (release
-number is not checked). Set the \b TCLHOME environment variable to the
-root directory of tcl/tk installation. It is recommended to use native
-tcl/tk on Mandrake 10.1.<br><br>
-</li>
-<li>boost 1.31.0
-\n\n Version number is defined by \b version.hpp file which is part of
-the boost distribution. This file defines the \b BOOST_VERSION macro
-which should be equal to "103100". In addition the existence of boost
-libraries is checked. Set the \b BOOSTDIR environment variable if you
-have a preinstalled version of boost.<br><br>
-</li>
-<li>Python 2.3.4
-\n\n Version number is checked by \b python -\b V command. The \b python
-executable should be in the \b PATH environment variable. Version
-number should be equal to "2.3.4". It is recommended to use native
-Python on Mandrake 10.1. Set the \b PYTHONHOME environment variable if
-you have a preinstalled version of Python.<br><br>
-</li>
-<li>Swig 1.3.24
-\n\n Version number is checked by \b swig -\b version command. The \b swig
-executable should be in the \b PATH environment variable. Version number
-should be equal to "1.3.24".
-<br><br>
-</li>
-<li>Qt 3.3.3
-\n\n Version number is defined by \b qglobal.h file which is part of the
-Qt distribution. This file defines \b QT_VERSION_STR macro which should be equal to "3.3.3". It is recommended to use native Qt on Mandrake 10.1.
-\n Set the \b QTDIR environment variable if you have a preinstalled version of qt.<br><br>
-</li>
-<li>msg2qm
-\n\n \b msg2qm is a Qt tool which is used to convert text *.po files
-to *.qm resource files. Unfortunately this tool is not included to the
-Linux distribution and provided only in Qt sources package. This is
-the reason why this tool is supplied with the SALOME Installation
-Wizard. There is no way to check the version number of msg2qm tool. Just set
-\b MSG2QM_ROOT environment variable if you have a preinstalled version
-of msg2qm tool.<br><br>
-</li>
-<li>Open CASCADE 6.1.2a2
-\n\n Version number is defined by \b Standard_Version.hxx file which
-is part of the Open CASCADE distribution. This file defines \b
-OCC_VERSION_MAJOR, \b OCC_VERSION_MINOR and \b OCC_VERSION_MAINTENANCE
-macros which should refer to version 6.1.2. \n Set the CASROOT
-environment variable if you have a preinstalled version of Open
-CASCADE.<br><br>
-</li>
-<li>qwt 4.2.0/0.4.2
-\n\n Version number is defined by \b qwt_global.h file which is part of
-the qwt distribution. This file defines \b QWT_VERSION_STR macro which should be equal to "4.2.0".
-\n Set the \b QWTHOME environment variable if you have a preinstalled version of qwt.<br><br>
-</li>
-<li>hdf 5-1.6.4
-\n\n Version number is defined by \b libhdf5.settings file which is
-part of the \b hdf5 distribution. Version should be equal to 1.6.4.
-\n Set the \b HDF5HOME environment variable if you have a preinstalled
-version of hdf5.<br><br>
-</li>
-<li>med 2.2.3
-\n\n Unfortunately there is no formal way to check med version
-number. We check existence of libmed.so.1.0.2 library on the
-computer. If you have any problem with a preinstalled version of med,
-please, reinstall it.
-\n Set the \b MED2HOME environment variable if you have a preinstalled
-version of med.<br><br>
-</li>
-<li>Vtk 4.2.6
-\n\n Unfortunately there is no formal way to check VTK version
-number. We just check the existence of \b libvtkCommon.so library on
-the computer and hope that it is of version we need. If you have any
-problem with a preinstalled version of Vtk, please, reinstall it.
-\n Set the \b VTKHOME environment variable if you have a preinstalled
-version of Vtk.<br><br>
-</li>
-<li>OmniORB 4.0.5, OmniORBpy 2.5, OmniNotify 2.1
-\n\n We just check existence of some omniORB libraries and executable
-on the computer, like \b libomniORB4.so.0.5, \b _omnipymodule.so.2.4,
-\b libCOSNotify4.so.0.1 and \b notifd. \n Set the \b OMNIORBDIR
-environment variable if you have a preinstalled version of omniORB
-products.<br><br>
-</li>
-<li>sip 4.1
-\n\n Version number is checked by \b sip -\b V command. The \b sip
-executable should be in the \b PATH environment variable. Version number should be equal to "4.1".
-\n Set the \b SIPDIR environment variable to the directory where you
-have sip executable preinstalled.<br><br>
-</li>
-<li>PyQt 3.13
-\n\n Version number is defined by \b pyqtconfig.py Python module file
-which is part of the \b PyQt distribution. Version should be equal to "3.13".
-\n Set the \b PYQTDIR environment variable if you have a preinstalled
-version of PyQt.<br><br>
-</li>
-<li>netgen 4.5
-\n\n Unfortunarely we can't find anything about netgen version. We
-just check if \b NETGENROOT environment variable is set. \n Set the\b
-NETGENROOT environment variable if you have a preinstalled version of
-netgen mesher.<br>
-\note netgen 4.5 provided with the SALOME installation Wizard has been patched to improve its performance.
-</li>
-<li>Numeric 23.7
-\n\n Version number is checked by <b>python -c 'import Numeric; print
-Numeric.__version__'</b> command. The \b python executable should be
-in the \b PATH environment variable and \b Numeric module should be
-available for the Python (for example it should be in the \b PYTHONPATH environment variable). Version number should be equal to "23.7". If you have any problem with a preinstalled version of Numeric 23.7, please, reinstall it.
-\n Add the directory where you have a preinstalled version of Numeric
-package to the the \b PYTHONHOME environment variable.<br><br>
-</li>
-<li>graphviz 2.2.1
-\n\n Version number is checked by \b dot -\b V command. The dot
-executable should be in the \b PATH environment variable. Version
-number should be equal to "2.2.1". \n Add \b graphviz bin directory to
-the the \b PATH environment variable.<br><br>
-</li>
-<li>doxygen 1.4.6
-\n\n Version number is checked by \b doxygen --\b version command. The
-\b doxygen executable should be in the \b PATH environment
-variable. Version number should be equal to "1.4.6".<br><br>
-</li>
-<li>\b SALOME module \b sources (3.2.4).
-\n\n For each SALOME module sources package (KERNEL, GUI, GEOM,
-etc...) the root directory contains file configure.in (configure.ac)
-which defines version information.\n Set the \b \<MODULE\>_SRC_DIR environment variable for each SALOME \b
-MODULE sources package installed (where \b MODULE is KERNEL, GUI,
-GEOM, ...).<br><br>
-</li>
-<li>\b SALOME module \b binaries (3.2.4)
-\n\n For each SALOME module binaries package (KERNEL, GUI, GEOM,
-etc...) the \b bin/salome directory contains file \b VERSION which
-defines version information.\n Set \<MODULE\>_ROOT_DIR environment
-variable for each SALOME \b MODULE binaries package installed (where
-\b MODULE is KERNEL, GUI, GEOM, ...).<br><br>
-</li>
-</ul>
-
-If you have native products installed to directories different from
-default ones (not \b /usr/bin, \b /usr/lib...), it is recommended to follow
-the above mentioned instructions. Or you should properly set \b PATH and
-\b LD_LIBRARY_PATH variables \em before starting the Installation
-Wizard. Otherwise the installation script will fail to find
-preinstalled/native products.
-
-\note for some native products (e.g. gcc, Python) the rules of version
-checking are not so strict as described above. Only major and minor
-version numbers should coincide with the prerequisite. Newer version
-of the product can also be used. If some native product has version
-number larger than that required by the installation procedure, the
-user will be prompted by the warning message like this: "<em>You have
-newer version of gcc installed on your computer than that is required
-(3.4.1). Continue?</em>". You can click "\em Yes" to proceed with the
-installation but in this case you should be aware of what you are
-doing. SALOME binaries (including other products) are compiled with
-the predefined prerequisites and most likely can not be run
-successfully if these products are not found. This can be helpful only
-if you plan to build all products from sources.
-
-<br>
-<hr>
-\anchor pick_up_env
-<h2>Pick up the <em>environment</em></h2>
-
-Please, read the following information carefully . This section
-describes how the installation procedure generates the environment
-scripts for the SALOME platform being installed.
-<br><br>
-After installing each product shell the script creates a special
-environment file for the product in its installation folder. The name
-of the file is generated from the name of product by the following
-scheme: \b env_<product_name>.sh (for example \b env_Vtk.sh for the
-Vtk). This file includes all necessary environment settings. At the
-final step of the installation the script picks up all the settings
-files and generates two common environment files from them: \b salome.sh
-and \b salome.csh for \b bash and \b csh shells correspondingly. Such approach
-helps to save time when reinstalling products and you may not bother
-about setting all environment variables manually to build/launch
-SALOME. What you simply need is to source one of these environment
-files.
-<br><br>
-This also concerns those products which are not being installed. For
-example, you install some SALOME binaries to the directory where you
-have previously installed other products. The Installation procedure
-tries to collect environment files from the target directory if it
-finds necessary products installed there. If some product is not found
-in the target directory the corresponding section of
-\b salome.sh/salome.csh files will be skipped.
-\n For native products (like \b gcc, \b tcl, etc...) the installation
-procedure tries to find them first using \b PATH / \b LD_LIBRARY_PATH
-variables and then in the system default directories (\b /usr/bin,
-\b /usr/lib etc., depending on the product).
-<br><br>
-In any case you may edit \b salome.* files after the installation
-procedure finishes, if you want.
-
-\note As it was mentioned \ref environment_files "above" there are
-other environment files which are generated by the installation
-procedure: \b env_products.csh + \b env_products.sh and \b env_build.csh +
-\b env_build.sh. These files can be found in the target installation root
-directory.
-
-<br>
-<hr>
-\anchor modifying_xml
-<h2>Modifying <em>XML</em> configuration <em>file</em></h2>
-
-You can create your own XML configuration file. The Installation
-Wizard can then take it as a command line argument to provide a list
-of products you want to install with it. The list of products and some
-other settings for the Installation Wizard are provided in the XML
-file. The default file which Installation Wizard looks for if no
-command line arguments are given, is \b config.xml.
-\n This section describes the structure of the configuration file.
-\n Optional sections/tags are in brackets.
-
-\code
-<document>
- [ <config [ version=<install_wizard_version> ]
- [ caption=<install_wizard_caption> ]
- [ copyright=<install_wizard_copyright> ]
- [ license=<install_wizard_license_info> ]
- [ os=<target_platform> ]
- />
- ]
- [ <path [ targetdir=<target_directory> ]
- [ tempdir=<temp_directory> ]
- />
- ]
- [ <button label=<button_label>
- [ tooltip=<button_tooltip> ]
- script=<button_script>
- [ disable=<disable_flag> ]
- />
- ]
- [ <button ...
- />
- ]
- [ <product name=<product_name>
- version=<product_version>
- [ context=<product_context> ]
- [ description=<product_description> ]
- install=<installation_mode>
- supported=<supported_installation_modes>
- [ disable=<disable_flag> ]
- [ pickupenv=<pickup_env_flag> ]
- dependancies=<list_of_prerequisites>
- installdiskspace=<install_disk_space>
- temporarydiskspace=<tmp_disk_space>
- script=<installation_script_name>
- />
- ]
- [ <product ...
- />
- ]
- ...
-</document>
-\endcode
-
-<b>\<config\> section</b>
-\n\n This is an optional section; it provides general information about
-the Installation Wizard itself.
-<br><br>
-Attributes:
-<ul>
-<li><b>version</b>
-\n\n The application version number to be shown in the caption.<br><br>
-</li>
-<li><b>caption</b>
-\n\n The application main window caption - if this string contains
-'\%1' text the title will contain the version number in this place (see
-above).<br><br>
-</li>
-<li><b>copyright</b>
-\n\n The application copyright information (shown in the first
-page).<br><br>
-</li>
-<li><b>license</b>
-\n\n The application license information (shown in the first
-page).<br><br>
-</li>
-<li><b>os</b>
-\n\n This parameter defines the directory (relative from
-./Products/BINARIES) where the Installation Wizard will search
-precompiled binaries packages. If this tag is not provided, binaries
-packages are looked for in the ./Products/BINARIES directory.<br><br>
-</li>
-</ul>
-
-<b>\<path\> section</b>
-\n\n This is an optional section; it defines default installation
-directories.
-<br><br>
-Attributes:
-<ul>
-<li><b>targetdir</b>
-\n\n The target directory - the path to the directory where products
-should be installed.<br><br>
-</li>
-<li><b>tempdir</b>
-\n\n The temporary directory - the path to the directory for the
-temporary files.<br><br>
-</li>
-</ul>
-
-<b>\<product\> section</b>
-\n\n This section describes product to be installed with the
-Installation Wizard. The XML file should include a \<product\> section
-for each product to be installed. The products appear in the tree view
-and are installed in the order they are described in the configuration
-file. It is recommended (but not obligatory) to define native products
-at the top of the list before all other products.
-<br><br>
-Attributes:
-<ul>
-<li><b>name</b>
-\n\n Product name.<br><br>
-</li>
-<li><b>version</b>
-\n\n Product version.<br><br>
-</li>
-<li><b>description</b>
-\n\n Product description (optional).<br><br>
-</li>
-<li><b>context</b>
-\n\n Context (optional). The possible values are '<b>salome
-sources</b>', '<b>salome binaries</b>' and '<b>prerequisite</b>'
-(several contexts can be given separated by ":" symbol).<br><br>
-</li>
-<li><b>supported</b>
-\n\n Supported modes of installation. Several modes can be separated
-by comma. Possible value are: <em>install sources, install binaries, use
-native</em>. The Installation script should contain the corresponding
-functions for each of the supported installation modes (see
-\ref installation_scripts "here").<br><br>
-</li>
-<li><b>install</b>
-\n\n Default (starting) installation mode.<br><br>
-</li>
-<li><b>disable</b>
-\n\n If this optional flag has 'true' value, the corresponding product
-will not appear in the list of products and will not be
-installed.<br><br>
-</li>
-<li><b>pickupenv</b>
-\n\n This flag points that pickup environment procedure should be
-performed for this product. If this flag equal to 'true', salome.sh
-and salome.csh files will be created in the product installation
-directory. Usually this option is set to true for SALOME KERNEL module
-sources and binaries package. This is an optional key, default value
-is 'false'.<br><br>
-</li>
-<li><b>dependancies</b>
-\n\n List of prerequisite products, which are necessary to build this
-product, separated by comma.<br><br>
-</li>
-<li><b>installdiskspace</b>
-\n\n Total amount of space (integer, in Kbytes), which the product
-occupies on the hard drive after the installation.<br><br>
-</li>
-<li><b>temporarydiskspace</b>
-\n\n Disk space (integer, in Kbytes) for temporary files, which is
-necessary to build the product from the sources.<br><br>
-</li>
-<li><b>script</b>
-\n\n The installation script name. This script is in charge of the
-installation of the product. It is called automatically by the
-Installation Wizard when necessary from the main program.
-See the \ref installation_scripts "next section" for more information.<br><br>
-</li>
-</ul>
-
-<b>\<button\> section</b>
-\n\n This is an optional section. It allows customization of the last
-"Finish installation" page of the Installation Wizard by adding one or
-more buttons in the lower part of the wizard's window. The script
-which is attached to each such button, can perform some specific
-action, for example, launch the application or show the Release Notes
-file by using an external program. See \ref finish_buttons "here" for
-more details about writing scripts.<br><br>
-Attributes:
-<ul>
-<li><b>label</b>
-\n\n This is the button text.<br><br>
-</li>
-<li><b>tooltip</b>
-\n\n The button tooltip (optional).<br><br>
-</li>
-<li><b>script</b>
-\n\n The script attached to the button.<br><br>
-</li>
-<li><b>disable</b>
-\n\n If this optional flag has 'true' value, the corresponding button
-will not appear in the "<em>Finish installation</em>" page - the section of XML
-file is silently ignored.<br><br>
-</li>
-</ul>
-
-\note If you add new products to be installed with Installation
-Wizard, you should also provide installation script for this
-product. See the next section for more details.
-
-<br>
-<hr>
-\anchor installation_scripts
-<h2>Implementing <em>installation scripts</em> for the new products</h2>
-
-When you want some product to be installed with the Installation
-Wizard, you should add its description \ref modifying_xml "to the configuration file"
-and create the installation script, following the rules described in this section.
-
-There are some obligatory functions which should be implemented in
-this installation script. These functions are automatically called by
-the master installation script or/and its GUI shell when it is
-necessary. \n File \b common.sh contains some service functions which can
-be used in your installation script, like \b make_env(), \b make_dir(),
-\b try_existing(), \b sort_path(), \b find_in_path(), etc.
-
-<ul>
-<li><b>check_version()</b>
-\n\n 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 its version. This
-helps to avoid unnecessary reinstallation. This is an internal
-function and is not called from the master installation
-script.<br><br>
-</li>
-<li><b>try_native()</b>
-\n\n This function is called when the 'use native' installation mode
-is selected by the user. The function should try to find a native
-version of the product and define possibility of its use. It should
-create the environment file for the product in the temporary directory
-(see also the description of \b print_env() function). It is not
-necessary to implement this function if you do not provide native mode
-installation.<br><br>
-</li>
-<li><b>install_source()</b>
-\n\n This function is called when the 'install sources' installation
-mode is selected by the user. The function is responsible for building
-the product from the sources package. It should create the environment
-file for the product in the temporary directory (see also description
-of \b print_env() function). It is not necessary to implement this
-function if you do not provide sources mode installation.<br><br>
-</li>
-<li><b>install_source_and_build()</b>
-\n\n This function is called when SALOME module is installed and the
---\b all-from-sources (-\b a) option is used (<em>"Build SALOME sources"</em>
-check box in GUI mode). This function should be used to unpack SALOME
-sources package and then call the build/install procedure for it.
-For more details please refer to the \ref installing_products "this"
-and \ref gui_mode_install "this" sections for more details.<br><br>
-</li>
-<li><b>install_binary()</b>
-\n\n This function is called when the <em>'install binaries'</em> installation
-mode is selected by the user. The function is responsible for the
-extracting of the product from the binaries package. It should create
-environment for the product in the temporary directory (see also
-description of \b print_env() function). It is not necessary to implement
-this function if you do not provide binaries mode
-installation.<br><br>
-</li>
-<li><b>try_preinstalled()</b>
-\n\n 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 an already preinstalled product, pick
-up and check the environment from there. See \ref pick_up_env "here" for more
-details.<br><br>
-</li>
-<li><b>print_env()</b>
-\n\n This function is in charge of creating the environment script. It
-should create a file with name \b 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.<br><br>
-</li>
-<li><b>pickup_env()</b>
-\n\n This procedure corresponds to the \b pickupenv tag of the
-configuration xml file (see previous section). It should call the
-\b make_env procedure to perform the pick-up environment procedure for
-the product.<br><br>
-</li>
-</ul>
-
-The calling signature of the product installation script is the following:
-<b>\<product_script_name\> \<function_name\> \<temp_folder\>
-\<products_directory\> \<target_directory\> \<dependancies\>
-\<product_name\></b>
-\n\n where \n\n
-<b>\<product_script_name\></b> - installation script name (described in the
-configuration xml file);\n
-<b>\<function_name\></b> - the name of function, corresponding to the selected
-installation mode: \em try_native, \em install_source, \em install_binary or
-\em try_preinstalled;\n
-<b>\<temp_folder\></b> - temporary files directory;\n
-<b>\<products_directory\></b> - directory where the sources/binaries package
-can be found. You should provide the sources package in the
-<em>\<Install_Wizard_root_directory\>/Products/SOURCES</em> directory and
-binaries package in the
-<em>\<InstallWizard_root_directory\>/Products/BINARIES/\<os_version\></em>, where
-\<os_version\> is the target platform description, which appears in the
-corresponding section of the \ref modifying_xml "configuration xml file";
-<em>\<target_directory\></em> - root target directory where the product should be installed to;
-<em>\<dependancies\></em> - single-quoted list of prerequisite products, separated by space;
-<em>\<product_name\></em> - product name itself.
-
-\b Example:
-\n <em>med-2.2.3.sh install_binary /tmp/work
-./Products/BINARIES/Mandrake10.1 /usr/salome 'gcc Hdf' med</em>
-
-Copy the created script into the
-<em>\<Install_Wizard_root_directory\>/config_files</em> sub-directory where all
-installation scripts are stored. Installation Wizard will
-automatically search and call your script during the installation
-procedure.
-
-<br>
-<hr>
-\anchor finish_buttons
-<h2>Customizing <em>Readme page</em> buttons</h2>
-
-The Installation Wizard allows customizing the look-n-feel of the last
-<em>"Finish installation"</em> page. If you want to add one or more buttons to
-this page in order to perform some specific actions at the end of the
-installation (for example, to show the Release Notes file by using
-Open Office) you can put an additional section to the XML
-configuration file. This is the \b \<button\> section (see
-\ref modifying_xml "here" for more details).
-
-To implement the action which will be performed when the user clicks
-the button, you need to create a script and put it to the
-<em>\<Install_Wizard_root_directory\>/config_files</em> directory.
-\n There are some obligatory functions which should be implemented in
-this script. These functions are automatically called by the
-Installation Wizard GUI.
-
-<ul>
-<li><b>check_enabled()</b>
-\n\n This procedure is called by the Installation Wizard when the
-<em>"Finish installation"</em> page is displayed and the status of the buttons
-should be modified according to the installation options. This
-procedure should return \b 0 if the corresponding action can be performed
-and, thus, the button should become enabled. Otherwise, it should
-return \b 1 - in this case the corresponding button will be
-disabled.<br><br>
-</li>
-<li><b>execute()</b>
-\n\n This procedure is invoked when the user clicks the button. This
-procedure should return \b 0 if the corresponding action is done
-successfully and \b 1 if any error occurs.<br><br>
-</li>
-</ul>
-
-The calling signature of the script is the following:
-\n <b>\<product_script_name\> \<function_name\> \<target_directory\>
-\<temp_folder\></b>
-\n\n where \n\n
-\b \<product_script_name\> - the script name itself (retrieved from the XML configuration xml file);
-\n \b \<function_name\> - the name of function;
-\n \b \<target_directory\> - root target directory where the product is installed to;
-\n \b \<temp_folder\> - temporary files directory;
-
-\note The standard Installation Wizard buttons "Launch SALOME" and
-"Release Notes" are implemented with this feature. Refer to scripts
-\b start_salome.sh and \b release_notes.sh for sample implementation.
-
-\note Any button (even standard) can be ignored by the Installation
-Wizard if the attribute \b \<disable\> in the XML configuration file is set
-to the "true" value.
-
-*/
\ No newline at end of file
+++ /dev/null
-/*!
-
-\page intro_to_salome_page Introduction to SALOME
-
-
-\b SALOME platform represents a generic open source platform for pre-
-and post-processing in numeric simulations. \b SALOME combines several
-software components, which are built in such a way that it allows to
-integrate solvers and existing meshing algorithms along with the
-specification of physical properties for a given domain. The
-originality of this approach is that the various components must
-cooperate dynamically and be
-configurable.
-
-\image html image54.jpg
-
-<br>SALOME platform integrates a number of modules each having its own function:
-<ul>
-<li>\b KERNEL : provides a common shell for all components, which can be integrated into the SALOME platform.
-<li>\b GUI : provides visual representation: basic widgets, viewers
-etc. Third party modules optionally can have GUI, but in any case they always connected with KERNEL.
-<li>\b Geometry : facilitates construction and optimization of geometrical models using a wide range of CAD functions.
-<li>\b Mesh : generates meshes on geometrical models previously created or imported by the Geometry component.
-<li>\b Supervisor : provides tools for construction of graphs and execution of calculations.
-<li>\b Post-Pro : performs data visualization.
-<li>\b MED : allows to work with MED files.
-</ul>
-
-*/
+++ /dev/null
-/*!
-
-\image html icon_about.png
-
-\page introduction_page Introduction
-
-<br>
-
-Welcome to SALOME Platform! Modern technological products (cars,
-structures, electrical or electronic equipment) are getting more and
-more complex every year and must meet increasingly severe requirements
-in terms of quality and performance. For example, for structures and
-their environment the demands to reduce risks and optimize costs are
-extremely high. It requires particularly refined simulations
-concerning structural behavior and robustness to ensure high
-reliability.
-\n The numeric modeling of a physical problem, the development of
-solutions and their integration into the design process are often
-handled in very specific environments. SALOME represents a generic
-CAD-based application for digital simulation with "high reactivity to
-market evolutions and customer expectations".
-
-SALOME is a free software that provides a generic platform for Pre and
-Post-Processing for numerical simulation. It is based on an open and
-flexible architecture made of reusable components available as free
-software.
-
-SALOME is a CAD/CAE integration platform. It provides reusable
-components for:
-<ul>
-<li>3D modeling (bottom-up construction, import, healing);
-<li>Visualization;
-<li>Computational schemas management;
-<li>Post-processing.
-</ul>
-
-SALOME is tailored for integration of custom components:
-<ul>
-<li>CAD interfaces;
-<li>Mesh generators;
-<li>Finite Element solvers with specific pre-processors.
-</ul>
-
-The SALOME platform is available in Open Source.
-
-<b>Salome Platform:</b>
-<ul>
-<li>Supports interoperability between CAD modeling and computation software (CAD-CAE link)
-<li>Makes easier the integration of new components on heterogeneous systems for numerical computation
-<li>Sets the priority to multi-physics coupling between computation software
-<li>Provides a generic user interface, user-friendly and efficient, which helps to reduce the costs and delays of carrying out the studies
-<li>Reduces training time to the specific time for learning the software solution which has been based on this platform
-<li>All functionalities are accessible through the programmatic
-integrated Python console
-</ul>
-
-\image html image65.gif
-
-<b>What can you do in SALOME? (Some of SALOME main functions)</b>
-<ul>
-<li>Define geometrical models (create/modify geometrical items), import and export them using the BREP, IGES and STEP formats;
-<li>Define meshing of these geometrical items, import and export them;
-<li>Handle physical properties and quantities attached to geometrical items, import and export them to a reusable format;
-<li>Perform computations using a solver (optionally provided): read input data, configure the solver, and write calculation results);
-<li>Visualize result fields in 3D, 2D and export images of their visualization to an appropriate format;
-<li>Manage study schemes: definition, save/restore;
-<li>Manage computation schemes: definition, execution.
-</ul>
-
-*/
\ No newline at end of file
+++ /dev/null
-/*!
-
-\page introduction_to_gui_page Introduction to GUI
-
-\b GUI (Graphical User Interface) provides a common shell for all components, which can be integrated into the SALOME platform.
-
-\b GUI component in SALOME platform provides:
-<ul>
-<li>Common desktop environment (\ref salome_desktop_page "SALOME desktop") for all
-components</li>
-<li>Component integration and management: uploading, switching,
-component menus/toolbars handling</li>
-<li>Study management (creation, saving, loading, editing studies)</li>
-<li>Multi-window management in the framework of one study</li>
-<li>Management of objects created or imported into the SALOME
-application (\ref using_object_browser_page "Object Browser")</li>
-<li>Integrated Python interpreter</li>
-<li>Output messages window</li>
-<li>Additional tools : \ref using_catalog_generator_page "Catalogue Generator",
-\ref using_registry_tool_page "Registry tool"</li>
-<li>Standard viewers for data visualization:</li>
-<ul>
-<li>VTK 3d viewer
-<li>OCC 3d viewer
-<li>Gauss Points viewer
-<li>Plot 2d viewer
-<li>Supervision viewer
-</ul>
-</ul>
-
-
-
-Since version 3.0.0 SALOME GUI is based on SUIT (Salome User Interface
-Toolkit) that proposes very flexible, powerful and safe mechanisms of
-interaction with SALOME tool components (both CORBA and standalone),
-resources management, viewers and selection handling,
-exception/signals processing, bringing to top multi-desktop
-dockable-windowed user interface which improves the usability of
-SALOME GUI.
-\n All Graphical User Interfaces of standard modules have plug-in
-structure, i.e. each module is placed in a dynamic library which is
-loaded on demand. All modules can create their own menu items, buttons
-in toolbar, windows etc
-
-*/
\ No newline at end of file
+++ /dev/null
-/*!
-
-\page mesh_preferences_page Mesh preferences
-
-In the Mesh module you can set mesh preferences, which can be used in
-later sessions with this module.
-
-<h2>General Preferences</h2>
-
-\image html pref21.png
-
-<ul>
-<li><b>Update</b></li>
-<ul>
-<li>If you toggle <b>Automatic Update</b> checkbox, the model in your
-viewer automatically updated whenever you make changes in it.</li>
-</ul>
-<li><b>Quality Controls</b></li>
-<ul>
-<li>If you toggle <b>Display entity</b>, both faces and edges of an
-object will be displayed in the viewer by default.</li>
-<li>If you toggle <b>Use precision</b> checkbox, you can display numbers in
-<b>Quality Control</b> diagrams at the necessary level of precision.</li>
-</ul>
-<li><b>Precision</b> - can be defined by the <b>Number of digits after point</b> in
-the corresponding field. By default, numbers in <b>Quality Control</b>
-diagrams are presented as integers.</li>
-<li><b>Display mode</b> - allows to set Wireframe, Shading, Nodes or Shrink
-presentation mode as default.</li>
-<li><b>Mesh export</b></li>
-<ul>
-<li>If you toggle <b>Automatically create groups for MED export</b> checkbox,
-this operation will be carried out automatically.</li>
-<li>If you toggle <b>Automatic renumbering</b> checkbox, the exported
-mesh will be renumbered automatically</li>
-</ul>
-<li><b>Mesh computation</b></li>
-<ul>
-<li><b>Show a computation result notification</b> combobox allows to
-select the notification mode about a mesh computation result.
-There are 3 possible modes:</li>
-<ul>
-<li><b>Never</b> - do not show the result dialog at all;</li>
-<li><b>Errors only</b> - the result dialog will be shown if there were
-some errors during a mesh computation;</li>
-<li><b>Always</b> - show the result dialog after each mesh
-computation. This is a default mode.</li>
-</ul>
-</ul>
-
-<h2>Mesh Preferences</h2>
-
-\image html pref22.png
-
-<ul>
-<li><b>Nodes</b></li>
-<ul>
-<li><b>Color</b> - allows to select the color of nodes. Click on the
-colored line to access to the \ref select_color_and_font_page "Select Color"
-dialog box.</li>
-<li><b>Size</b> - allows to define the size of nodes.</li>
-</ul>
-<li><b>Elements</b></li>
-<ul>
-<li><b>Fill</b> - allows to select the color of surface of elements
-(seen in Shading mode). Click on the colored line to access to the
-\ref select_color_and_font_page "Select Color" dialog box.</li>
-<li><b>Outline</b> - allows to select the color of borders of
-elements. Click on the colored line to access to the
-\ref select_color_and_font_page "Select Color" dialog box.</li>
-<li><b>Back Face</b> - allows to select the color of interior surface
-of elements. Click on the colored line to access to the
-\ref select_color_and_font_page "Select Color" dialog box.</li>
-<li><b>Width</b> - allows to define the width of lines (edges and borders of elements).</li>
-<li><b>Shrink coef.</b> - allows to define relative space of elements
-compared to gaps between them in shrink mode.</li>
-</ul>
-</ul>
-
-<br><h2>Selection Preferences</h2>
-
-\image html pref23.png
-
-<ul>
-<li><b>Selection</b> - performed with mouse-indexing (preselection)
-and left-clicking on an object, whose appearance changes as defined in
-the <b>Preferences</b>.</li>
-<ul>
-<li><b>Object Color</b> - allows to select the color of mesh (edges and
-borders of meshes) of the selected entity. Click on the colored line
-to access to the \ref select_color_and_font_page "Select Color" dialog
-box.</li>
-<li><b>Element color</b> - allows to select the color of surface of selected
-elements (seen in Shading mode). Click on the colored line to access
-to the \ref select_color_and_font_page "Select Color" dialog box.</li>
-<li><b>Width</b> - allows to define the width of selected edges. </li>
-</ul>
-<li><b>Preselection</b> - performed with mouse-indexing on an object,
-whose appearance changes as defined in the <b>Preferences</b>.</li>
-<ul>
-<li><b>Highlight Color</b> - allows to select the color of mesh (edges and
-borders of meshes) of the entity . Click on the colored line to access
-to the \ref select_color_and_font_page "Select Color" dialog box.</li>
-<li><b>Width</b> - allows to define the width of preselected edges.</li>
-</ul>
-<li><b>Precision</b> - in this menu you can set the value of precision
-used for <b>Nodes</b>, <b>Elements</b> and <b>Objects</b>.</li>
-</ul>
-
-<br><h2>Scalar Bar Preferences</h2>
-
-\image html pref24.png
-
-<ul>
-<li><b>Font</b> - in this menu you can set type, face and color for
-the font of <b>Title</b> and <b>Labels</b>.</li>
-<li><b>Colors & Labels</b> - in this menu you can set the <b>number of
-colors</b> and the <b>number of labels</b> in use.<li>
-<li><b>Orientation</b> - here you can choose between vertical and
-horizontal orientation of the <b>Scalar Bar</b></li>.
-<li><b>Origin & Size Vertical & Horizontal</b> - allows to define
-placement (<b>X</b> and <b>Y</b>) and lookout (<b>Width</b> and
-<b>Height</b>) of Scalar Bars</li>
-<ul>
-<li><b>X</b>: abscissa of the point of origin (from the left
-side)</li>
-<li><b>Y</b>: ordinate of the origin of the bar (from the bottom)</li>
-</ul>
-</ul>
-
-*/
\ No newline at end of file
+++ /dev/null
-/*!
-
-\page occ_3d_viewer_page OCC 3D Viewer
-
-<b>OCC (Open CasCade) 3D viewer</b> has been developed on the basis of Open
-CASCADE Technology. This is the default viewer for Geometry Module,
-providing good representation of construction and transformation of
-geometrical objects. Only this viewer allows to work with groups and
-sub-shapes. This viewer can also work in Mesh module, however, it
-doesn't allow to visualize meshes.
-
-The functionalities of OCC viewer are available via its Viewer
-Toolbar. Buttons marked with small downward triangles have extended
-functionality which can be accessed by locking on them with left mouse
-button.
-
-\image html occviewer_toolbar.png "Viewer Toolbar"
-
-<hr>
-\image html image77.gif
-\n <center><b>Dump View</b> - exports an object from the viewer in bmp, png, jpg
-or jpeg image format.</center>
-<hr>
-
-\image html image88.gif
-\n <center><b>Show/Hide Trihedron</b> - shows or hides coordinate axes.</center>
-<hr>
-
-\image html image96.gif
-\n <center><b>Fit all</b> - allows to select a point to be the center of a
-scene representing all displayed objects in the visible area.</center>
-<hr>
-
-\image html image97.gif
-\n <center><b>Fit area</b> - resizes the view to place in the visible area
-only the contents of a frame drawn with pressed left mouse button.</center>
-<hr>
-
-\image html image98.gif
-\n <center><b>Zoom</b> - allows to zoom in and out.</center>
-<hr>
-
-\image html image99.gif
-\n <center><b>Panning</b> - if the represented objects are greater that the
-visible area and you don't wish to use <b>Fit all</b> functionality, click on
-this button and you'll be able to drag the scene to see its remote
-parts.</center>
-<hr>
-
-\image html image100.gif
-\n <center><b>Global panning</b> - represents all displayed objects in
-the visible area.</center>
-<hr>
-
-\image html view_rotation_point.png
-\n <center><b>Change rotation point</b> - allows to to choose the point around
-which the rotation is performed.</center>
-
-\image html set_rotation_point_dialog1.png
-
-<center>By default the rotation point is located in the Center of the bounding
-box of an object.</center>
-
-\image html set_rotation_point_dialog2.png
-
-<center>Unchecking <b>Use Bounding Box Center</b> checkbox allows you to
-define the coordinates of the rotation point manually.</center>
-
-<b>Set to Origin</b> button restores the default rotation point
-coordinates.\n
-<b>Select Point from View</b> button allows to select the rotation
-point in the 3D Viewer.
-<hr>
-
-\image html image89.gif
-\n <center><b>Rotation</b> - allows to rotate the selected object using the
-mouse.</center>
-
-\image html image102.gif
-
-<center>These buttons orientate the scene strictly about coordinate axes.</center>
-<hr>
-
-\image html image91.gif
-\n <center><b>Reset</b> - restores the default position (isometric) of
-objects in the scene.</center>
-<hr>
-
-\image html image103.gif
-\n <center><b>Memorise view</b> - saves the current position of
-objects in the scene.</center>
-<hr>
-
-\image html image105.gif
-\n <center><b>Restore view</b> - restores the saved position of
-objects in the scene.</center>
-<hr>
-
-\image html image86.gif
-\n <center><b>Clone view</b> - opens a new duplicate scene.</center>
-<hr>
-
-\image html image106.gif
-\n <center><b>Clipping</b> - allows to create cross-section views
-(clipping planes) of geometrical objects.</center>
-
-\image html clipping.png
-<ul>
-<li><b>Base point</b> - allows to define the coordinates of the base
-point for the clipping plane.</li>
-<ul>
-<li><b>Reset</b> - returns the base point to coordinate origin.</li>
-</ul>
-<li><b>Direction</b> - allows to define the orientation of the
-clipping plane.</li>
-<ul>
-<li><b>Invert</b> - allows to select which part of the object will be removed
-and which will remain after clipping.</li>
-</ul>
-<li><b>Preview</b> - allows to see the results of clipping in the
-viewer.</li>
-</ul>
-<hr>
-\image html occviewer_axialscale.png
-\n <center><b>Scaling</b> - represents objects deformed (stretched or
-stuffed) along the axes of coordinates.</center>
-
-<b>Note!</b> OCC Viewer features a special <b>Polyline Selection</b> mechanism, which allows selecting an arbitraty part of the graphic area using a polygon frame, instead of the usual selection with a rectangular frame.
-
-To produce a Polyline Selection, lock the right mouse button and draw the first side of the polygon, then change the direction by clicking the left mouse button add draw another side, etc. The whole selection frame is drawn with the locked right mouse button.
-
-\image html polyselection1.png
-
-As a result, only the nodes within the frame are selected.
-
-\image html polyselection2.png
-
-*/
+++ /dev/null
-/*!
-
-\page opening_studies_page Opening studies
-
-In \b SALOME all studies are stored in a special format *.hdf.
-
-<em>To open an existing study:</em>
-\par
-In the main toolbar click "Open document" button or from the main menu select <b>File > Open</b>
-option. From a standard Search File dialog box choose the required
-*.hdf file and click \b Open button.
-
-\image html open.jpg ""Open document" button"
-
-<em>To load an unloaded study (\ref saving_and_closing_studies_page
-"see also"):</em>
-\par
-From the main menu select <b>File > Connect</b> option. In the following
-dialog box select one of the studies, which has been previously
-created and unloaded and click \b Ok button:
-
-\image html loadstudy2.png
-
-\par
-Alternatively, it is possible to select <b>File > Most Recently Used > </b> to select a study from the list.
-
-
-\n\b Tip: After opening an existing study, you will see its structure
-in the \ref using_object_browser_page "Object Browser". It will contain the objects created with the
-help of different components during the previous study session. If you
-right-click on one of the objects and from the associated pop-up menu
-choose <b>Open With</b> option, which will automatically launch the component
-corresponding to this object.
-
-*/
\ No newline at end of file
+++ /dev/null
-/*!
-
-\page plot2d_viewer_page Plot 2D viewer
-
-\n <b>Plot 2d viewer</b> is destined to the representation of 2d
-plots and graphs in Post-Pro module.
-\n Its viewer toolbar gives you fast access to the following
-operations:
-
-\image html image77.gif
-<center><b>Dump View</b> - exports an object from the viewer in bmp,
-png, jpg or jpeg image format.</center>
-
-\image html image96.gif
-<center><b>Fit all</b> - scales the display to show the entire
-scene. Use this to resize the scene so that it could fit within the
-Viewer boundary.</center>
-
-\image html image97.gif
-<center><b>Fit area</b> - resizes the view to place in the visible
-area only the contents of a frame drawn with pressed left mouse
-button.</center>
-
-\image html image98.gif
-<center><b>Zoom</b> - allows to zoom in and out.</center>
-
-\image html image99.gif
-<center>\b Panning - if the represented objects are greater that the
-visible area and you don't wish to use Fit all functionality, click on
-this button and you'll be able to drag the scene to see its remote
-parts.</center>
-
-\image html image100.gif
-<center><b>Global panning</b> - allows to define the center of the
-scene presenting all displayed objects in the visible area.</center>
-
-\image html plot2d_points.gif
-<center><b>Draw Points</b> - represents points on the graph.</center>
-
-\image html plot2d_lines.gif
-<center><b>Draw Lines</b> - represents lines on the graph.</center>
-
-\image html plot2d_splines.gif
-<center><b>Draw Splines</b> - represents splines on the graph.</center>
-
-\image html plot2d_logarithmic_horizontal.gif
-<center><b>Horizontal axis logarithmic</b> - changes the scaling on
-horizontal axis to logarithmic.</center>
-
-\image html plot2d_logarithmic_vertical.gif
-<center><b>Vertical axis logarithmic</b> - changes the scaling on vertical
-axis to logarithmic.</center>
-
-\image html plot2d_legend.gif
-<center><b>Show Legend</b> - reveals all verbal and numerical
-information on the graphs.</center>
-
-\image html plot2d_settings.gif
-<center>\b Settings - calls a menu, in which you can specify advanced
-settings for your Plot 2d Viewer.</center>
-
-\image html plot2d_clone.gif
-<center><b>Clone view</b> - opens a new duplicate scene.</center>
-
-\anchor settings
-\n \image html plot2d_view_settings.png
-
-The options are as follows:
-<ul>
-<li><b>Main title:</b> the title of the XY plot. By default, it will
-consist of the names of the tables, on the basis of which the curve
-lines have been constructed.</li>
-<li><b>Curve type:</b> you can select from \b Points, \b Lines and \b Spline.</li>
-<li><b>Show legend:</b> here you can define the position of the
-description table on the XY plot (to the \b Left, to the \b Right, on
-\b Top or on \b Bottom).</li>
-<li><b>Marker size</b> - size of the points (markers) forming curve lines.</li>
-<li><b>Background color</b> of the XY plot.</li>
-<li><b>Scale mode:</b> here you can select the type of scaling (\b
-Linear or \b Logarithmic) along <b>X (Horizontal)</b> or <b>Y (Vertical)</b> axes.</li>
-</ul>
-
-You can define settings for each axis separately:
-<ul>
-<li>\b Horizontal or \b Vertical axis title.</li>
-<li><b>Grid/Axes marks:</b> here you can define the maximum number of major
-and minor scale divisions for a specified axis. The real number of
-intervals fits to {1,2,5}*10^N, where N is a natural number, and
-doesn't exceed the maximum.</li>
-<li><b>Save settings as default:</b> If this check box is marked, all
-XY plots will be displayed with these defined properties.</li>
-</ul>
-
-*/
+++ /dev/null
-/*!
-
-\page postpro_preferences_page Post-Pro Preferences
-
-In the Post-Pro module you can set preferences, default settings,
-which can be used in later sessions with this module.
-
-<h2>MED import Preferences</h2>
-
-\image html ppref1.png
-
-<ul>
-<li><b>MED files import</b></li>
-<ul>
-<li><b>Use Build Progress</b> - when this option is checked you can choose
-all other import MED options at the moment of loading of each file
-using <b>Build Progress</b> menu, otherwise the loading will be done
-according to the <b>Preferences</b> without addressing to the
-user.</li>
-<li><b>Full MED Loading</b> - when this option is checked, the MED file is
-fully loaded in the study, and no additional access to the MED file is
-needed during the session. Reversibly, when unchecked, the MED file is
-loaded on demand. This is the default behaviour in SALOME and
-recommended for big files to optimize memory usage.</li>
-<li><b>Build at once</b> - when this option is checked, you can't
-perform any operations until the MED file is fully loaded and
-processed.</li>
-<li><b>Build fields</b> - when this option is checked, the fields are
-built automatically at loading.</li>
-<li><b>Build min/max</b> - when this option is checked, minimum and
-maximum values of the time stamps are found at loading.</li>
-<li><b>Build groups</b> - when this option is checked, the groups and
-families are built automatically at loading.</li>
-<li><b>Close dialog at finish</b> - when this option is checked, the
-dialog box is closed after loading of the selected MED file. When
-unchecked, it allows loading other MED files.</li>
-</ul>
-</ul>
-
-<br><h2>Scalar Bar Preferences</h2>
-
-\image html pref31.png
-
-<ul>
-<li><b>Scalar Range</b></li>
-<ul>
-<li><b>Scalar Mode</b> - this feature allows refining the value to be
-inspected:</li>
-<ul>
-<li><b>Modulus:</b> value of a scalar or modulus of a vector.</li>
-<li><b>Component N:</b> Nth component of a vector, a tensor or a matrix.</li>
-</ul>
-<li><b>Logarithmic Scaling</b> - this checkbox toggles logarithmic
-scaling.</li>
-<li><b>Ranges to Use</b> - you can use either Field Range or Imposed Range.</li>
-</ul>
-<li><b>Min and Max for Imposed Range</b> - in this menu you can set
-the limits for your Imposed Range, if you have chosen to use it.</li>
-<li><b>Font</b> - in this menu you can set type, face and color for
-the font of <b>Title</b> and <b>Labels</b>.</li>
-<li><b>Colors & Labels</b> - in this menu you can set the <b>number of
-colors</b> and the <b>number of labels</b> in the Scalar bar.</li>
-<li><b>Orientation</b> - here you can choose between vertical and horizontal
-orientation of the Scalar Bar.</li>
-<li><b>Origin & Size Vertical & Horizontal</b> - allows to define
-placement (<b>X</b> and <b>Y</b>) and lookout (<b>Width</b> and
-<b>Height</b>) of Scalar Bars.</li>
-<ul>
-<li><b>X:</b> abscissa of the point of origin (from the left
-side)</li>
-<li><b>Y:</b> ordinate of the origin of the bar (from the bottom)</li>
-</ul>
-<li><b>Scalar bars default position</b></li>
-<ul>
-<li><b>Arrange Scalar Bars</b> - this option prevents superposition of
-scalar bars during visualisation of several fields in the same
-window. If checked, a separate scalar bar is displayed for each
-presentation.</li>
-</ul>
-</ul>
-
-<br><h2>Cut Lines Preferences</h2>
-
-\image html ppref2.png
-
-<ul>
-<li><b>CutLine Preferences</b></li>
-<ul>
-<li><b>Show preview</b> check box allows to edit the parameters of the
-presentation and simultaneously observe the preview of this
-presentation in the viewer.</li>
-<li><b>Invert all curves</b> check box allows to invert the resulting
-curves.</li>
-<li><b>Use absolute length</b> check box allows to use absolute length
-for curves.</li>
-<li><b>Generate Data Table:</b> If this check box is marked, <b>Post
-Pro</b> will automatically generate a data table on the basis of your
-Cut Lines presentation. This table will be created in the structure of
-the study.</li>
-<li><b>Generate Curves:</b> If this check box is marked, <b>Post Pro</b> will
-automatically generate curve lines on the basis of values taken from
-the generated data table. These curves will be created in the
-structure of the study and can be visualized in a XY plot.</li>
-</ul>
-</ul>
-
-<br><h2>Sweep Preferences</h2>
-
-\image html ppref3.png
-
-<ul>
-<li><b>Sweeping preferences</b></li>
-<ul>
-<li><b>Mode of the Sweeping</b> - allows to choose between Linear,
-Cosinusoidal and sinusoidal sweeping.</li>
-<li><b>Time step</b> - in this menu you can set the time of
-representation of one step.</li>
-<li><b>Number of cycles</b> - in this menu you can define the number
-of times this animation will be repeated.</li>
-<li><b>Number of steps</b> - in this menu you can define the number of
-steps, which will compose the whole animation.</li>
-<li><b>Parameter varies</b> - allows to choose the range for the
-parameter: from 0 to Pi or from Pi to -Pi.</li>
-</ul>
-</ul>
-
-<ul>
-<li><b>Animation preferences</b></li>
-<ul>
-<li><b>Speed</b> - allows to define the speed of the animation.</li>
-<li><b>Cycled animation</b> - allows to start a cycled animation of the presentation.</li>
-<li><b>Use proportional timing</b> - allows to render the animation with proportional periods of time between every frame (not depending on the time stamps).</li>
-<li><b>Clean memory at each frame</b> - this option allows to optimize the performance of the operation.</li>
-</ul>
-</ul>
-
-<br><h2>Representation Preferences</h2>
-
-\image html pref33.png
-
-<ul>
-<li><b>Representation properties</b> - these checkboxes allow to
-choose the default representation type for each field presentation.</li>
-<ul>
-<li><b>Use Shading</b> - when this option is checked, the objects will
-be displayed with shading.</li>
-<li><b>Display only on creation</b> - when this option is checked, all
-previously created presentations will be automatically removed from
-the viewer when a new presentation is created and displayed. You can
-restore the previously created presentations using the Object
-Browser.</li>
-</ul>
-</ul>
-
-<br><h2>3D Cache</h2>
-
-\image.html pref40.png
-
-<ul>
-<li><b>3D Cache Preferences</b> - allow to define the mode of usage
-and the size of the 3D Cache, which enables to save in RAM and quickly
-restore the states of field animation.</li>
-<ul>
-<li><b>Memory Mode</b> - allows to define the mode of usage
-of the 3D Cache: <b>Minimal</b> actually disables the Cache,
-<b>Limited</b> Cache size depends on the current system
-configuration.</li>
-<li><b>Memory Limit</b> - allows to define the maximum size of the 3D
-Cache</li>
-</ul>
-</ul>
-
-
-<br><h2>Gauss Points Preferences</h2>
-
-\image html pref34.png
-
-<ul>
-<li><b>Primitive</b> - this menu allows user to choose the graphic
-primitive to use to present the results at Gauss points in the
-viewer.</li>
-<ul>
-<li><b>Primitive type</b> - provides choice between <b>Point
-sprites</b>, <b>Open GL points</b> and <b>Geometrical Spheres</b>.</li>
-<li><b>Maximum Size (Clamp)</b> - defines the maximum size of sprite
-points ranging from 1 to 512. By default the value is set to 256
-pixels.</li>
-<li><b>Main Texture</b> - path to the <b>Main Texture</b> (16x16
-pixels) which defines the shape of the point sprite used for
-rendering.</li>
-<li><b>Alpha Channel Texture (16*16)</b> - path to the <b>Alpha
-Channel Texture</b> which defines the texture of the point
-sprite.</li>
-<li><b>Alpha Channel Threshold</b> - defines the level of transparency
-ranging from 0 to 1.</li>
-<li><b>Geometrical Sphere Resolution</b> - defines the number of faces
-of <b>Geometry Spheres</b>.</li>
-<li><b>Notify when number of faces exceeds</b> - limitation of the
-number of faces; the user will be warned if it exceeds the given
-value.</li>
-</ul>
-</ul>
-
-<ul>
-<li><b>Size</b> - in this menu you can define:</li>
-<ul>
-<li><b>Range value for min and max size</b> - these two parameters
-will be respectively multiplied by a reference length (average size of
-cells of the mesh) to define the range for minimum and maximum size of
-a point during rendering (at magnification = 100%). Default values
-are:</li>
-<ul>
-<li><b>Rainbow</b> scale: <b>min</b> = <b>10%</b>, <b>max</b> =
-<b>33%</b></li>
-<ul>
-<li>Min size is associated to the smallest real value (including
-negative values).</li>
-<li>Max size is associated to the largest real value.</li>
-</ul>
-<li><b>Bicolor</b> scale: <b>min</b> = <b>0</b> (not editable),
-<b>max</b> = <b>33%</b></li>
-<ul>
-<li>Null size is associated to the 0 scalar value.</li>
-<li>Max size is associated to the largest absolute value.</li>
-</ul>
-</ul>
-Both values are dynamically updated by the system according to the
-selected scalar bar. In the case of a Bicolor scale, the minimum value
-is set to 0 in the dialog and the control is disabled.
-<li><b>Magnification (%)</b> corresponds to the change of size of
-results at Gauss point primitives in 2D space. Acceptable values range
-from 0 to N; 100% means no magnification, 50% means half of its size,
-200% mean twice its size and so forth. By default this value is set to
-100%.</li>
-<li><b>+/- Ratio</b> corresponds to the number by which the
-magnification will be respectively multiplied or divided at edition,
-ranging from 0.01 to 10. By default this value is set to 2.</li>
-</ul>
-</ul>
-
-<ul>
-<li><b>Geometry</b></li>
-<ul>
-<li><b>Size of points (%)</b> defines a value that will be multiplied
-by a reference length (representative of the average size of cells of
-the mesh) to define the size of points during rendering (at
-magnification = 100%). Default values 10%.</li>
-<li><b>Color</b> - allows to select the color of points used for
-presentations. Click on the colored line to access to the \ref
-select_color_and_font_page "Select Color" dialog box.</li>
-</ul>
-</ul>
-
-<ul>
-<li><b>Gauss Points Scalar Bar</b></li>
-<ul>
-<li><b>Active Bar</b> - this option allows to choose <b>Local</b> or
-<b>Global</b> Bar as active.</li>
-<li><b>Display Global Bar</b> - this option allows to visualize or to
-hide the Global Bar.</li>
-<li><b>Scalar Bar Mode</b> - this option allows to choose between
-<b>Bicolor</b> and <b>Rainbow</b> Scalar Bar Mode.</li>
-<li><b>Spacing</b> - allows to define Spacing from 0.01 to 1.</li>
-</ul>
-</ul>
-
-<br><br><b>Inside<b> and </b>Outside Cursor Preferences</b> allow to set
-<b>Primitives</b>, <b>Size</b> and <b>Magnification</b> for the
-respective zones.
-
-<br><h2>Picking Preferences</h2>
-
-\image html pref37.png
-
-<ul>
-<li><b>Cursor</b> - allows to adjust the Size of the cursor used for
-Picking (ranging from 0.1 to 1), the Height of the pyramids (ranging
-from 0 to 10) and the Selection cursor color.</li>
-<li><b>Tolerance</b> - defines at which distance of the cursor from
-the point it becomes selected (ranges from 0.001 to 10).</li>
-<li><b>Information window</b> - allows to define the
-<b>Transparency</b> (from 0% = opaque to 100% = transparent) and
-<b>Position</b> of the window, which can be:</li>
-<ul>
-<li><b>Centred below the point</b>, or</li>
-<li>located at <b>Top-left corner of the 3D view</b></li>
-</ul>
-<li><b>Movement of the Camera</b> can also be define by the user.</li>
-<ul>
-<li><b>Zoom at first selected point</b> - This value is used to define
-the focal distance at the first selected point (at the end of the
-movement of the camera). This value is a ratio that will be multiplied
-by the current zoom value.</li>
-<li><b>Number of steps between two positions</b> - defines the
-smoothness of camera movement at selection by the number of
-iterations. If set to 1 the camera is zoomed and centered at the point
-momentarily. Greater numbers mean very slow camera movement.</li>
-</ul>
-<li><b>Display parent mesh element</b> - allows to visualize or hide
-the patent mesh element of the selected gauss point.</li>
-</ul>
-
-<br><h2>Navigation Preferences</h2>
-
-\image html pref38.png
-
-<br>
-<ul>
-<li><b>Mouse</b></li>
-<ul>
-<li><b>Mouse Behaviour</b> - this option allows to choose one of the
-modes of work with mouse in Gauss Viewer.</li>
-<ul>
-<li><b>Salome Standard Controls</b> - allows to manipulate objects in the
-viewer with the mouse and locked Ctrl button: increase or decrease the
-zoom ratio with the left mouse button, translate object in any
-direction with the central mouse button or rotate it with the right
-mouse button.</li>
-<li><b>Keyboard Free</b> - allows to manipulate objects in the viewer
-with the mouse without locking Ctrl button. In this case the
-operations are assigned to the buttons differently: rotation is made
-with the left button, translation with the right and zoom with both
-pressed in the same time.</li>
-</ul>
-</ul>
-</ul>
-
-<ul>
-<li><b>Keyboard</b></li>
-<ul>
-<li><b>[+]/[-] Speed Increment</b> - defines the number of units by
-which the speed increases or respectively decreases after pressing [+]
-or [-] keyboard buttons.</li>
-</ul>
-</ul>
-
-<ul>
-<li><b>Spacemouse</b> - a mouse-like manipulator device specially designed
-for working with 3D presentations, objects, etc. You can reassign the
-actions listed below to any of its buttons.</li>
-<ul>
-<li><b>Decrease Speed Increment</b> - decreases by 1 the speed increment used for the keyboard (same as [-] key).</li>
-<li><b>Increase Speed Increment</b> - increase by 1 the speed increment used for the keyboard (same as [+] key).</li>
-<li><b>Decrease Gauss Points Magnification</b> - divides the current magnification by the magnification ratio.</li>
-<li><b>Increase Gauss Points Magnification</b> - multiplies the current magnification by the magnification ratio.</li>
-<li><b>Dominant / combined switch</b> - toggles button to switch to dominant or combined movements.</li>
-</ul>
-</ul>
-
-<br><h2>Recorder Preferences</h2>
-
-\image html pref38.png
-
-<ul>
-<li><b>Settings</b></li>
-<ul>
-<li><b>Mode</b> - allows to choose from two recording regimes:</li>
-<ul>
-<li><b>Recording all displayed frames</b> - records exactly at the FPS rate specified by the user.</li>
-<li><b>Recording at a given FPS</b> - records only when the contents
-of the viewer change (some activity is performed). In the AVI file
-non-recorded images are substituted with the copies of the latest
-recorded image, which produces files with lower quality but requires
-less system resources. </li>
-</ul>
-<li><b>FPS</b> - allows to define the FPS (frames per second) rate for
-the clip. Set greater value for better quality.</li>
-<li><b>Quality</b> - allows to set the quality of the clip in the
-interval between 0 and 100.</li>
-<li><b>Progressive</b> - allows to record a progressive API
-file.</li>
-</ul>
-</ul>
-
-*/
+++ /dev/null
-/*!
-
-\page running_salome_page Running SALOME
-
-<em>To launch SALOME:</em>
-<ol>
-<li>Install the SALOME package into a definite directory (ex. \b SALOME)
-on your hard disk. It is preferable if you use the special
-installation procedure allowing to install the SALOME platform and
-all corresponding applications.</li>
-<li>The installation shell script will create a special file:
-<b>salome.csh</b> (CShell file) in your SALOME/KERNEL directory. This file
-contains all environment variables necessary for launching SALOME
-platform with other application products provided with SALOME
-installation package. You have a possibility to add one of them into
-your profile if you enter in the command console the following: <br><br>
-<tt>source salome.csh</tt>
-
-<b>Tip:</b> During the installation procedure you have a possibility to set your profile automatically.</li>
-
-<li> Launch SALOME platform, using the following Python script located
-in the <b>SALOME/KERNEL/bin/salome</b> directory:<br><br>
-<ul>
-<li>\b runSalome.py [command line options]
-</ul>
-</li>
-</ol>
-
-\anchor batch_mode_run
-
-<table>
-<tr>
-<td><h2>Options</h2></td>
-<td><h2>Description</h2></td>
-</tr>
-<tr>
-<td>--\b help or -\b h</td>
-<td>print this help</td>
-</tr>
-<tr>
-<td>--\b gui or -\b g</td>
-<td>launch with GUI</td>
-</tr>
-<tr>
-<td> --\b terminal or -\b t</td>
-<td>launch without GUI in batch mode</td>
-</tr>
-<tr>
-<td>--\b logger or -\b l</td>
-<td>redirects log messages in the file <em>logger.log</em></td>
-</tr>
-<tr>
-<td>--\b file=<b>\<FILE\></b> or -\b f=<b>\<FILE\></b></td>
-<td>redirects log messages in a custom file</td>
-</tr>
-<tr>
-<td>--\b xterm or -\b x</td>
-<td>the servers open an xterm window and log messages are displayed in this window</td>
-</tr>
-<tr>
-<td>--\b modules=\b module1,\b module2,... or -\b m=\b module1,\b module2,...</td>
-<td>list of SALOME modules which will be loaded into the module catalogue</td>
-</tr>
-<tr>
-<td>--\b embedded=<b>registry,study,moduleCatalog,cppContainer</b>,
-or -\b e=<b>registry,study,moduleCatalog,cppContainer</b></td>
-<td>embedded CORBA servers (default: registry,study,moduleCatalog,cppContainer)
-note that logger,pyContainer,supervContainer can't be embedded</td>
-</tr>
-<tr>
-<td>--\b standalone=<b>registry,study,moduleCatalog,cppContainer,pyContainer,supervContainer</b>, or
--\b s=<b>registry,study,moduleCatalog,cppContainer,pyContainer,supervContainer</b></td>
-<td>standalone CORBA servers (default: pyContainer,supervContainer)</td>
-</tr>
-<tr>
-<td>--\b containers=<b>cpp,python,superv</b>
-or -\b c=<b>cpp,python,superv</b></td>
-<td>launch of cpp, python and supervision containers</td>
-</tr>
-<tr>
-<td>--\b portkill or -\b p</td>
-<td>kill SALOME launched with the current port</td>
-</tr>
-<tr>
-<td>--\b killall or -\b k</td>
-<td>kill SALOME</td>
-</tr>
-<tr>
-<td>--<b>interp</b>=<b>n</b> or -<b>i</b>=<b>n</b></td>
-<td>number of additional xterm to open, with session environment</td>
-</tr>
-<tr>
-<td>-\b z</td>
-<td>display splash screen</td>
-</tr>
-<tr>
-<td>-\b r</td>
-<td>disable centralized exception handling mechanism</td>
-</tr>
-</table>
-
-<b>Tip:</b> If the \b runSalome.py script is launched without prompting
-any options, they will be taken by default from the file <b>SalomeApp.xml
-(SALOME/GUI/share/salome/resources/SalomeApp.xml)</b>. 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.
-
-*/
\ No newline at end of file
+++ /dev/null
-/*!
-
-\page salome_architecture_page SALOME architecture
-
-
-\b SALOME architecture is based on \b CORBA technology using
-distributed system model of applications. This architecture takes the
-concept of multitier client/server to its natural conclusion. The
-distributed system model exposes all functionality of the application
-as objects, each of which can use any of the services provided by
-other objects in the system, or even objects in other systems. The
-architecture can also blur the distinction between "client" and
-"server" because the client components can also create objects that
-behave in server-like roles. This architecture provides the ultimate
-in flexibility.
-
-
-
-The distributed system architecture achieves its flexibility by
-encouraging (or enforcing) the definition of specific component
-interfaces. The interface of a component specifies to other components
-what services are offered by that component and how they are used. As
-long as the interface of a component remains constant, that
-component's implementation can change dramatically without affecting
-other components.
-
-
-
-All software components (Post-Pro, Geometry, Mesh...) integrated into
-\b SALOME platform implement predefined interfaces. Each component
-provides data for the \b SALOME study in a form of links (stored in
-the Study) to the specific data created and stored in the
-component. All components represent \b CORBA servers and it allows to
-run them on different host stations.
-
-\image html image67.gif
-
-
-It is equally possible to create engine-independent modules. These
-modules may not use CORBA at all, and can have internal data structure
-which can be written in pure C++ (or python). Such modules are located
-inside SALOME GUI process and from the point of view of the end user
-have no difference with standard components. Such modules not using
-the standard tools of SALOME platform are defined on a special
-separated level named CAM. CAM component is the basis for new SALOME
-GUI and contains all basic functionality for working with modules
-(loading; saving, closing, customization of toolbar and menu).
-
-
-
-Another fundamental piece of the \b SALOME architecture is the use of
-the Interface Definition Language (IDL). IDL, which specifies
-interfaces between CORBA components, is instrumental in ensuring
-CORBA's language independence. Because interfaces described in IDL can
-be mapped to any programming language, CORBA applications and
-components are thus independent of the language(s) used to implement
-them.
-
-
-Additional information about CORBA technology
-is available at http://www.omg.org
-
-\note In \b SALOME there is a possibility to run
-definite components in the so-called \ref batch_mode_run "batch mode" without GUI provided
-by GUI component. In this case you can work with these components with
-the help of Python commands and scripts.
-
-
-The architecture of this all-inclusive
-platform for numerical components responds to the following
-objectives:
-<ol>
-<li>\b Flexibility : the creation and modification of computation
-schemes must be easy. The developer must have easy access to all
-modeling parameters to create domain-specific tools adapted to new
-situations or to test new numerical algorithms. SALOME allows
-integration and implementation of numerical and physical components
-derived from existing code.</li>
-<li>\b Productivity : the implementation of code is simple for the
-user and the reuse of components (within other environments for
-macro-components) is noticeably facilitated.</li>
-<li> \b Performance :\b SALOME is able to more finely simulate
-phenomena that is more complex in scale and in physical coupling
-requirements. \b SALOME economically exploits the performance of used
-machines (massively parallel processors, PC clusters, etc).</li>
-<li> \b Expandability: on the one hand, software technologies and
-physical architectures evolve rapidly compared to the development
-time, validation and use of a scientific application while on the
-other hand, the development of a database model adapted to the
-totality of exchanges between components can be achieved
-incrementally. \b SALOME is able to easily follow these
-developments.</li>
-</ol>
-
-*/
\ No newline at end of file
+++ /dev/null
-/*!
-
-\page salome_desktop_page SALOME desktop
-
-The main SALOME Desktop consists of the following sections and
-toolbars:
-
-\image html geomview-alt.png
-
-<b>Basic parts of the SALOME Desktop:</b>
-<ul>
-<li><b>Main menu</b> - This is a set of context-sensitive menus, which will
-be updated according the functionality of the loaded component. In
-general, these menus contain all functional options of SALOME
-platform.</li>
-<li><b>Standard Toolbar</b> - This toolbar contains icons allowing
-creating/saving studies, correcting mistakes, copying/pasting
-objects.</li>
-<li><b>Components Toolbar</b> - This toolbar is destined for uploading
-components in SALOME platform.</li>
-<li><b>Module Toolbar</b> - This toolbar contains icons specific to the
-loaded module.</li>
-<li><b>Viewer Toolbar</b> - This is a set of tools destined for visualization
-of the presentations in the viewer.</li>
-</ul>
-
- All toolbars in the
-\b SALOME Platform are context-sensitive. Loading of a definite component
-(Geometry, Post-Pro, Mesh etc.) will automatically add some additional
-toolbars specific to this component. To display/hide a definite
-toolbar, in the main menu choose <b>View > Toolbars</b>, and from this
-submenu check or uncheck the toolbar, you would like to display/hide.
-
- By default all
-toolbars are located on the top of the SALOME desktop. But you can
-relocate toolbars by dragging with the mouse and dropping it in any
-place of the window.
-
-<b>Parts of the study window:</b>
-<ul>
-<li><b>Object Browser</b> - Management of objects created or imported into
-SALOME application.</li>
-<li>\b Viewer - This window is destined for visualization of
-presentations.</li>
-<li><b>Python console</b> - Window for Python interpreter. This window
-functions like a standard document: the pop-up menu invoked by
-right-click in this window gives access to
-<b>Copy/Paste/SelectAll/ClearAll</b> options.</li>
-</ul>
-
- Object Browser, Python
-Console, MenuBar, etc are, in fact, separate dockable windows.
-Dockable windows can be placed in special areas, on the borders of
-desktop like toolbars. You can change the size and the position of
-dockable windows, hide them or even place outside desktop. SALOME
-saves in the same file all positions and sizes of dockable windows. It
-means that the difference in settings of the same windows (for example
-Python console) is possible between different modules (the same window
-can have different size and position when other module is
-activated). Also each module can indicate which common windows are
-necessary for working, and only they will be displayed when this
-module is active.
-
- Starting from the
-version 3.0.0 Salome uses a <b>Multi-Desktop Approach</b>. Multi-desktop
-Approach means that now there is separate Desktop for each document
-(Study) and all windows connected to a Study (viewers, dockable
-windows etc) are placed in one container. It is very comfortable,
-because you can't mix up windows from different studies. This approach
-positively differs from the classic multi document interface in case
-if many windows are used, i.e. when one document contains a lot of
-viewers, dialogs, etc. Each desktop also has its own menu and toolbar.
-
-*/
\ No newline at end of file
+++ /dev/null
-/*!
-
-\page salome_preferences_page SALOME preferences
-
-To begin setting preferences for your study, select \b Preferences in the
-main menu, the following dialog box will appear:
-
-\image html pref11.png
-If you've just started your study and haven't yet loaded other
-modules, you'll be able to change only those settings, which refer to
-the whole GUI SALOME session. These settings will be valid for the
-whole study session.
-
-<h2>General Preferences</h2>
-
-<ul>
-<li><b>Study Properties</b></li>
-<ul>
-<li><b>MultiFile Save</b> - if checked in, your study will be saved in
-several HDF files (one file for the data created by each component
-used during the study session).</li>
-<li><b>ASCII Save</b> - if checked in, your study will be saved in
-ASCII format file (or files).</li>
-<li><b>Store positions of windows</b> - if checked in, positions of windows
-will be saved in a special file at the end of the current session and
-then restored for a new session.</li>
-<li><b>Store/restore last GUI state</b> - if checked in, all GUI settings are
-saved with the rest of the data whenever you save the study. When the
-study is reopened, the GUI state is restored.</li>
-</ul>
-<li><b>External browser</b></li>
-<ul>
-<li>\b Application - this option allows you to set an external browser (IE,
-Netscape) which will be used for viewing SALOME reference manuals. By
-default, Mozilla is used. Press the "<b>...</b>" button(see
-the picture below) to browse for the application you need in the data
-tree of your computer.</li>
-<li>\b Parameters</li>
-</ul>
-<li><b>Python console properties</b> - here you can quickly set the
-parameters (style, size, face) of the font used in your Python
-console.</li>
-</ul>
-\par
-For detailed settings in \ref select_color_and_font_page "Select Font"
-dialog box press the "<b>...</b>" button(see the picture below).
-
-\image html image69.gif ""..." button"
-
-<br><h2>Viewers Preferences</h2>
-
-\image html pref12.png
-
-<ul>
-<li><b>OCC and VTK 3D Viewers</b></li>
-<ul>
-<li><b>Trihedron size</b> - this submenu allows to set the size of
-coordinate axes displayed in the viewer.</li>
-<li><b>Background Color</b> - this submenu allows to select background
-color. Click on the colored line to access to the
-\ref select_color_and_font_page "Select Color" dialog box.</li>
-<li><b>Number of isolines along U</b> (or <b>V</b>) - this submenu allows to specify
-the number of isolines along the axes of coordinates.</li>
-<li><b>Relative size</b> - if checked in, trihedron axes scale to fit the
-size of the area displayed in 3D Viewer.</li>
-</ul>
-<br>
-<li><b>Plot2d Viewer</b></li>
-<ul>
-<li><b>Legend Position</b> - this submenu allows to set the default position
-of the legend, it can be located to the left, to the right, on top or
-on bottom of the graph.</li>
-<li><b>Curve Type</b> - this allows to set the representation of graphs in
-your presentations. You can see only <b>Points</b>, points connected with
-<b>Lines</b> or points connected with smooth <b>Splines</b>.</li>
-<li><b>Marker Size</b> - this submenu allows you to set the size of
-markers in your graphs</li>
-<li><b>Horizontal & Vertical Axis Scale</b> - this submenu allows you to set
-the scale for vertical and horizontal axes. It can be either <b>Linear</b> or
-<b>Logarithmic</b></li>
-<li>Background Color - this submenu allows to select the background
-color. Click on the colored line to access to the
-\ref select_color_and_font_page "Select Color" dialog box.</li>
-</ul>
-<br>
-<li><b>Graph Supervisor</b></li>
-<ul>
-<li><b>Background Color</b> - this submenu allows to select background
-color. Click on the colored line to access to the
-\ref select_color_and_font_page "Select Color" dialog box.</li>
-<li><b>Title Color</b> - this submenu allows to select title color. Click on
-the colored line to access to the
-\ref select_color_and_font_page "Select Color" dialog box.</li>
-</ul>
-</ul>
-
-<br><h2>Directories Preferences</h2>
-
-\image html pref13.png
-
-<ul>
-<li>
-<b>Quick Directory List</b> - this section allows to create and manage
-a custom quick directory list. To add a directory in the list, press
-the "Add directory" button:
-\image html image70.gif
-
-then the "<b>...</b>" button and browse the data tree for the
-directory you need.
-The "Up" and "Down" buttons(see the picture below) help you to sort
-the directories in the list:
-\image html image73.gif
-
-\image html image75.gif
-To remove the selected directory from the list, press the "Delete"
-button:
-\image html image72.gif
-</li>
-</ul>
-
-<br><h2>Object Browser Preferences</h2>
-
-\image html pref14.png
-
-<ul>
-<li><b>Object browser settings</b></li>
-<ul>
-<li><b>Auto size for the first column</b> - this checkbox enables automatic
-resizing for the first column.</li>
-<li><b>Auto size for other columns</b> - this checkbox enables
-automatic resizing for the other columns.</li>
-<li><b>Resize columns after expanding an item</b> - this checkbox enables
-resizing columns on expanding an object browser item.</li>
-</ul>
-</ul>
-
-<ul>
-<li><b>Default columns</b> - these checkboxes allow to display or hide <b>Value</b>,
-<b>Entry</b>, <b>IOR</b> and <b>Reference entry</b> columns in the Object Browser.</li>
-</ul>
-
-*/
\ No newline at end of file
+++ /dev/null
-/*!
-
-\page saving_and_closing_studies_page Saving and closing studies
-
-In \b SALOME a study can be saved in \b HDF binary (by default) or \b ASCII
-files (see also: \ref salome_preferences_page "Setting ASCII save option").
-
-You can also specify two options of saving your study:
-<ul>
-<li><b>In one HDF file:</b> in this case all components used during this
-study session will write their data into one common HDF file.
-</li>
-<li>
-<b>In multiple files</b> (see also: \ref salome_preferences_page
-"Setting Multifile save option") : in this
-case SALOME will create one base HDF file which will store the main
-information about the saved study and several other special files with
-particular extensions storing the data written by each component which
-has been used during this study session. Opening of this study
-requires that \b ALL saved files should be stored in the \b SAME directory.
-If you would like to copy your saved study in another directory or
-machine, you should copy all stored files. Otherwise, if you try to
-open this study, some data will be lost and it will lead to invalid
-functioning of the SALOME platform.
-</li>
-</ul>
-
-Saving a study you also save its layout, i.e. all positions and sizes
-of dockable windows. It means that the difference in settings of the
-same windows (for example Python console) is possible between
-different modules (the same window can have different size and
-position when other module is activated). Also each module can
-indicate which common windows are necessary for working, and only they
-will be displayed when this module is active.
-
-<em>To save an existing study:</em>
-\par
-In the main toolbar click "Save document" button or from the main menu
-select <b>File > Save</b> option. Your study will be automatically
-updated.
-
-\image html save.jpg ""Save document" button"
-
-\note If your study hasn't been previously saved, this option will
-call the standard Search File dialog box where you can enter the name
-for your study and save it.
-
-<em>To save a study with a new name:</em>
-\par
-From the main menu select <b>File > Save as</b> option. In the standard
-Search File dialog box enter a new name for your study and click \b Save
-button.
-
-<em>To save the current layout of the GUI:</em>
-\par
-From the main menu select <b>File > Save VISU State</b>. The current
-state of the graphic interface is published in Object Browser in the
-folder GUI states and can be at any time \b Restored, \b Renamed or \b
-Deleted. This operation saves and allows to
-restore almost all GUI settings: names, position, zooming and panning
-of viewers and all displayed objects (in Post-Pro module only).
-
-<em>To close a study:</em>
-\par
-In the main toolbar click "Close document" button or from the main menu select <b>File > Close</b>
-option or click on the cross in the upper right corner of the study
-window.
-
-\image html image94.gif ""Close document" button"
-
-\note If your study hasn't been previously saved, this option will
-call the following dialog box with several options:
-
-\image html closestudy.png
-
-\n\b Unload option allows to unload your current study from the SALOME
-Desktop. In the same working session you can reload it again (see:
-\ref opening_studies_page "Opening studies"). But if you quit the SALOME application, all changes
-in the unloaded study will be lost.
-
-*/
+++ /dev/null
-/*!
-
-\page select_color_and_font_page Select Color and Font
-
-<b>Select Color</b> and <b>Select Font</b> menus are used in many
-Preferences.
-
-<br><h2>Select color</h2>
-
-\image html selectcolor.png
-
-This menu allows to choose from either predefined <b>Basic Colors</b>
-grouped in the upper left corner of the window or <b>Custom Colors</b>, which
-you can define yourselves. To define a Custom Color, click on one of
-the Custom Color cells, select the color you need in the field of
-colors or by typing in its numeric parameters in the lower right
-corner of the window, then click <b>Add to Custom Colors</b> button. The
-chosen color will be added to <b>Custom Colors</b> table.
-
-<br><h2>Select font</h2>
-
-\image html selectfont.png
-
-This menu provides a wide choice of \b Fonts, <b>Font Styles</b> and
-\b Sizes. Characters can be underlined or struck out. It is possible to
-preview them in the \b Sample window. \b Script dialog-box gives the
-possibility to use not only Latin and Latin Extended but also
-Cyrillic, Greek, Arabic, Runic and many other subsets.
-
-*/
\ No newline at end of file
+++ /dev/null
-/*!
-
-\page setting_preferences_subpage Setting Preferences
-
-In \b SALOME you can set preferences for each module in the common editor
-of preferences. SALOME preferences refer to the whole GUI SALOME
-session, other preferences are module-specific and are accessible only
-after you load a respective module.
-\n When you change settings (click \b OK or \b Apply button) each module
-receives the notification about what preferences are changed. You can
-also click \b Defaults button to restore default preferences or \b Close
-button to quit the menu without any changes.
-\n \b Import button allows to load a user file containing preferences
-from your home directory through a standard Import dialog box.
-
-\image html import.png
-
-This file has no extension and by default starts with
-.SalomeApprc. followed by Salome version number. There exists one file
-for each Salome version in use.
-\n The preferences, set during the current study session, are
-automatically saved in this file at the end of the session. Next time
-you launch SALOME application, these preferences will be restored.
-
-\note The preferences you set will be default preferences for all \b new
-objects, but they are not retroactive and do not automatically apply
-to the existing objects.
-
-*/
\ No newline at end of file
+++ /dev/null
-/*!
-
-\page setting_preferences_page Setting Preferences
-
-<ul>
-<li>\subpage setting_preferences_subpage</li>
-<li>\subpage select_color_and_font_page</li>
-<li>\subpage salome_preferences_page</li>
-<li>\subpage geometry_preferences_page</li>
-<li>\subpage mesh_preferences_page</li>
-<li>\subpage postpro_preferences_page</li>
-</ul>
-
-*/
\ No newline at end of file
+++ /dev/null
-/*!
-
-\page setting_study_properties_page Setting study properties
-
-<em>To view the properties of the current study:</em>
-\par
-From the main menu select \b File > \b Properties option. The following
-dialog box will appear:
-
-\image html studyproperties.png
-
-This dialog box gives complete information about your study.
-
-<em>To change the name of the study author:</em>
-\par
-In this dialog box click on the \b Author field and enter a new name.
-
-<em>To view the list of changes made with your study:</em>
-\par
-In this dialog box click on the \b Modifications field and scroll it
-down. Each record contains the following information: date and time of
-modification of the study, name of the user, who has made these
-changes.
-
-<em>To lock your study for modifications:</em>
-\par
-In the dialog box shown on the picture above click on the \b Locked
-field and choose \b Yes item.
-
-In this case your study will be locked for any kind of modifications
-for all users. Next time you try to edit it, you will see the
-following warning message:
-
-\image html lockedstudy.png
-
-*/
\ No newline at end of file
+++ /dev/null
-/*!
-
-\page study_management_page Study management
-
-<ul>
-<li>\subpage creating_new_study_page</li>
-<li>\subpage opening_studies_page</li>
-<li>\subpage saving_and_closing_studies_page</li>
-<li>\subpage editing_studies_page</li>
-<li>\subpage displaying_studies_page</li>
-<li>\subpage working_with_python_scripts_page</li>
-<li>\subpage setting_study_properties_page</li>
-</ul>
-
-*/
\ No newline at end of file
+++ /dev/null
-/*!
-
-\page using_catalog_generator_page Using Catalog Generator (for advanced users)
-
-SALOME platform is an open platform for
-integration of your custom components, which can used in the same way
-as typical modules provided in the standard installed package. The
-<b>Catalog Generator</b> tool serves for implementation of the interface of
-your custom component. It allows to generate from IDL description of
-your component interface its xml description. The component xml
-description allows SALOME application to know about the component and
-its services and provides the possibility to call the component
-services, for example, inside Supervisor module.
-
-If you have a look at runSalome,
-runSalomeWithPort scripts running SALOME application, which are stored
-in build/bin directory you will see that SALOME_ModuleCatalog_Server
-is started with two xml files as its input parameters:
-\b CatalogModuleGeneral.xml and \b CatalogModulePersonnel.xml. These two
-files store the descriptions of interfaces and services of all
-components, provided with typical SALOME package. To add a new
-component into SALOME platform you should either update one of these
-existing xml files with generated xml description of your component or
-create a new one.
-
-<em>To open the Catalog Generator:</em>
-\par
-From the main menu choose <b>Tools > Catalog Generator</b>, the following
-dialog box will appear:
-
-\image html cataloggenerator.png
-
-<br>In this dialog box you can specify:
-<ul>
-<li>Name and location of the IDL file describing the interface of your
-component (Click the \b Browse button to find it using the data tree).</li>
-<li>Name and location of an existing XML file, which will be updated
-with the interface of you component or name and desired location of a
-new XML file, which will be generated (Click the \b Browse button to find
-it using the data tree).</li>
-<li>Name of the author.</li>
-<li>Name of the component.</li>
-<li>Name of the user.</li>
-<li>Version.</li>
-<li>Capability of multi study support.</li>
-<li>Type of the component.</li>
-<li>Icon of your component (Click the \b Browse button to find it using
-the data tree).</li>
-</ul>
-
-\note If you have chosen to create a new xml file containing the
-description of your component, don't forget to specify it as
-input parameter for SALOME_ModuleCatalog_Server in the file, you are
-using as a running script of SALOME platform (in runSalomeWithPort,
-for example).
-
-When launching SALOME next time you will see your module alongside other components.
-
-\b Tip: You can use the <b>Catalog Generator</b> tool, if you would like to \b
-test the functionality of your new component. After implementation of
-your component interface, launch SUPERVISION module where you can try
-using the services of your new component. (see also: Adding factory
-nodes)
-
-*/
\ No newline at end of file
+++ /dev/null
-/*!
-
-\page using_find_tool_page Using Find toolbox
-
-The <b>Object Browser</b> is supplied with the \b Find toolbox. This tool
-allows performing context search of the items in the Object Browser:
-
-\image html findtool1.png
-
-The \b Find toolbox can be invoked in several ways:
-- Pressing \a <Ctrl>-<F> key combination starts new
-search; the text previously entered by the user in the edit control of
-the \b Find toolbox is automatically selected.
-- Pressing \a </> (slash) key starts new search; the text
-previously entered by the user is cleared.
-- Pressing \a <F3> key repeats previous search in the forward
-direction (from top to bottom).
-- Pressing \a <Shift>-<F3> key repeats previous search in
-the backward direction (from bottom to top).
-- Activating \a Find command from the Object Browser context popup
-menu starts new search (the same as \a <Ctrl>-<F>).
-
-Pressing \a <Escape> key closes the \b Find toolbox.
-
-The search is always started beginning from the first selected item in
-the Object Browser. If there are no selected items, the search is
-started from the top of the Object Browser contents. If there is an
-item which satisfies the search conditions, it is selected and
-Object Browser is expanded to show this item (if it is collapsed).
-
-The \b Find toolbox provides a set of widgets which are used to
-perform the search operations or affect on the search conditions:
-- \a "Close" button closes the \b Find toolbox.
-- Line edit box is used to enter the text to be searched. Note that
-search is alwasy done by the object name, i.e. by the data displayed
-in the "Name" column of the Object Browser.
-- \a "Find first item" button searches the very first item
-which satisfies the search condition.
-- \a "Find previous item" button searches the previous item
-which satisfies the search condition.
-- \a "Find next item" button searches the next item
-which satisfies the search condition.
-- \a "Find last item" button searches the very last item
-which satisfies the search condition.
-- \a "Case sensitive" check box allows performing case sensitive
-search.
-- \a "Regular Expression" check box allow performing the search of the
-items by the regular expression, for example:
- - <i>Face</i> - matches all faces
- - <i>Face_[\\d]</i> - matches Face_1, Face_2, etc.. (all faces)
- - <i>Face_[\\d]$</i> - matches Face_1, Face_2, but not matches Face_11, Face_12.
- - <i>^Face_[\\d]$</i> - same as above
- - <i>^ Face_[\\d]$</i> - matches nothing
-
-- \a "Wrap search" check box: when it is switched on and search
-reaches last item, satisfying the search conditions, pressing \a "Find
-Next" button moves the selection to the very first item which matches
-search conditions (i.e. cyclic search is performed).
-
-If there are no items in the Object Browser which satisfy the search
-conditions, the edit control of the \b Find toolbox becomes
-red-colored:
-
-\image html findtool2.png
-
-The \b Find toolbox has also auto-hiding feature. This works as
-follows:
-- If input focus is inside the \b Find toolbox, auto-hiding is
-automatically deactivated.
-- If input focus moves outside the \b Find toolbox, it hides
-automatically in 10 seconds after the last search operation (which can
-be done by clicking \a "Find Next", \a "Find Previous" button, or typing
-something in the edit field); it means that each new search operation
-restarts the auto-hide timer.
-
-*/
+++ /dev/null
-/*!
-
-\page using_object_browser_page Using Object Browser
-
-The <b>Object Browser</b> in SALOME is destined for displaying the
-structure of the current study in a tree-like form. It contains:
-
-<ul>
-<li>components, loaded during the current session</li>
-<li>objects created with the help of different components (The objects
-created with the help of a definite component are located in the
-folder having the name of this component)
-</li>
-<li>references to different objects (they are highlighted in red)</li>
-</ul>
-
-\image html objectbrowser1.png
-
-\note The <b>Object Browser</b> is destined to getting quick access to
-different objects created during SALOME session. All pop-up menus
-associated with the objects displayed in the Object Browser are
-context-sensitive. So it depends on a definite currently loaded SALOME
-component what options you will see in the pop-up menu, if you
-right-click on a definite object in the Object Browser.
-
-The Object Browser may contain supplementary attributes of the objects
-displayed in additional columns. By default, these columns are not
-displayed - displaying/hiding these columns is possible through
-\ref salome_preferences_page "setting study preferences" or
-right-clicking on the attributes bar and toggling the necessary
-attributes.
-
-\image html objectbrowser2.png
-
-<ul>
-<li>\b Entry - Identification index of the object in the structure of
-the study</li>
-<li>\b IOR - Interoperable Object Reference</li>
-<li><b>Reference entry</b> - Identification index of the references
-to the objects</li>
-<li>\b Value - Displays the value of the first object attribute</li>
-</ul>
-
-\note <b>Entry, IOR and Reference entry</b> attributes are displayed for debugging purposes only.
-
-*/
\ No newline at end of file
+++ /dev/null
-/*!
-
-\page using_registry_tool_page Using Registry tool
-
-\b Registry tool is in the SALOME platform is destined for providing
-information about the processes (components), which have ever been
-launched in the current study session.
-
-<em>To view the Registry:</em>
-\par
-From the main menu choose <b>Tools > Registry display</b>, the
-following dialog box will appear:
-
-\image html registry1.png
-
-\b Running tab of this dialog box displays a list of the currently
-started processes (components) with supplementary information on each
-of them divided into columns:
-
-<ul>
-<li>\b Component: name of the started component
-<li>\b PID: process identification number
-<li>\b User \b Name: name of the user launching the component
-<li>\b Machine: name of the machine, on which the process has been started
-<li>\b begins: date and time of the starting of the component
-<li>\b hello: date and time of the last call to the component
-</ul>
-
-\b History tab displays a list of all processes, which have ever been
-launched within this study session. It contains the same supplementary
-information on each of the processes (components).
-
-\b Refresh button allows to refresh the current list of processes
-(components).
-
-\b Interval button allows to set an interval for refreshment of the
-current list of processes (components).
-
-\image html registry3.png
-
-<em>To display complete information on a definite process
-(component):</em>
-\par
-Double-click on this process (component). The following window will
-appear:
-
-\image html registry4.png
-
-*/
\ No newline at end of file
+++ /dev/null
-/*!
-
-\page viewers_page Viewers
-
-<ul>
-<li>\subpage occ_3d_viewer_page</li>
-<li>\subpage vtk_3d_viewer_page</li>
-<li>\subpage plot2d_viewer_page</li>
-</ul>
-
-*/
+++ /dev/null
-/*!
-
-\page vtk_3d_viewer_page VTK 3D Viewer
-
-<b>VTK 3D viewer</b> is the default viewer for Mesh Module, allowing to
-visualize meshes. It is also used in Post-Pro module for all 3D
-presentations except for Gauss Points.
-
-The functionalities of VTK viewer are available via its Viewer
-Toolbar. Buttons marked with small downward triangles have extended
-functionality which can be accessed by locking on them with left mouse
-button.
-
-\image html image157.gif "Viewer Toolbar"
-
-<hr>
-\image html image77.gif
-\n <center><b>Dump View</b> - exports an object from the viewer in bmp, png, jpg
-or jpeg image format.</center>
-<hr>
-
-\image html image88.gif
-\n <center><b>Show/Hide Trihedron</b> - shows or hides coordinate axes.</center>
-<hr>
-
-\image html image96.gif
-\n <center><b>Fit all</b> - scales the presentation so that it could
-fit within the Viewer boundaries. </center>
-<hr>
-
-\image html image97.gif
-\n <center><b>Fit area</b> - resizes the view to place in the visible area
-only the contents of a frame drawn with pressed left mouse button.</center>
-<hr>
-
-\image html image98.gif
-\n <center><b>Zoom</b> - allows to zoom in and out.</center>
-<hr>
-
-\image html image99.gif
-\n <center><b>Panning</b> - if the represented objects are greater that the
-visible area and you don't wish to use <b>Fit all</b> functionality, click on
-this button and you'll be able to drag the scene to see its remote
-parts.</center>
-<hr>
-
-\image html image100.gif
-\n <center><b>Global panning</b> - allows to select a point to be the
-center of the presentation showing all displayeed objects in the
-visible ares <center>
-<hr>
-
-\image html view_rotation_point.png
-\n <center><b>Change rotation point</b> - allows to to choose the point around
-which the rotation is performed.</center>
-
-\image html set_rotation_point_dialog1.png
-
-<center>By default the rotation point is located in the Center of the bounding
-box of an object.</center>
-
-\image html set_rotation_point_dialog2.png
-
-<center>Unchecking <b>Use Bounding Box Center</b> checkbox allows you to
-define the coordinates of the rotation point manually.</center>
-
-<b>Set to Origin</b> button restores the default rotation point
-coordinates.\n
-<b>Select Point from View</b> button allows to select the rotation
-point in the 3D Viewer.
-<hr>
-
-\image html image89.gif
-\n <center><b>Rotation</b> - allows to rotate the selected object using the
-mouse.</center>
-
-\image html image102.gif
-
-<center>These buttons orientate the scene strictly about coordinate axes.</center>
-<hr>
-
-\image html image91.gif
-\n <center><b>Reset</b> - restores the default position (isometric) of
-objects in the scene.</center>
-<hr>
-
-\image html urbutton.png
-\n <center><b>Update Rate</b> - allows to define the Update Rate for
-the presentations displayed in the viewer</center>
-
-\image html updaterate.png
-
-<ul>
-<li><b>Desired Update Rate, FPS</b> - allows to set the target Update
-Rate</li>
-<li><b>Still Update Rate, FPS</b> - allows to set the Update Rate for
-the periods when both the user and the application do not perform any
-actions in the viewer</li>
-<li><b>Current Update Rate, FPS</b> - shows the Update Rate currently
-available on your configuration</li>
-<li><b>Number of Cells</b> - shows the number of cells currently in
-display</li>
-</ul>
-
-\image html image108.gif
-\n <center><b>Scaling</b> - represents objects deformed (stretched or
-stuffed) along the axes of coordinates.</center>
-<hr>
-
-\image html image109.gif
-\n <center><b>Graduated axes</b> - allows to define parameters of axes
-and graduate them.</center>
-
-\image html graduatedaxes1.png
-
-<ul>
-<li><b>Axis name</b></li>
-<ul>
-<li><b>Is visible</b> - if checked the axis name is displayed in the
-viewer.</li>
-<li><b>Name</b> - allows to redefine the name of the axis.</li>
-<li><b>Font</b> - allows to define color and properties of the font of
-axis name.</li>
-</ul>
-<li><b>Labels</b></li>
-<ul>
-<li><b>Is visible</b> - if checked the labels are displayed in the
-viewer.</li>
-<li><b>Number</b> - allows to define the number of labels.</li>
-<li><b>Offset</b> - allows to define the distance between labels.</li>
-<li><b>Font</b> - allows to define color and properties of the font of
-labels names.</li>
-</ul>
-<li><b>Tick marks</b></li>
-<ul>
-<li><b>Is visible</b> - if checked the tick marks are displayed in the
-viewer.</li>
-<li><b>Length</b> - allows to define the length of tick marks.</li>
-</ul>
-<li><b>Is visible</b> - if checked the axis is displayed in the
-viewer. </li>
-</ul>
-
-*/
\ No newline at end of file
+++ /dev/null
-/*!
-
-\page working_with_python_scripts_page Working with Python Scripts
-
-\b SALOME Platform can be launched in the batch mode, without Graphical
-User Interface, and operated with the use of Python scripts, which can
-fulfill most of the necessary tasks, however, the process of scripting
-is quite time consuming and rather error-prone.
-\n This problem has been resolved by the possibility to automatically
-generate a set of Python scripts from data created with SALOME GUI,
-which greatly increases the productivity of using SALOME platform in
-the batch mode. This mechanism can convert a SALOME Study in one or
-several Python scripts, which can be stored and imported later to
-re-create the content of the original study. The first script is a
-SALOME document, which re-creates the SALOME Study, adds the
-stored Salome components to the SALOME and automatically calls
-Python scripts of the second type containing component specific Python
-function calls. This architecture gives great flexibility in manual
-modification of the generated scripts because you can modify only one
-of the component specific Python scripts without touching others, thus
-avoiding expert knowledge of Python API of unused components.
-
-To Dump a SALOME Study in one or several scripts, in the main menu
-select \b File --> <b>Dump study</b>
-\n The following dialog box allowing to browse for the location and
-define the name for a Python file will appear:
-
-\image html dumpstudy.png
-
-\par
-<ul>
-<li>
-<b>Publish in study</b> - if checked in, the component objects created by
-Python commands will be published in the created Study when the script
-is played, otherwise the objects will not be published in the Study.
-</li>
-<li>
-<b>Save GUI state</b> - if checked in, the current application layout will be
-saved in the Python file.
-</li>
-</ul>
-To confirm your choice click \b Save.
-
-Reversibly it is possible to load a saved Python Script selecting in
-the main menu \b File -> <b>Load Script</b>.
-
-\image html loadscript.png
-
-\par
-To confirm your choice click \b Open.
-
-*/
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-</head>
-<body>
-<hr style="width: 100%; height: 2px;">
-<div style="text-align: center;">Copyright © 2003-2007 CEA, EDF<br>
-</div>
-</body>
-</html>
+++ /dev/null
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
- <title>$title</title>
- <link href="doxygen.css" rel="stylesheet" type="text/css">
-</head>
-<hr>
-<center>
-SALOME documentation central
-</center>
-<hr>
include $(top_srcdir)/adm_local/unix/make_common_starter.am
-EXTRA_DIST+=GUI
+EXTRA_DIST += images input static
-doxygen=@DOXYGEN@
-
-usr_docs:
- cd ./GUI; \
+usr_docs: doxyfile
echo "Running doxygen in directory: "`pwd`; \
- $(doxygen) ./doxyfile;
+ $(DOXYGEN) $<
docs: usr_docs
clean-local:
- cd ./GUI; \
- rm -fr `ls | grep -v "doxyfile"`
- rm -fr `ls | grep -vE "Makefile|GUI"`
+ -rm -fr GUI doxygen.bak
install-data-local: usr_docs
- mkdir -p $(docdir)/gui
- cp -rf GUI $(docdir)/gui
- -find $(PWD) -name CVS -prune -exec rm -rf {} \;
+ $(INSTALL) -d $(DESTDIR)$(docdir)/gui
+ cp -rp GUI $(DESTDIR)$(docdir)/gui
uninstall-local:
- rm -rf $(docdir)/gui/GUI
-
-docguidir=$(docdir)/gui/GUI
-
-nodist_docgui_DATA= GUI/doxyfile
-GUI/doxyfile: GUI/doxyfile.in
-EXTRA_DIST+= GUI/doxyfile.in
+ rm -rf $(DESTDIR)$(docdir)/gui
--- /dev/null
+#---------------------------------------------------------------------------
+# Project related configuration options
+#---------------------------------------------------------------------------
+PROJECT_NAME = "GUI Module Reference Manual v.@VERSION@"
+OUTPUT_DIRECTORY = GUI
+CREATE_SUBDIRS = NO
+OUTPUT_LANGUAGE = English
+TAB_SIZE = 5
+
+#---------------------------------------------------------------------------
+# configuration options related to warning and progress messages
+#---------------------------------------------------------------------------
+QUIET = NO
+WARNINGS = YES
+
+#---------------------------------------------------------------------------
+#Input related options
+#---------------------------------------------------------------------------
+INPUT = @srcdir@/input
+FILE_PATTERNS = *.doc
+IMAGE_PATH = @srcdir@/images
+
+#---------------------------------------------------------------------------
+#HTML related options
+#---------------------------------------------------------------------------
+GENERATE_HTML = YES
+HTML_OUTPUT = .
+HTML_HEADER = @srcdir@/static/header.html
+HTML_FOOTER = @srcdir@/static/footer.html
+#HTML_STYLESHEET = @srcdir@/static/doxygen.css
+TOC_EXPAND = YES
+DISABLE_INDEX = NO
+GENERATE_TREEVIEW = YES
+TREEVIEW_WIDTH = 300
+
+#---------------------------------------------------------------------------
+#LaTeX related option
+#---------------------------------------------------------------------------
+GENERATE_LATEX = NO
+
+#---------------------------------------------------------------------------
+#RTF related options
+#---------------------------------------------------------------------------
+GENERATE_RTF = NO
\ No newline at end of file
--- /dev/null
+/*!
+
+\page about_salome_page About SALOME
+
+<ul>
+<li>\subpage intro_to_salome_page</li>
+<li>\subpage salome_architecture_page</li>
+<li>\subpage installing_salome_page "Installing SALOME"</li>
+<li>\subpage running_salome_page</li>
+</ul>
+
+*/
\ No newline at end of file
--- /dev/null
+/*!
+
+\page creating_new_study_page Creating a new study
+
+Study is a document within GUI, an abstraction layer between actual
+document data (probably, remote data available through CORBA) and data
+presentation (in the Object Browser). It contains a tree of Data
+Object instances.
+
+<em>To create a new study:</em>
+
+\par
+From the main menu select <b>File > New</b> or in the standard toolbar
+click "New document" button.
+
+\image html newsticn.jpg ""New document" button"
+
+Your study will be created with default name \b Study1. In SALOME you
+can create several studies.
+
+In addition to it, you can create several windows with different
+activated viewers (VTK, OCC, Plot2d) for each study.
+
+<em>To create a new window for a definite study:</em>
+<ol>
+<li>Make your study \b active: maximize it (if it minimized) or click on
+the top control zone of the study window.
+</li>
+<li>\n From the main menu select <b>Window > New Window</b> and from the submenu
+choose the viewer, which will be activated in a new window.
+</li>
+</ol>
+
+The window for your study will be created with a default name \b Study1.
+
+*/
\ No newline at end of file
--- /dev/null
+/*!
+
+\page displaying_studies_page Displaying studies
+
+Starting from SALOME version 3.0.0. you are able to work in a
+multi-desktop environment, which means that you can open as many
+studies as you need, place them wherever you wish on the desktop, in
+brief, work with Salome Platform like with a normal Windows
+application.
+\n Such windows as Object Browser and Python Console are dockable and
+also can be placed at any part of the desktop.
+\n Only one study window in representation area can be active. You can
+change their size and move any windows between representation
+areas. When an area becomes empty, it is not displayed.
+\n All windows are placed inside tabs where you can switch between
+them. If there are several windows (viewers) in your current study and
+you want to display more then one at the same time, you can split
+representation area into two parts, in horizontal or vertical
+direction, to create two representation areas with windows be placed
+in them. To do this, right-click on the tab and select <b>Split
+Vertically</b> or <b>Split Horizontally</b>.
+
+For example, on this screen-shot the active zone has been split
+horizontally to be able to work with OCC and VTK viewers
+simultaneously, the one of the windows was split again, at this time
+vertically to see Plot 2d graphs.
+
+\image html neo-view2.png
+
+*/
\ No newline at end of file
--- /dev/null
+/*!
+
+\page editing_studies_page Editing studies
+
+\b SALOME has \b Copy/Paste functionality allowing to edit your study
+within a definite component:
+
+<em>To copy/paste a definite object:</em>
+\par
+In the main toolbar click "Copy"/"Paste" button or from the main menu
+choose <b>Edit > Copy/Paste</b> option.
+
+\image html copy-paste.jpg ""Copy" and "Paste" buttons"
+
+\n The availability of \b Copy/Paste operations depends on the module and
+the nature of an operation or an object, so if the module does not
+provide this functionality, it won't be available.
+
+*/
\ No newline at end of file
--- /dev/null
+/*!
+
+\page geometry_preferences_page Geometry preferences
+
+In the \b Geometry module you can set preferences for visualisation of
+geometrical figures which can be used in later sessions with this
+module.
+
+\image html pref15.png
+
+\par
+For all color definitions click on the respective line to access to
+the \ref select_color_and_font_page "Select Color" dialog box.
+
+<ul>
+<li><b>General</b></li>
+<ul>
+<li><b>Default Display Mode</b> - allows to choose between wireframe
+or shading.<li>
+<li><b>Default Shading Color</b> - allows to select default shading
+color.<li>
+<li><b> Default Wireframe Color</b> - allows to select default
+wireframe color (to be applied to any lines not being free boundaries
+or isolated lines).<li>
+<li><b>Color of free boundaries</b> - allows to select default color for free boundaries.<li>
+<li><b>Color of edges, vectors and wires</b> - allows to select
+default color for edges, vectors and wires (isolated lines).<li>
+<li><b>Color of points</b> - allows to select default color for
+vertices.<li>
+<li><b>Color of isolines</b> - allows to select default color for
+isolines.<li>
+<li><b>Step Value for Spin Boxes</b> - allows to define the increment
+of values set in spin boxes.<li>
+</ul>
+</ul>
+
+<ul>
+<li><b>Marker of Points</b></li>
+<ul>
+<li><b>Type</b> - allows to select the symbol for representation of
+points (cross, asterisk, etc.).</li>
+<li><b>Size</b> - allows to define the size of the marker from 1
+(smallest) to 7 (largest).</li>
+</ul>
+</ul>
+
+*/
\ No newline at end of file
--- /dev/null
+/*!
+
+\page getting_started_page Getting started
+
+When you start the SALOME Platform, the following initial desktop window appears:
+
+\image html view2.png
+
+ In general, the SALOME platform is destined
+for performance of different numerical calculations and visualization
+of the resulting data. For that purpose, in the SALOME environment the
+following notion is used - \b Study.
+<br>Study represents a working document in which you can realize all
+operations connected with the SALOME functionality.
+<br>SALOME is a multi-study platform. It means that simultaneously you can
+work with several studies.
+
+\note To proceed working in SALOME you should create or open a new study.
+
+*/
\ No newline at end of file
--- /dev/null
+/*!
+
+\page gui_module_page GUI module
+
+<ul>
+<li>\subpage introduction_to_gui_page</li>
+<li>\subpage getting_started_page</li>
+<li>\subpage salome_desktop_page</li>
+<li>\subpage study_management_page</li>
+<ul>
+<li>\ref creating_new_study_page</li>
+<li>\ref opening_studies_page</li>
+<li>\ref saving_and_closing_studies_page</li>
+<li>\ref editing_studies_page</li>
+<li>\ref displaying_studies_page</li>
+<li>\ref working_with_python_scripts_page</li>
+<li>\ref setting_study_properties_page</li>
+</ul>
+<li>\subpage using_object_browser_page</li>
+<li>\subpage using_find_tool_page</li>
+<li>\subpage using_registry_tool_page</li>
+<li>\subpage using_catalog_generator_page "Using Catalog Generator"</li>
+<li>\subpage viewers_page</li>
+<ul>
+<li>\ref occ_3d_viewer_page</li>
+<li>\ref vtk_3d_viewer_page</li>
+<li>\ref plot2d_viewer_page</li>
+</ul>
+<li>\subpage setting_preferences_page</li>
+<ul>
+<li>\ref setting_preferences_subpage</li>
+<li>\ref select_color_and_font_page</li>
+<li>\ref salome_preferences_page</li>
+<li>\ref geometry_preferences_page</li>
+<li>\ref mesh_preferences_page</li>
+<li>\ref postpro_preferences_page</li>
+</ul>
+</ul>
+
+*/
--- /dev/null
+/*!
+
+\mainpage GUI Module Reference Documentation
+
+<ul>
+<li>\subpage introduction_page</li>
+<li>\subpage about_salome_page</li>
+<ul>
+<li>\ref intro_to_salome_page</li>
+<li>\ref salome_architecture_page</li>
+<li>\ref installing_salome_page</li>
+<li>\ref running_salome_page</li>
+</ul>
+<li>\subpage gui_module_page "GUI module"</li>
+<ul>
+<li>\ref introduction_to_gui_page</li>
+<li>\ref getting_started_page</li>
+<li>\ref salome_desktop_page</li>
+<li>\ref study_management_page</li>
+<ul>
+<li>\ref creating_new_study_page</li>
+<li>\ref opening_studies_page</li>
+<li>\ref saving_and_closing_studies_page</li>
+<li>\ref editing_studies_page</li>
+<li>\ref displaying_studies_page</li>
+<li>\ref working_with_python_scripts_page</li>
+<li>\ref setting_study_properties_page</li>
+</ul>
+</ul>
+<li>\ref using_object_browser_page</li>
+<li>\ref using_find_tool_page</li>
+<li>\ref using_registry_tool_page</li>
+<li>\ref using_catalog_generator_page "Using Catalog Generator"</li>
+<li>\ref viewers_page</li>
+<ul>
+<li>\ref occ_3d_viewer_page</li>
+<li>\ref vtk_3d_viewer_page</li>
+<li>\ref plot2d_viewer_page</li>
+</ul>
+<li>\ref setting_preferences_page</li>
+<ul>
+<li>\ref setting_preferences_subpage</li>
+<li>\ref select_color_and_font_page</li>
+<li>\ref salome_preferences_page</li>
+<li>\ref geometry_preferences_page</li>
+<li>\ref mesh_preferences_page</li>
+<li>\ref postpro_preferences_page</li>
+</ul>
+</ul>
+
+
+*/
--- /dev/null
+/*!
+
+\page installing_salome_page SALOME Installation Wizard Help
+
+<hr>
+<ul>
+<li>\ref installing_products "Installing products with the Installation Wizard"
+<ul>
+<li>\ref gui_mode_install "GUI mode"
+<li>\ref batch_mode_install "Batch mode"
+<li>\ref environment_files "Environment files"
+</ul>
+<li>\ref notes_on_check "Notes on check products version procedure"
+<li>\ref pick_up_env "Pick up the environment"
+<li>\ref modifying_xml "Modifying XML configuration file"
+<li>\ref installation_scripts "Implementing installation scripts for the new products"
+<li>\ref finish_buttons "Customizing Readme page buttons"
+</ul>
+<hr>
+\anchor installing_products
+<h1>Installing products with the <em>Installation Wizard</em></h1>
+
+The Installation Wizard can be launched in two modes: \b GUI and \b
+batch.
+<br>The root directory of the Installation Wizard contains Python
+script \b runInstall. To run the Installation Wizard just type \b runInstall.
+in the terminal window:
+<br><br>[ python ] \b runInstall [options]
+
+Without options this script will launch the SALOME Installation
+Wizard in the default mode (GUI). \n The default installation settings
+can be overridden by using command line options. Each option has a
+short and a long notation:
+
+<b>-g / --gui</b>
+\par
+Runs the Installation Wizard in the GUI mode (this is the default
+mode).
+
+<b>-b / --batch</b>
+\par
+Runs the Installation Wizard in the terminal mode.
+
+<b>-f FILE / --file=FILE</b>
+\par
+The XML configuration file to be used by the Installation Wizard. If
+this option is not used then the installation script tries to define
+the \e Linux version and use the corresponding XML file if it exists. For
+examle, for <em>Linux Mandrake 10.1</em> the <b>config_Mandrake_10.1.xml</b> file
+will be used by default. If no appropriate file is found, the file
+<b>config.xml</b> will be used. This file refers to the basic target platform
+which is <em>Linux Mandrake 10.1</em> for SALOME 3.0 and newer. If <b>config.xml</b>
+file is not found either, a warning message box is shown (in GUI mode)
+or printed to the console (in batch mode) and the Installation Wizard
+quits.
+
+<b>-d DIR / --target=DIR</b>
+\par
+The target directory SALOME platform is to be installed to.
+If used, this option overrides the default target directory, given in
+the configuration XML file (usually <b>${HOME}/salome_\<version\></b>,
+see \ref modifying_xml "here" for more details).
+
+<b>-t DIR / --tmp=DIR</b>
+\par
+The directory, which should be used for temporary files. If given,
+this option overrides the default temporary directory, given in the
+configuration xml file (usually \b /tmp, see \ref modifying_xml "here"
+for more information).
+
+<b>-a / --all-from-sources</b>
+\par
+Forces all the products to be installed from sources (including all
+SALOME modules). If this option is used, all default installation
+modes for all products are ignored.
+\n This option is helpful when the user wants to install SALOME on the
+platform which is not officially supported. In this case, the user can
+try to run the SALOME Installation Wizard with the \b -a option in order
+to build all the products from sources.
+\n <b>Note, that this is a time-consuming operation which can take
+more than 24 hours depending on the computer.</b>
+
+<b>-h / --help</b>
+\par
+Prints help information on the Installation Wizard's use.
+
+<b>-v / --version</b>
+\par
+Prints version information (\b Note: this is the Installation Wizard's
+version number, not the number of SALOME platform version).
+
+The installation procedure supports different \em Linux platforms and
+installs various installation 3d-party prerequisite products which are
+required by SALOME platform. As it was mentioned above, the basic
+target platform for SALOME 3.0 and newer is <em>Linux Mandrake 10.1</em>.
+Use of configuration XML files gives a flexible way to modify the list
+of products to be installed by the Installation Wizard without
+changing the program source code. Just create your own XML
+configuration file and implement installation scripts for the
+prerequisite products you need and then use this XML file with the
+Installation Wizard. This can be done, for example, for some Linux
+platform which is not supported directly by the Installation
+Wizard. See \ref modifying_xml "Modifying XML configuration file" and
+\ref installation_scripts "Implementing installation scripts for the new products"
+sections for more information.
+
+<br>
+\anchor gui_mode_install
+<h2>GUI mode</h2>
+
+The <b>Installation Wizard</b> GUI has been developed using
+Trolltech's <b>Qt 3.0.5</b> toolkit. After launching the Installation
+Wizard in the GUI mode the wizard window is shown to the user. This
+wizard guides the user through several subsequent pages. To navigate
+between the pages use \em "Next" and \em "Back" buttons in the lower
+part of the wizard window. The \em "Cancel" button closes the wizard
+window and quits the installation procedure after the user's
+confirmation. The \em "Help" button opens an additional window to show
+help information.
+
+The first \em "Introduction" page is shown in \ref figure_1 "Figure 1".
+Skip this page by clicking \em "Next":
+
+\anchor figure_1
+\image html intropage.png
+\n <center><b>Figure 1:</b> "Introduction" page</center>
+
+In the second page you are proposed to enter the target directory
+where the SALOME platform should be installed to. You can also click
+<em>"Browse..."</em> and choose the destination folder using the standard
+browse directory dialog box.
+\n If the directory you want to install products to does not exist you
+are prompted to confirm directory creation. If you type a wrong
+directory path, or if you do not have write permissions
+for the directory you use, the corresponding message box is shown.
+
+You can also change the temporary directory (which is used to store
+temporary files required for the installation).
+\n In the bottom part of the window the total disk space required for
+the installation and for the temporary files is displayed (see below
+for more details).
+
+In the GUI mode the Installation Wizard provides two different options
+to install the SALOME platform: \b basic (default option) and
+\b advanced. In the \b basic mode the user should enter the target
+installation directory and temporary folder. All other installation
+options are taken from the XML configuration file (see \ref figure_2 "Figure 2"):
+
+\anchor figure_2
+\image html productpage1.png
+\n <center><b>Figure 2:</b> "Installation settings"</center>
+
+In addition, you have a choice to use "Install all products from
+sources" check box. If this option is turned on, all the products will
+be installed from the sources (using their own build procedures). This
+check box corresponds to the <b>--all-from-sources (-a)</b> option of
+the \b runInstall script (see \ref installing_products "here").
+
+\Note <b>Installation of all products from sources is a long-time
+operation.</b>
+
+To switch to the \b advanced option, click <em>"More..."</em> (see
+\ref figure_3 "Figure 3" ).
+
+In the advanced mode you have a possibility to select products to be
+installed. Each product can have several options of installation: you
+have a possibility to use the native product (provided with Linux
+distribution and installed in the system folders), install already
+precompiled binaries, build the product from sources or not install it
+at all. Available options and default option are taken from the XML
+configuration file. You can mark the products you want to install by
+clicking the corresponding radio-buttons in the list view in the left
+part of the page.
+\n Note, that some products may require some other pre-requisite
+products to be installed (or these prerequisite products should be
+already available on your computer). The installation procedure has a
+special feature to automatically mark these products in the list
+view. For example, in order to install \b PyQt it is necessary to have
+<b>gcc, Python, Qt</b> and \b Sip installed. Therefore all these
+products will also be turned on when you check on \b PyQt. This
+feature can be switched off by clicking the <em>"Automatic
+dependencies"</em> checkbox. Turn on this checkbox if you want all
+prerequisite products to be automatically checked when you select some
+product to be installed. Turn off this checkbox if you want to disable
+this feature.
+
+\anchor figure_3
+\image html productpage.png
+\n <center><b>Figure 3:</b> "Installation settings" page in the 'advanced' mode</center>
+
+If you want to use native products (like \b gcc, \b tcl, etc.), select <em>"use
+native"</em> option.
+\n Special button in the right part of the page - <em>"Unselect All"</em> -
+allows to reset quickly all products to the <em>"not install"</em> state.
+<br><br>
+There are also two checkboxes on this page: <em>"SALOME sources"</em>
+and <em>"SALOME binaries"</em>. These three-state checkboxes allow
+quick selecting/unselecting sources/binaries packages of SALOME
+modules for installation.
+<br><br>
+In addition, when some SALOME sources are selected, one more check box
+becomes available: <em>"Build SALOME sources"</em>. If this option is
+turned on, the selected SALOME modules will be built and installed
+from sources.
+
+\note <b>If this check box is turned on, the corresponding SALOME
+module binaries package installation is disabled, because of SALOME
+module sources and binaries packages conflict</b> (see \ref figure_4 "Figure 4" below).
+
+\anchor figure_4
+\image html productpage2.png
+\n <center><b>Figure 4:</b> "Build SALOME sources" check box
+usage</center>
+
+The box at the right side of the page displays the information about
+currently highlighted product: name, version and short description,
+required disk space, disk space required for temporary files, list of
+prerequisites (this information is provided in the XML file) and
+current user choice.
+<br><br>
+The <em>"Disk space required:"</em> field displays how much disk space
+on the hard drive is required for installation of selected products.
+
+\note <b>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.</b>
+
+The installation procedure uses a special directory to store temporary
+files. The <em>"Space for temporary files:"</em> field shows the information
+about required disk space on the hard drive for extracting and
+compiling the selected products. You can change the temporary
+directory - just type a path to the folder you want to use or click on
+the corresponding <em>"Browse..."</em> button.
+
+\note Actually, temporary files are not stored directly in the
+directory entered by the user. The Installation Wizard creates an
+additional folder in this directory named something like
+INSTALLWORK<b>XXXXX</b> where XXXXX is a unique number. This allows to launch
+several Installation Wizards simultaneously. This temporary directory
+is removed automatically when the installation finishes.
+
+The installation procedure also checks the available disk space. If
+there is not enough disk space on your hard drive you will see a
+corresponding error message box.
+
+\note <b>You are strongly recommended not to use directory names
+containing spaces</b>. Otherwise you can experience
+some troubles with the installation.
+
+To proceed further click <em>"Next"</em>. At this moment the program will make
+some tests to check installation settings: if there is enough disk
+space on the hard drive, check for native products installation,
+dependencies (prerequisites) for each product you have selected to be
+installed. If any test fails you will see the corresponding warning
+message box. Otherwise the wizard will proceed to the next page:
+
+\anchor figure_5
+\image html choicepage.png
+\n <center><b>Figure 5:</b> "Check your choice" page</center>
+
+This page summarizes the installation options you've made on the
+previous pages. You can check again your choice and change it if
+necessary by getting back to the previous page.
+\n When you are sure that everything is OK, click <em>"Next"</em> to
+follow to the \ref figure_6 "next page".
+
+\anchor figure_6
+\image html progresspage1.png
+\n <center><b>Figure 6:</b> "Installation progress" page</center>
+
+To start installation of the selected products click "Start". It
+launches the shell installation script and you will be able to see the
+output of the script in the dialog topmost frame. If any errors occur
+during the installation progress the corresponding messages will be
+printed to the log window in bold red font.
+
+It is possible to break the installation at any time by clicking
+"Stop". Then you can get back to the previous pages if you wish to
+change installation settings or restart installation by pressing again
+"Start" button.
+
+\note <b>In the current implementation it is not possible to resume
+the stopped installation process; it will be re-started from the very
+beginning.</b>
+
+\anchor figure_7
+\image html progresspage.png
+\n <center><b>Figure 7:</b> "Installation progress" page: installation in progress</center>
+
+The <em>"Installation Status"</em> frame window shows you the progress of
+installation. \c "Waiting" status means that installation of this product
+has not been started yet. The product currently being installed is
+marked as \c "Processing". All installed products have \c "Completed"
+status.
+
+You can abort installation and close the installation procedure using
+\em "Cancel" button.
+
+\note <b>This button sends the signal "SIGTERM" to the shell
+script. The script tries to clear all temporary files. The process of
+removing temporary files can take some time, so the installation
+wizard will wait 3 seconds before closing.</b>
+
+At the end of installation (all selected products have been installed
+successfully) you can go back to the previous pages to start a new
+installation or click \em "Next" to go the Readme page:
+
+\anchor figure_8
+\image html readmepage.png
+\n <center><b>Figure 8:</b> "Finish installation" page</center>
+
+In this page you can read important information about the Instalation
+Wizard itself and some tips: how to run and test SALOME or how to
+build SALOME from the sources. This is the contents of the README file
+which you can find in the root directory of the Installation Wizard.
+
+You can also launch SALOME Desktop from this page or read the Release
+Notes file by clicking on the corresponding buttons in the lower part
+of the page (see \ref modifying_xml "here" and \ref finish_buttons
+"here" for more information about customizing these buttons).
+
+<br>
+\anchor batch_mode_install
+<h2>Batch mode</h2>
+
+To launch the Installation Wizard in the batch mode use -\b b (--\b batch)
+parameter.
+\n In this mode the GUI wizard is not shown but all the installation
+status is displayed directly in the console. In the batch mode the
+user does not have a possibility to change installation settings which
+are given in the configuration file, except target and temporary
+directories which can be overridden by the corresponding command line
+options.
+\n The only exception is --\b all-from-sources (-\b a) option which enables
+special installation mode in which all the products (including SALOME
+modules) are installed from sources, ignoring the default mode defined
+in the XML configuration file (see \ref installing_products "here" for details).
+
+\anchor figure_9
+\image html batchmode.png
+\n <center><b>Figure 9:</b> Batch mode</center>
+
+<br>
+\anchor environment_files
+<h2>Environment files</h2>
+
+During the process of installation the script creates some environment
+files to simplify the procedure of launching SALOME. These shell
+scripts set all necessary environment variables for all products you
+have installed. To learn how installation scripts collects the
+environment, see \ref pick_up_env "here". These files are: \b
+salome.csh + \b salome.sh in the <b><em>KERNEL module sources</em></b>
+and <b><em>KERNEL module binaries</em></b> root directories and
+\b env_products.csh + \b env_products.sh and \b env_build.csh +
+\b env_build.sh in the target installation directory.
+
+\note there is some difference between these files: \b env_build.*
+files are optimized to be used for building SALOME modules from
+sources (see \b README file provided with the installation procedure
+on the CD). The \b env_products.* (and \b salome.*) files are
+optimized for SALOME launching. The behavior is defined by the
+environment variable \b ENV_FOR_LAUNCH which is set to \b 0 in
+env_build.* files and to \b 1 in env_products.* (salome.*) files.
+
+<br>
+<hr>
+\anchor notes_on_check
+<h2>Notes on <em>check products version</em> procedure</h2>
+
+Unfortunately there is no exact algorithm to identify the product
+version under Linux platform. The information in this section gives an
+idea how the version is checked for the native/preinstalled products
+(this information refers to the base platform <em>Linux Mandrake
+10.1</em>; and the same algorithms are used for other platforms).
+
+The general rule for all products is that the path to the binaries
+should be set via the \b PATH environment variable, path to the libraries
+should be set via the \b LD_LIBRARY_PATH variable and the python modules
+should be available via the \b PYTHONPATH variable.
+
+\note the information given in this section refers to the prerequisite
+products for SALOME version 3.2.4.
+
+<ul>
+<li>gcc 3.4.1
+\n\n Version number is checked by <b>gcc -dumpversion</b> command. The \b gcc
+executable should be in the \b PATH environment variable. Version should
+be equal to "3.4.1". It is recommended to use native gcc on Mandrake
+10.1.<br><br>
+</li>
+<li>tcl/tk 8.4.5
+\n\n Version number for \b tcl/tk can be found in tclConfig.sh and
+tkConfig.sh files (\b TCL_VERSION and \b TK_VERSION variables
+correspondingly). Version number should be equal to "8.4" (release
+number is not checked). Set the \b TCLHOME environment variable to the
+root directory of tcl/tk installation. It is recommended to use native
+tcl/tk on Mandrake 10.1.<br><br>
+</li>
+<li>boost 1.31.0
+\n\n Version number is defined by \b version.hpp file which is part of
+the boost distribution. This file defines the \b BOOST_VERSION macro
+which should be equal to "103100". In addition the existence of boost
+libraries is checked. Set the \b BOOSTDIR environment variable if you
+have a preinstalled version of boost.<br><br>
+</li>
+<li>Python 2.3.4
+\n\n Version number is checked by \b python -\b V command. The \b python
+executable should be in the \b PATH environment variable. Version
+number should be equal to "2.3.4". It is recommended to use native
+Python on Mandrake 10.1. Set the \b PYTHONHOME environment variable if
+you have a preinstalled version of Python.<br><br>
+</li>
+<li>Swig 1.3.24
+\n\n Version number is checked by \b swig -\b version command. The \b swig
+executable should be in the \b PATH environment variable. Version number
+should be equal to "1.3.24".
+<br><br>
+</li>
+<li>Qt 3.3.3
+\n\n Version number is defined by \b qglobal.h file which is part of the
+Qt distribution. This file defines \b QT_VERSION_STR macro which should be equal to "3.3.3". It is recommended to use native Qt on Mandrake 10.1.
+\n Set the \b QTDIR environment variable if you have a preinstalled version of qt.<br><br>
+</li>
+<li>msg2qm
+\n\n \b msg2qm is a Qt tool which is used to convert text *.po files
+to *.qm resource files. Unfortunately this tool is not included to the
+Linux distribution and provided only in Qt sources package. This is
+the reason why this tool is supplied with the SALOME Installation
+Wizard. There is no way to check the version number of msg2qm tool. Just set
+\b MSG2QM_ROOT environment variable if you have a preinstalled version
+of msg2qm tool.<br><br>
+</li>
+<li>Open CASCADE 6.1.2a2
+\n\n Version number is defined by \b Standard_Version.hxx file which
+is part of the Open CASCADE distribution. This file defines \b
+OCC_VERSION_MAJOR, \b OCC_VERSION_MINOR and \b OCC_VERSION_MAINTENANCE
+macros which should refer to version 6.1.2. \n Set the CASROOT
+environment variable if you have a preinstalled version of Open
+CASCADE.<br><br>
+</li>
+<li>qwt 4.2.0/0.4.2
+\n\n Version number is defined by \b qwt_global.h file which is part of
+the qwt distribution. This file defines \b QWT_VERSION_STR macro which should be equal to "4.2.0".
+\n Set the \b QWTHOME environment variable if you have a preinstalled version of qwt.<br><br>
+</li>
+<li>hdf 5-1.6.4
+\n\n Version number is defined by \b libhdf5.settings file which is
+part of the \b hdf5 distribution. Version should be equal to 1.6.4.
+\n Set the \b HDF5HOME environment variable if you have a preinstalled
+version of hdf5.<br><br>
+</li>
+<li>med 2.2.3
+\n\n Unfortunately there is no formal way to check med version
+number. We check existence of libmed.so.1.0.2 library on the
+computer. If you have any problem with a preinstalled version of med,
+please, reinstall it.
+\n Set the \b MED2HOME environment variable if you have a preinstalled
+version of med.<br><br>
+</li>
+<li>Vtk 4.2.6
+\n\n Unfortunately there is no formal way to check VTK version
+number. We just check the existence of \b libvtkCommon.so library on
+the computer and hope that it is of version we need. If you have any
+problem with a preinstalled version of Vtk, please, reinstall it.
+\n Set the \b VTKHOME environment variable if you have a preinstalled
+version of Vtk.<br><br>
+</li>
+<li>OmniORB 4.0.5, OmniORBpy 2.5, OmniNotify 2.1
+\n\n We just check existence of some omniORB libraries and executable
+on the computer, like \b libomniORB4.so.0.5, \b _omnipymodule.so.2.4,
+\b libCOSNotify4.so.0.1 and \b notifd. \n Set the \b OMNIORBDIR
+environment variable if you have a preinstalled version of omniORB
+products.<br><br>
+</li>
+<li>sip 4.1
+\n\n Version number is checked by \b sip -\b V command. The \b sip
+executable should be in the \b PATH environment variable. Version number should be equal to "4.1".
+\n Set the \b SIPDIR environment variable to the directory where you
+have sip executable preinstalled.<br><br>
+</li>
+<li>PyQt 3.13
+\n\n Version number is defined by \b pyqtconfig.py Python module file
+which is part of the \b PyQt distribution. Version should be equal to "3.13".
+\n Set the \b PYQTDIR environment variable if you have a preinstalled
+version of PyQt.<br><br>
+</li>
+<li>netgen 4.5
+\n\n Unfortunarely we can't find anything about netgen version. We
+just check if \b NETGENROOT environment variable is set. \n Set the\b
+NETGENROOT environment variable if you have a preinstalled version of
+netgen mesher.<br>
+\note netgen 4.5 provided with the SALOME installation Wizard has been patched to improve its performance.
+</li>
+<li>Numeric 23.7
+\n\n Version number is checked by <b>python -c 'import Numeric; print
+Numeric.__version__'</b> command. The \b python executable should be
+in the \b PATH environment variable and \b Numeric module should be
+available for the Python (for example it should be in the \b PYTHONPATH environment variable). Version number should be equal to "23.7". If you have any problem with a preinstalled version of Numeric 23.7, please, reinstall it.
+\n Add the directory where you have a preinstalled version of Numeric
+package to the the \b PYTHONHOME environment variable.<br><br>
+</li>
+<li>graphviz 2.2.1
+\n\n Version number is checked by \b dot -\b V command. The dot
+executable should be in the \b PATH environment variable. Version
+number should be equal to "2.2.1". \n Add \b graphviz bin directory to
+the the \b PATH environment variable.<br><br>
+</li>
+<li>doxygen 1.4.6
+\n\n Version number is checked by \b doxygen --\b version command. The
+\b doxygen executable should be in the \b PATH environment
+variable. Version number should be equal to "1.4.6".<br><br>
+</li>
+<li>\b SALOME module \b sources (3.2.4).
+\n\n For each SALOME module sources package (KERNEL, GUI, GEOM,
+etc...) the root directory contains file configure.in (configure.ac)
+which defines version information.\n Set the \b \<MODULE\>_SRC_DIR environment variable for each SALOME \b
+MODULE sources package installed (where \b MODULE is KERNEL, GUI,
+GEOM, ...).<br><br>
+</li>
+<li>\b SALOME module \b binaries (3.2.4)
+\n\n For each SALOME module binaries package (KERNEL, GUI, GEOM,
+etc...) the \b bin/salome directory contains file \b VERSION which
+defines version information.\n Set \<MODULE\>_ROOT_DIR environment
+variable for each SALOME \b MODULE binaries package installed (where
+\b MODULE is KERNEL, GUI, GEOM, ...).<br><br>
+</li>
+</ul>
+
+If you have native products installed to directories different from
+default ones (not \b /usr/bin, \b /usr/lib...), it is recommended to follow
+the above mentioned instructions. Or you should properly set \b PATH and
+\b LD_LIBRARY_PATH variables \em before starting the Installation
+Wizard. Otherwise the installation script will fail to find
+preinstalled/native products.
+
+\note for some native products (e.g. gcc, Python) the rules of version
+checking are not so strict as described above. Only major and minor
+version numbers should coincide with the prerequisite. Newer version
+of the product can also be used. If some native product has version
+number larger than that required by the installation procedure, the
+user will be prompted by the warning message like this: "<em>You have
+newer version of gcc installed on your computer than that is required
+(3.4.1). Continue?</em>". You can click "\em Yes" to proceed with the
+installation but in this case you should be aware of what you are
+doing. SALOME binaries (including other products) are compiled with
+the predefined prerequisites and most likely can not be run
+successfully if these products are not found. This can be helpful only
+if you plan to build all products from sources.
+
+<br>
+<hr>
+\anchor pick_up_env
+<h2>Pick up the <em>environment</em></h2>
+
+Please, read the following information carefully . This section
+describes how the installation procedure generates the environment
+scripts for the SALOME platform being installed.
+<br><br>
+After installing each product shell the script creates a special
+environment file for the product in its installation folder. The name
+of the file is generated from the name of product by the following
+scheme: \b env_<product_name>.sh (for example \b env_Vtk.sh for the
+Vtk). This file includes all necessary environment settings. At the
+final step of the installation the script picks up all the settings
+files and generates two common environment files from them: \b salome.sh
+and \b salome.csh for \b bash and \b csh shells correspondingly. Such approach
+helps to save time when reinstalling products and you may not bother
+about setting all environment variables manually to build/launch
+SALOME. What you simply need is to source one of these environment
+files.
+<br><br>
+This also concerns those products which are not being installed. For
+example, you install some SALOME binaries to the directory where you
+have previously installed other products. The Installation procedure
+tries to collect environment files from the target directory if it
+finds necessary products installed there. If some product is not found
+in the target directory the corresponding section of
+\b salome.sh/salome.csh files will be skipped.
+\n For native products (like \b gcc, \b tcl, etc...) the installation
+procedure tries to find them first using \b PATH / \b LD_LIBRARY_PATH
+variables and then in the system default directories (\b /usr/bin,
+\b /usr/lib etc., depending on the product).
+<br><br>
+In any case you may edit \b salome.* files after the installation
+procedure finishes, if you want.
+
+\note As it was mentioned \ref environment_files "above" there are
+other environment files which are generated by the installation
+procedure: \b env_products.csh + \b env_products.sh and \b env_build.csh +
+\b env_build.sh. These files can be found in the target installation root
+directory.
+
+<br>
+<hr>
+\anchor modifying_xml
+<h2>Modifying <em>XML</em> configuration <em>file</em></h2>
+
+You can create your own XML configuration file. The Installation
+Wizard can then take it as a command line argument to provide a list
+of products you want to install with it. The list of products and some
+other settings for the Installation Wizard are provided in the XML
+file. The default file which Installation Wizard looks for if no
+command line arguments are given, is \b config.xml.
+\n This section describes the structure of the configuration file.
+\n Optional sections/tags are in brackets.
+
+\code
+<document>
+ [ <config [ version=<install_wizard_version> ]
+ [ caption=<install_wizard_caption> ]
+ [ copyright=<install_wizard_copyright> ]
+ [ license=<install_wizard_license_info> ]
+ [ os=<target_platform> ]
+ />
+ ]
+ [ <path [ targetdir=<target_directory> ]
+ [ tempdir=<temp_directory> ]
+ />
+ ]
+ [ <button label=<button_label>
+ [ tooltip=<button_tooltip> ]
+ script=<button_script>
+ [ disable=<disable_flag> ]
+ />
+ ]
+ [ <button ...
+ />
+ ]
+ [ <product name=<product_name>
+ version=<product_version>
+ [ context=<product_context> ]
+ [ description=<product_description> ]
+ install=<installation_mode>
+ supported=<supported_installation_modes>
+ [ disable=<disable_flag> ]
+ [ pickupenv=<pickup_env_flag> ]
+ dependancies=<list_of_prerequisites>
+ installdiskspace=<install_disk_space>
+ temporarydiskspace=<tmp_disk_space>
+ script=<installation_script_name>
+ />
+ ]
+ [ <product ...
+ />
+ ]
+ ...
+</document>
+\endcode
+
+<b>\<config\> section</b>
+\n\n This is an optional section; it provides general information about
+the Installation Wizard itself.
+<br><br>
+Attributes:
+<ul>
+<li><b>version</b>
+\n\n The application version number to be shown in the caption.<br><br>
+</li>
+<li><b>caption</b>
+\n\n The application main window caption - if this string contains
+'\%1' text the title will contain the version number in this place (see
+above).<br><br>
+</li>
+<li><b>copyright</b>
+\n\n The application copyright information (shown in the first
+page).<br><br>
+</li>
+<li><b>license</b>
+\n\n The application license information (shown in the first
+page).<br><br>
+</li>
+<li><b>os</b>
+\n\n This parameter defines the directory (relative from
+./Products/BINARIES) where the Installation Wizard will search
+precompiled binaries packages. If this tag is not provided, binaries
+packages are looked for in the ./Products/BINARIES directory.<br><br>
+</li>
+</ul>
+
+<b>\<path\> section</b>
+\n\n This is an optional section; it defines default installation
+directories.
+<br><br>
+Attributes:
+<ul>
+<li><b>targetdir</b>
+\n\n The target directory - the path to the directory where products
+should be installed.<br><br>
+</li>
+<li><b>tempdir</b>
+\n\n The temporary directory - the path to the directory for the
+temporary files.<br><br>
+</li>
+</ul>
+
+<b>\<product\> section</b>
+\n\n This section describes product to be installed with the
+Installation Wizard. The XML file should include a \<product\> section
+for each product to be installed. The products appear in the tree view
+and are installed in the order they are described in the configuration
+file. It is recommended (but not obligatory) to define native products
+at the top of the list before all other products.
+<br><br>
+Attributes:
+<ul>
+<li><b>name</b>
+\n\n Product name.<br><br>
+</li>
+<li><b>version</b>
+\n\n Product version.<br><br>
+</li>
+<li><b>description</b>
+\n\n Product description (optional).<br><br>
+</li>
+<li><b>context</b>
+\n\n Context (optional). The possible values are '<b>salome
+sources</b>', '<b>salome binaries</b>' and '<b>prerequisite</b>'
+(several contexts can be given separated by ":" symbol).<br><br>
+</li>
+<li><b>supported</b>
+\n\n Supported modes of installation. Several modes can be separated
+by comma. Possible value are: <em>install sources, install binaries, use
+native</em>. The Installation script should contain the corresponding
+functions for each of the supported installation modes (see
+\ref installation_scripts "here").<br><br>
+</li>
+<li><b>install</b>
+\n\n Default (starting) installation mode.<br><br>
+</li>
+<li><b>disable</b>
+\n\n If this optional flag has 'true' value, the corresponding product
+will not appear in the list of products and will not be
+installed.<br><br>
+</li>
+<li><b>pickupenv</b>
+\n\n This flag points that pickup environment procedure should be
+performed for this product. If this flag equal to 'true', salome.sh
+and salome.csh files will be created in the product installation
+directory. Usually this option is set to true for SALOME KERNEL module
+sources and binaries package. This is an optional key, default value
+is 'false'.<br><br>
+</li>
+<li><b>dependancies</b>
+\n\n List of prerequisite products, which are necessary to build this
+product, separated by comma.<br><br>
+</li>
+<li><b>installdiskspace</b>
+\n\n Total amount of space (integer, in Kbytes), which the product
+occupies on the hard drive after the installation.<br><br>
+</li>
+<li><b>temporarydiskspace</b>
+\n\n Disk space (integer, in Kbytes) for temporary files, which is
+necessary to build the product from the sources.<br><br>
+</li>
+<li><b>script</b>
+\n\n The installation script name. This script is in charge of the
+installation of the product. It is called automatically by the
+Installation Wizard when necessary from the main program.
+See the \ref installation_scripts "next section" for more information.<br><br>
+</li>
+</ul>
+
+<b>\<button\> section</b>
+\n\n This is an optional section. It allows customization of the last
+"Finish installation" page of the Installation Wizard by adding one or
+more buttons in the lower part of the wizard's window. The script
+which is attached to each such button, can perform some specific
+action, for example, launch the application or show the Release Notes
+file by using an external program. See \ref finish_buttons "here" for
+more details about writing scripts.<br><br>
+Attributes:
+<ul>
+<li><b>label</b>
+\n\n This is the button text.<br><br>
+</li>
+<li><b>tooltip</b>
+\n\n The button tooltip (optional).<br><br>
+</li>
+<li><b>script</b>
+\n\n The script attached to the button.<br><br>
+</li>
+<li><b>disable</b>
+\n\n If this optional flag has 'true' value, the corresponding button
+will not appear in the "<em>Finish installation</em>" page - the section of XML
+file is silently ignored.<br><br>
+</li>
+</ul>
+
+\note If you add new products to be installed with Installation
+Wizard, you should also provide installation script for this
+product. See the next section for more details.
+
+<br>
+<hr>
+\anchor installation_scripts
+<h2>Implementing <em>installation scripts</em> for the new products</h2>
+
+When you want some product to be installed with the Installation
+Wizard, you should add its description \ref modifying_xml "to the configuration file"
+and create the installation script, following the rules described in this section.
+
+There are some obligatory functions which should be implemented in
+this installation script. These functions are automatically called by
+the master installation script or/and its GUI shell when it is
+necessary. \n File \b common.sh contains some service functions which can
+be used in your installation script, like \b make_env(), \b make_dir(),
+\b try_existing(), \b sort_path(), \b find_in_path(), etc.
+
+<ul>
+<li><b>check_version()</b>
+\n\n 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 its version. This
+helps to avoid unnecessary reinstallation. This is an internal
+function and is not called from the master installation
+script.<br><br>
+</li>
+<li><b>try_native()</b>
+\n\n This function is called when the 'use native' installation mode
+is selected by the user. The function should try to find a native
+version of the product and define possibility of its use. It should
+create the environment file for the product in the temporary directory
+(see also the description of \b print_env() function). It is not
+necessary to implement this function if you do not provide native mode
+installation.<br><br>
+</li>
+<li><b>install_source()</b>
+\n\n This function is called when the 'install sources' installation
+mode is selected by the user. The function is responsible for building
+the product from the sources package. It should create the environment
+file for the product in the temporary directory (see also description
+of \b print_env() function). It is not necessary to implement this
+function if you do not provide sources mode installation.<br><br>
+</li>
+<li><b>install_source_and_build()</b>
+\n\n This function is called when SALOME module is installed and the
+--\b all-from-sources (-\b a) option is used (<em>"Build SALOME sources"</em>
+check box in GUI mode). This function should be used to unpack SALOME
+sources package and then call the build/install procedure for it.
+For more details please refer to the \ref installing_products "this"
+and \ref gui_mode_install "this" sections for more details.<br><br>
+</li>
+<li><b>install_binary()</b>
+\n\n This function is called when the <em>'install binaries'</em> installation
+mode is selected by the user. The function is responsible for the
+extracting of the product from the binaries package. It should create
+environment for the product in the temporary directory (see also
+description of \b print_env() function). It is not necessary to implement
+this function if you do not provide binaries mode
+installation.<br><br>
+</li>
+<li><b>try_preinstalled()</b>
+\n\n 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 an already preinstalled product, pick
+up and check the environment from there. See \ref pick_up_env "here" for more
+details.<br><br>
+</li>
+<li><b>print_env()</b>
+\n\n This function is in charge of creating the environment script. It
+should create a file with name \b 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.<br><br>
+</li>
+<li><b>pickup_env()</b>
+\n\n This procedure corresponds to the \b pickupenv tag of the
+configuration xml file (see previous section). It should call the
+\b make_env procedure to perform the pick-up environment procedure for
+the product.<br><br>
+</li>
+</ul>
+
+The calling signature of the product installation script is the following:
+<b>\<product_script_name\> \<function_name\> \<temp_folder\>
+\<products_directory\> \<target_directory\> \<dependancies\>
+\<product_name\></b>
+\n\n where \n\n
+<b>\<product_script_name\></b> - installation script name (described in the
+configuration xml file);\n
+<b>\<function_name\></b> - the name of function, corresponding to the selected
+installation mode: \em try_native, \em install_source, \em install_binary or
+\em try_preinstalled;\n
+<b>\<temp_folder\></b> - temporary files directory;\n
+<b>\<products_directory\></b> - directory where the sources/binaries package
+can be found. You should provide the sources package in the
+<em>\<Install_Wizard_root_directory\>/Products/SOURCES</em> directory and
+binaries package in the
+<em>\<InstallWizard_root_directory\>/Products/BINARIES/\<os_version\></em>, where
+\<os_version\> is the target platform description, which appears in the
+corresponding section of the \ref modifying_xml "configuration xml file";
+<em>\<target_directory\></em> - root target directory where the product should be installed to;
+<em>\<dependancies\></em> - single-quoted list of prerequisite products, separated by space;
+<em>\<product_name\></em> - product name itself.
+
+\b Example:
+\n <em>med-2.2.3.sh install_binary /tmp/work
+./Products/BINARIES/Mandrake10.1 /usr/salome 'gcc Hdf' med</em>
+
+Copy the created script into the
+<em>\<Install_Wizard_root_directory\>/config_files</em> sub-directory where all
+installation scripts are stored. Installation Wizard will
+automatically search and call your script during the installation
+procedure.
+
+<br>
+<hr>
+\anchor finish_buttons
+<h2>Customizing <em>Readme page</em> buttons</h2>
+
+The Installation Wizard allows customizing the look-n-feel of the last
+<em>"Finish installation"</em> page. If you want to add one or more buttons to
+this page in order to perform some specific actions at the end of the
+installation (for example, to show the Release Notes file by using
+Open Office) you can put an additional section to the XML
+configuration file. This is the \b \<button\> section (see
+\ref modifying_xml "here" for more details).
+
+To implement the action which will be performed when the user clicks
+the button, you need to create a script and put it to the
+<em>\<Install_Wizard_root_directory\>/config_files</em> directory.
+\n There are some obligatory functions which should be implemented in
+this script. These functions are automatically called by the
+Installation Wizard GUI.
+
+<ul>
+<li><b>check_enabled()</b>
+\n\n This procedure is called by the Installation Wizard when the
+<em>"Finish installation"</em> page is displayed and the status of the buttons
+should be modified according to the installation options. This
+procedure should return \b 0 if the corresponding action can be performed
+and, thus, the button should become enabled. Otherwise, it should
+return \b 1 - in this case the corresponding button will be
+disabled.<br><br>
+</li>
+<li><b>execute()</b>
+\n\n This procedure is invoked when the user clicks the button. This
+procedure should return \b 0 if the corresponding action is done
+successfully and \b 1 if any error occurs.<br><br>
+</li>
+</ul>
+
+The calling signature of the script is the following:
+\n <b>\<product_script_name\> \<function_name\> \<target_directory\>
+\<temp_folder\></b>
+\n\n where \n\n
+\b \<product_script_name\> - the script name itself (retrieved from the XML configuration xml file);
+\n \b \<function_name\> - the name of function;
+\n \b \<target_directory\> - root target directory where the product is installed to;
+\n \b \<temp_folder\> - temporary files directory;
+
+\note The standard Installation Wizard buttons "Launch SALOME" and
+"Release Notes" are implemented with this feature. Refer to scripts
+\b start_salome.sh and \b release_notes.sh for sample implementation.
+
+\note Any button (even standard) can be ignored by the Installation
+Wizard if the attribute \b \<disable\> in the XML configuration file is set
+to the "true" value.
+
+*/
\ No newline at end of file
--- /dev/null
+/*!
+
+\page intro_to_salome_page Introduction to SALOME
+
+
+\b SALOME platform represents a generic open source platform for pre-
+and post-processing in numeric simulations. \b SALOME combines several
+software components, which are built in such a way that it allows to
+integrate solvers and existing meshing algorithms along with the
+specification of physical properties for a given domain. The
+originality of this approach is that the various components must
+cooperate dynamically and be
+configurable.
+
+\image html image54.jpg
+
+<br>SALOME platform integrates a number of modules each having its own function:
+<ul>
+<li>\b KERNEL : provides a common shell for all components, which can be integrated into the SALOME platform.
+<li>\b GUI : provides visual representation: basic widgets, viewers
+etc. Third party modules optionally can have GUI, but in any case they always connected with KERNEL.
+<li>\b Geometry : facilitates construction and optimization of geometrical models using a wide range of CAD functions.
+<li>\b Mesh : generates meshes on geometrical models previously created or imported by the Geometry component.
+<li>\b Supervisor : provides tools for construction of graphs and execution of calculations.
+<li>\b Post-Pro : performs data visualization.
+<li>\b MED : allows to work with MED files.
+</ul>
+
+*/
--- /dev/null
+/*!
+
+\image html icon_about.png
+
+\page introduction_page Introduction
+
+<br>
+
+Welcome to SALOME Platform! Modern technological products (cars,
+structures, electrical or electronic equipment) are getting more and
+more complex every year and must meet increasingly severe requirements
+in terms of quality and performance. For example, for structures and
+their environment the demands to reduce risks and optimize costs are
+extremely high. It requires particularly refined simulations
+concerning structural behavior and robustness to ensure high
+reliability.
+\n The numeric modeling of a physical problem, the development of
+solutions and their integration into the design process are often
+handled in very specific environments. SALOME represents a generic
+CAD-based application for digital simulation with "high reactivity to
+market evolutions and customer expectations".
+
+SALOME is a free software that provides a generic platform for Pre and
+Post-Processing for numerical simulation. It is based on an open and
+flexible architecture made of reusable components available as free
+software.
+
+SALOME is a CAD/CAE integration platform. It provides reusable
+components for:
+<ul>
+<li>3D modeling (bottom-up construction, import, healing);
+<li>Visualization;
+<li>Computational schemas management;
+<li>Post-processing.
+</ul>
+
+SALOME is tailored for integration of custom components:
+<ul>
+<li>CAD interfaces;
+<li>Mesh generators;
+<li>Finite Element solvers with specific pre-processors.
+</ul>
+
+The SALOME platform is available in Open Source.
+
+<b>Salome Platform:</b>
+<ul>
+<li>Supports interoperability between CAD modeling and computation software (CAD-CAE link)
+<li>Makes easier the integration of new components on heterogeneous systems for numerical computation
+<li>Sets the priority to multi-physics coupling between computation software
+<li>Provides a generic user interface, user-friendly and efficient, which helps to reduce the costs and delays of carrying out the studies
+<li>Reduces training time to the specific time for learning the software solution which has been based on this platform
+<li>All functionalities are accessible through the programmatic
+integrated Python console
+</ul>
+
+\image html image65.gif
+
+<b>What can you do in SALOME? (Some of SALOME main functions)</b>
+<ul>
+<li>Define geometrical models (create/modify geometrical items), import and export them using the BREP, IGES and STEP formats;
+<li>Define meshing of these geometrical items, import and export them;
+<li>Handle physical properties and quantities attached to geometrical items, import and export them to a reusable format;
+<li>Perform computations using a solver (optionally provided): read input data, configure the solver, and write calculation results);
+<li>Visualize result fields in 3D, 2D and export images of their visualization to an appropriate format;
+<li>Manage study schemes: definition, save/restore;
+<li>Manage computation schemes: definition, execution.
+</ul>
+
+*/
\ No newline at end of file
--- /dev/null
+/*!
+
+\page introduction_to_gui_page Introduction to GUI
+
+\b GUI (Graphical User Interface) provides a common shell for all components, which can be integrated into the SALOME platform.
+
+\b GUI component in SALOME platform provides:
+<ul>
+<li>Common desktop environment (\ref salome_desktop_page "SALOME desktop") for all
+components</li>
+<li>Component integration and management: uploading, switching,
+component menus/toolbars handling</li>
+<li>Study management (creation, saving, loading, editing studies)</li>
+<li>Multi-window management in the framework of one study</li>
+<li>Management of objects created or imported into the SALOME
+application (\ref using_object_browser_page "Object Browser")</li>
+<li>Integrated Python interpreter</li>
+<li>Output messages window</li>
+<li>Additional tools : \ref using_catalog_generator_page "Catalogue Generator",
+\ref using_registry_tool_page "Registry tool"</li>
+<li>Standard viewers for data visualization:</li>
+<ul>
+<li>VTK 3d viewer
+<li>OCC 3d viewer
+<li>Gauss Points viewer
+<li>Plot 2d viewer
+<li>Supervision viewer
+</ul>
+</ul>
+
+
+
+Since version 3.0.0 SALOME GUI is based on SUIT (Salome User Interface
+Toolkit) that proposes very flexible, powerful and safe mechanisms of
+interaction with SALOME tool components (both CORBA and standalone),
+resources management, viewers and selection handling,
+exception/signals processing, bringing to top multi-desktop
+dockable-windowed user interface which improves the usability of
+SALOME GUI.
+\n All Graphical User Interfaces of standard modules have plug-in
+structure, i.e. each module is placed in a dynamic library which is
+loaded on demand. All modules can create their own menu items, buttons
+in toolbar, windows etc
+
+*/
\ No newline at end of file
--- /dev/null
+/*!
+
+\page mesh_preferences_page Mesh preferences
+
+In the Mesh module you can set mesh preferences, which can be used in
+later sessions with this module.
+
+<h2>General Preferences</h2>
+
+\image html pref21.png
+
+<ul>
+<li><b>Update</b></li>
+<ul>
+<li>If you toggle <b>Automatic Update</b> checkbox, the model in your
+viewer automatically updated whenever you make changes in it.</li>
+</ul>
+<li><b>Quality Controls</b></li>
+<ul>
+<li>If you toggle <b>Display entity</b>, both faces and edges of an
+object will be displayed in the viewer by default.</li>
+<li>If you toggle <b>Use precision</b> checkbox, you can display numbers in
+<b>Quality Control</b> diagrams at the necessary level of precision.</li>
+</ul>
+<li><b>Precision</b> - can be defined by the <b>Number of digits after point</b> in
+the corresponding field. By default, numbers in <b>Quality Control</b>
+diagrams are presented as integers.</li>
+<li><b>Display mode</b> - allows to set Wireframe, Shading, Nodes or Shrink
+presentation mode as default.</li>
+<li><b>Mesh export</b></li>
+<ul>
+<li>If you toggle <b>Automatically create groups for MED export</b> checkbox,
+this operation will be carried out automatically.</li>
+<li>If you toggle <b>Automatic renumbering</b> checkbox, the exported
+mesh will be renumbered automatically</li>
+</ul>
+<li><b>Mesh computation</b></li>
+<ul>
+<li><b>Show a computation result notification</b> combobox allows to
+select the notification mode about a mesh computation result.
+There are 3 possible modes:</li>
+<ul>
+<li><b>Never</b> - do not show the result dialog at all;</li>
+<li><b>Errors only</b> - the result dialog will be shown if there were
+some errors during a mesh computation;</li>
+<li><b>Always</b> - show the result dialog after each mesh
+computation. This is a default mode.</li>
+</ul>
+</ul>
+
+<h2>Mesh Preferences</h2>
+
+\image html pref22.png
+
+<ul>
+<li><b>Nodes</b></li>
+<ul>
+<li><b>Color</b> - allows to select the color of nodes. Click on the
+colored line to access to the \ref select_color_and_font_page "Select Color"
+dialog box.</li>
+<li><b>Size</b> - allows to define the size of nodes.</li>
+</ul>
+<li><b>Elements</b></li>
+<ul>
+<li><b>Fill</b> - allows to select the color of surface of elements
+(seen in Shading mode). Click on the colored line to access to the
+\ref select_color_and_font_page "Select Color" dialog box.</li>
+<li><b>Outline</b> - allows to select the color of borders of
+elements. Click on the colored line to access to the
+\ref select_color_and_font_page "Select Color" dialog box.</li>
+<li><b>Back Face</b> - allows to select the color of interior surface
+of elements. Click on the colored line to access to the
+\ref select_color_and_font_page "Select Color" dialog box.</li>
+<li><b>Width</b> - allows to define the width of lines (edges and borders of elements).</li>
+<li><b>Shrink coef.</b> - allows to define relative space of elements
+compared to gaps between them in shrink mode.</li>
+</ul>
+</ul>
+
+<br><h2>Selection Preferences</h2>
+
+\image html pref23.png
+
+<ul>
+<li><b>Selection</b> - performed with mouse-indexing (preselection)
+and left-clicking on an object, whose appearance changes as defined in
+the <b>Preferences</b>.</li>
+<ul>
+<li><b>Object Color</b> - allows to select the color of mesh (edges and
+borders of meshes) of the selected entity. Click on the colored line
+to access to the \ref select_color_and_font_page "Select Color" dialog
+box.</li>
+<li><b>Element color</b> - allows to select the color of surface of selected
+elements (seen in Shading mode). Click on the colored line to access
+to the \ref select_color_and_font_page "Select Color" dialog box.</li>
+<li><b>Width</b> - allows to define the width of selected edges. </li>
+</ul>
+<li><b>Preselection</b> - performed with mouse-indexing on an object,
+whose appearance changes as defined in the <b>Preferences</b>.</li>
+<ul>
+<li><b>Highlight Color</b> - allows to select the color of mesh (edges and
+borders of meshes) of the entity . Click on the colored line to access
+to the \ref select_color_and_font_page "Select Color" dialog box.</li>
+<li><b>Width</b> - allows to define the width of preselected edges.</li>
+</ul>
+<li><b>Precision</b> - in this menu you can set the value of precision
+used for <b>Nodes</b>, <b>Elements</b> and <b>Objects</b>.</li>
+</ul>
+
+<br><h2>Scalar Bar Preferences</h2>
+
+\image html pref24.png
+
+<ul>
+<li><b>Font</b> - in this menu you can set type, face and color for
+the font of <b>Title</b> and <b>Labels</b>.</li>
+<li><b>Colors & Labels</b> - in this menu you can set the <b>number of
+colors</b> and the <b>number of labels</b> in use.<li>
+<li><b>Orientation</b> - here you can choose between vertical and
+horizontal orientation of the <b>Scalar Bar</b></li>.
+<li><b>Origin & Size Vertical & Horizontal</b> - allows to define
+placement (<b>X</b> and <b>Y</b>) and lookout (<b>Width</b> and
+<b>Height</b>) of Scalar Bars</li>
+<ul>
+<li><b>X</b>: abscissa of the point of origin (from the left
+side)</li>
+<li><b>Y</b>: ordinate of the origin of the bar (from the bottom)</li>
+</ul>
+</ul>
+
+*/
\ No newline at end of file
--- /dev/null
+/*!
+
+\page occ_3d_viewer_page OCC 3D Viewer
+
+<b>OCC (Open CasCade) 3D viewer</b> has been developed on the basis of Open
+CASCADE Technology. This is the default viewer for Geometry Module,
+providing good representation of construction and transformation of
+geometrical objects. Only this viewer allows to work with groups and
+sub-shapes. This viewer can also work in Mesh module, however, it
+doesn't allow to visualize meshes.
+
+The functionalities of OCC viewer are available via its Viewer
+Toolbar. Buttons marked with small downward triangles have extended
+functionality which can be accessed by locking on them with left mouse
+button.
+
+\image html occviewer_toolbar.png "Viewer Toolbar"
+
+<hr>
+\image html image77.gif
+\n <center><b>Dump View</b> - exports an object from the viewer in bmp, png, jpg
+or jpeg image format.</center>
+<hr>
+
+\image html image88.gif
+\n <center><b>Show/Hide Trihedron</b> - shows or hides coordinate axes.</center>
+<hr>
+
+\image html image96.gif
+\n <center><b>Fit all</b> - allows to select a point to be the center of a
+scene representing all displayed objects in the visible area.</center>
+<hr>
+
+\image html image97.gif
+\n <center><b>Fit area</b> - resizes the view to place in the visible area
+only the contents of a frame drawn with pressed left mouse button.</center>
+<hr>
+
+\image html image98.gif
+\n <center><b>Zoom</b> - allows to zoom in and out.</center>
+<hr>
+
+\image html image99.gif
+\n <center><b>Panning</b> - if the represented objects are greater that the
+visible area and you don't wish to use <b>Fit all</b> functionality, click on
+this button and you'll be able to drag the scene to see its remote
+parts.</center>
+<hr>
+
+\image html image100.gif
+\n <center><b>Global panning</b> - represents all displayed objects in
+the visible area.</center>
+<hr>
+
+\image html view_rotation_point.png
+\n <center><b>Change rotation point</b> - allows to to choose the point around
+which the rotation is performed.</center>
+
+\image html set_rotation_point_dialog1.png
+
+<center>By default the rotation point is located in the Center of the bounding
+box of an object.</center>
+
+\image html set_rotation_point_dialog2.png
+
+<center>Unchecking <b>Use Bounding Box Center</b> checkbox allows you to
+define the coordinates of the rotation point manually.</center>
+
+<b>Set to Origin</b> button restores the default rotation point
+coordinates.\n
+<b>Select Point from View</b> button allows to select the rotation
+point in the 3D Viewer.
+<hr>
+
+\image html image89.gif
+\n <center><b>Rotation</b> - allows to rotate the selected object using the
+mouse.</center>
+
+\image html image102.gif
+
+<center>These buttons orientate the scene strictly about coordinate axes.</center>
+<hr>
+
+\image html image91.gif
+\n <center><b>Reset</b> - restores the default position (isometric) of
+objects in the scene.</center>
+<hr>
+
+\image html image103.gif
+\n <center><b>Memorise view</b> - saves the current position of
+objects in the scene.</center>
+<hr>
+
+\image html image105.gif
+\n <center><b>Restore view</b> - restores the saved position of
+objects in the scene.</center>
+<hr>
+
+\image html image86.gif
+\n <center><b>Clone view</b> - opens a new duplicate scene.</center>
+<hr>
+
+\image html image106.gif
+\n <center><b>Clipping</b> - allows to create cross-section views
+(clipping planes) of geometrical objects.</center>
+
+\image html clipping.png
+<ul>
+<li><b>Base point</b> - allows to define the coordinates of the base
+point for the clipping plane.</li>
+<ul>
+<li><b>Reset</b> - returns the base point to coordinate origin.</li>
+</ul>
+<li><b>Direction</b> - allows to define the orientation of the
+clipping plane.</li>
+<ul>
+<li><b>Invert</b> - allows to select which part of the object will be removed
+and which will remain after clipping.</li>
+</ul>
+<li><b>Preview</b> - allows to see the results of clipping in the
+viewer.</li>
+</ul>
+<hr>
+\image html occviewer_axialscale.png
+\n <center><b>Scaling</b> - represents objects deformed (stretched or
+stuffed) along the axes of coordinates.</center>
+
+<b>Note!</b> OCC Viewer features a special <b>Polyline Selection</b> mechanism, which allows selecting an arbitraty part of the graphic area using a polygon frame, instead of the usual selection with a rectangular frame.
+
+To produce a Polyline Selection, lock the right mouse button and draw the first side of the polygon, then change the direction by clicking the left mouse button add draw another side, etc. The whole selection frame is drawn with the locked right mouse button.
+
+\image html polyselection1.png
+
+As a result, only the nodes within the frame are selected.
+
+\image html polyselection2.png
+
+*/
--- /dev/null
+/*!
+
+\page opening_studies_page Opening studies
+
+In \b SALOME all studies are stored in a special format *.hdf.
+
+<em>To open an existing study:</em>
+\par
+In the main toolbar click "Open document" button or from the main menu select <b>File > Open</b>
+option. From a standard Search File dialog box choose the required
+*.hdf file and click \b Open button.
+
+\image html open.jpg ""Open document" button"
+
+<em>To load an unloaded study (\ref saving_and_closing_studies_page
+"see also"):</em>
+\par
+From the main menu select <b>File > Connect</b> option. In the following
+dialog box select one of the studies, which has been previously
+created and unloaded and click \b Ok button:
+
+\image html loadstudy2.png
+
+\par
+Alternatively, it is possible to select <b>File > Most Recently Used > </b> to select a study from the list.
+
+
+\n\b Tip: After opening an existing study, you will see its structure
+in the \ref using_object_browser_page "Object Browser". It will contain the objects created with the
+help of different components during the previous study session. If you
+right-click on one of the objects and from the associated pop-up menu
+choose <b>Open With</b> option, which will automatically launch the component
+corresponding to this object.
+
+*/
\ No newline at end of file
--- /dev/null
+/*!
+
+\page plot2d_viewer_page Plot 2D viewer
+
+\n <b>Plot 2d viewer</b> is destined to the representation of 2d
+plots and graphs in Post-Pro module.
+\n Its viewer toolbar gives you fast access to the following
+operations:
+
+\image html image77.gif
+<center><b>Dump View</b> - exports an object from the viewer in bmp,
+png, jpg or jpeg image format.</center>
+
+\image html image96.gif
+<center><b>Fit all</b> - scales the display to show the entire
+scene. Use this to resize the scene so that it could fit within the
+Viewer boundary.</center>
+
+\image html image97.gif
+<center><b>Fit area</b> - resizes the view to place in the visible
+area only the contents of a frame drawn with pressed left mouse
+button.</center>
+
+\image html image98.gif
+<center><b>Zoom</b> - allows to zoom in and out.</center>
+
+\image html image99.gif
+<center>\b Panning - if the represented objects are greater that the
+visible area and you don't wish to use Fit all functionality, click on
+this button and you'll be able to drag the scene to see its remote
+parts.</center>
+
+\image html image100.gif
+<center><b>Global panning</b> - allows to define the center of the
+scene presenting all displayed objects in the visible area.</center>
+
+\image html plot2d_points.gif
+<center><b>Draw Points</b> - represents points on the graph.</center>
+
+\image html plot2d_lines.gif
+<center><b>Draw Lines</b> - represents lines on the graph.</center>
+
+\image html plot2d_splines.gif
+<center><b>Draw Splines</b> - represents splines on the graph.</center>
+
+\image html plot2d_logarithmic_horizontal.gif
+<center><b>Horizontal axis logarithmic</b> - changes the scaling on
+horizontal axis to logarithmic.</center>
+
+\image html plot2d_logarithmic_vertical.gif
+<center><b>Vertical axis logarithmic</b> - changes the scaling on vertical
+axis to logarithmic.</center>
+
+\image html plot2d_legend.gif
+<center><b>Show Legend</b> - reveals all verbal and numerical
+information on the graphs.</center>
+
+\image html plot2d_settings.gif
+<center>\b Settings - calls a menu, in which you can specify advanced
+settings for your Plot 2d Viewer.</center>
+
+\image html plot2d_clone.gif
+<center><b>Clone view</b> - opens a new duplicate scene.</center>
+
+\anchor settings
+\n \image html plot2d_view_settings.png
+
+The options are as follows:
+<ul>
+<li><b>Main title:</b> the title of the XY plot. By default, it will
+consist of the names of the tables, on the basis of which the curve
+lines have been constructed.</li>
+<li><b>Curve type:</b> you can select from \b Points, \b Lines and \b Spline.</li>
+<li><b>Show legend:</b> here you can define the position of the
+description table on the XY plot (to the \b Left, to the \b Right, on
+\b Top or on \b Bottom).</li>
+<li><b>Marker size</b> - size of the points (markers) forming curve lines.</li>
+<li><b>Background color</b> of the XY plot.</li>
+<li><b>Scale mode:</b> here you can select the type of scaling (\b
+Linear or \b Logarithmic) along <b>X (Horizontal)</b> or <b>Y (Vertical)</b> axes.</li>
+</ul>
+
+You can define settings for each axis separately:
+<ul>
+<li>\b Horizontal or \b Vertical axis title.</li>
+<li><b>Grid/Axes marks:</b> here you can define the maximum number of major
+and minor scale divisions for a specified axis. The real number of
+intervals fits to {1,2,5}*10^N, where N is a natural number, and
+doesn't exceed the maximum.</li>
+<li><b>Save settings as default:</b> If this check box is marked, all
+XY plots will be displayed with these defined properties.</li>
+</ul>
+
+*/
--- /dev/null
+/*!
+
+\page postpro_preferences_page Post-Pro Preferences
+
+In the Post-Pro module you can set preferences, default settings,
+which can be used in later sessions with this module.
+
+<h2>MED import Preferences</h2>
+
+\image html ppref1.png
+
+<ul>
+<li><b>MED files import</b></li>
+<ul>
+<li><b>Use Build Progress</b> - when this option is checked you can choose
+all other import MED options at the moment of loading of each file
+using <b>Build Progress</b> menu, otherwise the loading will be done
+according to the <b>Preferences</b> without addressing to the
+user.</li>
+<li><b>Full MED Loading</b> - when this option is checked, the MED file is
+fully loaded in the study, and no additional access to the MED file is
+needed during the session. Reversibly, when unchecked, the MED file is
+loaded on demand. This is the default behaviour in SALOME and
+recommended for big files to optimize memory usage.</li>
+<li><b>Build at once</b> - when this option is checked, you can't
+perform any operations until the MED file is fully loaded and
+processed.</li>
+<li><b>Build fields</b> - when this option is checked, the fields are
+built automatically at loading.</li>
+<li><b>Build min/max</b> - when this option is checked, minimum and
+maximum values of the time stamps are found at loading.</li>
+<li><b>Build groups</b> - when this option is checked, the groups and
+families are built automatically at loading.</li>
+<li><b>Close dialog at finish</b> - when this option is checked, the
+dialog box is closed after loading of the selected MED file. When
+unchecked, it allows loading other MED files.</li>
+</ul>
+</ul>
+
+<br><h2>Scalar Bar Preferences</h2>
+
+\image html pref31.png
+
+<ul>
+<li><b>Scalar Range</b></li>
+<ul>
+<li><b>Scalar Mode</b> - this feature allows refining the value to be
+inspected:</li>
+<ul>
+<li><b>Modulus:</b> value of a scalar or modulus of a vector.</li>
+<li><b>Component N:</b> Nth component of a vector, a tensor or a matrix.</li>
+</ul>
+<li><b>Logarithmic Scaling</b> - this checkbox toggles logarithmic
+scaling.</li>
+<li><b>Ranges to Use</b> - you can use either Field Range or Imposed Range.</li>
+</ul>
+<li><b>Min and Max for Imposed Range</b> - in this menu you can set
+the limits for your Imposed Range, if you have chosen to use it.</li>
+<li><b>Font</b> - in this menu you can set type, face and color for
+the font of <b>Title</b> and <b>Labels</b>.</li>
+<li><b>Colors & Labels</b> - in this menu you can set the <b>number of
+colors</b> and the <b>number of labels</b> in the Scalar bar.</li>
+<li><b>Orientation</b> - here you can choose between vertical and horizontal
+orientation of the Scalar Bar.</li>
+<li><b>Origin & Size Vertical & Horizontal</b> - allows to define
+placement (<b>X</b> and <b>Y</b>) and lookout (<b>Width</b> and
+<b>Height</b>) of Scalar Bars.</li>
+<ul>
+<li><b>X:</b> abscissa of the point of origin (from the left
+side)</li>
+<li><b>Y:</b> ordinate of the origin of the bar (from the bottom)</li>
+</ul>
+<li><b>Scalar bars default position</b></li>
+<ul>
+<li><b>Arrange Scalar Bars</b> - this option prevents superposition of
+scalar bars during visualisation of several fields in the same
+window. If checked, a separate scalar bar is displayed for each
+presentation.</li>
+</ul>
+</ul>
+
+<br><h2>Cut Lines Preferences</h2>
+
+\image html ppref2.png
+
+<ul>
+<li><b>CutLine Preferences</b></li>
+<ul>
+<li><b>Show preview</b> check box allows to edit the parameters of the
+presentation and simultaneously observe the preview of this
+presentation in the viewer.</li>
+<li><b>Invert all curves</b> check box allows to invert the resulting
+curves.</li>
+<li><b>Use absolute length</b> check box allows to use absolute length
+for curves.</li>
+<li><b>Generate Data Table:</b> If this check box is marked, <b>Post
+Pro</b> will automatically generate a data table on the basis of your
+Cut Lines presentation. This table will be created in the structure of
+the study.</li>
+<li><b>Generate Curves:</b> If this check box is marked, <b>Post Pro</b> will
+automatically generate curve lines on the basis of values taken from
+the generated data table. These curves will be created in the
+structure of the study and can be visualized in a XY plot.</li>
+</ul>
+</ul>
+
+<br><h2>Sweep Preferences</h2>
+
+\image html ppref3.png
+
+<ul>
+<li><b>Sweeping preferences</b></li>
+<ul>
+<li><b>Mode of the Sweeping</b> - allows to choose between Linear,
+Cosinusoidal and sinusoidal sweeping.</li>
+<li><b>Time step</b> - in this menu you can set the time of
+representation of one step.</li>
+<li><b>Number of cycles</b> - in this menu you can define the number
+of times this animation will be repeated.</li>
+<li><b>Number of steps</b> - in this menu you can define the number of
+steps, which will compose the whole animation.</li>
+<li><b>Parameter varies</b> - allows to choose the range for the
+parameter: from 0 to Pi or from Pi to -Pi.</li>
+</ul>
+</ul>
+
+<ul>
+<li><b>Animation preferences</b></li>
+<ul>
+<li><b>Speed</b> - allows to define the speed of the animation.</li>
+<li><b>Cycled animation</b> - allows to start a cycled animation of the presentation.</li>
+<li><b>Use proportional timing</b> - allows to render the animation with proportional periods of time between every frame (not depending on the time stamps).</li>
+<li><b>Clean memory at each frame</b> - this option allows to optimize the performance of the operation.</li>
+</ul>
+</ul>
+
+<br><h2>Representation Preferences</h2>
+
+\image html pref33.png
+
+<ul>
+<li><b>Representation properties</b> - these checkboxes allow to
+choose the default representation type for each field presentation.</li>
+<ul>
+<li><b>Use Shading</b> - when this option is checked, the objects will
+be displayed with shading.</li>
+<li><b>Display only on creation</b> - when this option is checked, all
+previously created presentations will be automatically removed from
+the viewer when a new presentation is created and displayed. You can
+restore the previously created presentations using the Object
+Browser.</li>
+</ul>
+</ul>
+
+<br><h2>3D Cache</h2>
+
+\image.html pref40.png
+
+<ul>
+<li><b>3D Cache Preferences</b> - allow to define the mode of usage
+and the size of the 3D Cache, which enables to save in RAM and quickly
+restore the states of field animation.</li>
+<ul>
+<li><b>Memory Mode</b> - allows to define the mode of usage
+of the 3D Cache: <b>Minimal</b> actually disables the Cache,
+<b>Limited</b> Cache size depends on the current system
+configuration.</li>
+<li><b>Memory Limit</b> - allows to define the maximum size of the 3D
+Cache</li>
+</ul>
+</ul>
+
+
+<br><h2>Gauss Points Preferences</h2>
+
+\image html pref34.png
+
+<ul>
+<li><b>Primitive</b> - this menu allows user to choose the graphic
+primitive to use to present the results at Gauss points in the
+viewer.</li>
+<ul>
+<li><b>Primitive type</b> - provides choice between <b>Point
+sprites</b>, <b>Open GL points</b> and <b>Geometrical Spheres</b>.</li>
+<li><b>Maximum Size (Clamp)</b> - defines the maximum size of sprite
+points ranging from 1 to 512. By default the value is set to 256
+pixels.</li>
+<li><b>Main Texture</b> - path to the <b>Main Texture</b> (16x16
+pixels) which defines the shape of the point sprite used for
+rendering.</li>
+<li><b>Alpha Channel Texture (16*16)</b> - path to the <b>Alpha
+Channel Texture</b> which defines the texture of the point
+sprite.</li>
+<li><b>Alpha Channel Threshold</b> - defines the level of transparency
+ranging from 0 to 1.</li>
+<li><b>Geometrical Sphere Resolution</b> - defines the number of faces
+of <b>Geometry Spheres</b>.</li>
+<li><b>Notify when number of faces exceeds</b> - limitation of the
+number of faces; the user will be warned if it exceeds the given
+value.</li>
+</ul>
+</ul>
+
+<ul>
+<li><b>Size</b> - in this menu you can define:</li>
+<ul>
+<li><b>Range value for min and max size</b> - these two parameters
+will be respectively multiplied by a reference length (average size of
+cells of the mesh) to define the range for minimum and maximum size of
+a point during rendering (at magnification = 100%). Default values
+are:</li>
+<ul>
+<li><b>Rainbow</b> scale: <b>min</b> = <b>10%</b>, <b>max</b> =
+<b>33%</b></li>
+<ul>
+<li>Min size is associated to the smallest real value (including
+negative values).</li>
+<li>Max size is associated to the largest real value.</li>
+</ul>
+<li><b>Bicolor</b> scale: <b>min</b> = <b>0</b> (not editable),
+<b>max</b> = <b>33%</b></li>
+<ul>
+<li>Null size is associated to the 0 scalar value.</li>
+<li>Max size is associated to the largest absolute value.</li>
+</ul>
+</ul>
+Both values are dynamically updated by the system according to the
+selected scalar bar. In the case of a Bicolor scale, the minimum value
+is set to 0 in the dialog and the control is disabled.
+<li><b>Magnification (%)</b> corresponds to the change of size of
+results at Gauss point primitives in 2D space. Acceptable values range
+from 0 to N; 100% means no magnification, 50% means half of its size,
+200% mean twice its size and so forth. By default this value is set to
+100%.</li>
+<li><b>+/- Ratio</b> corresponds to the number by which the
+magnification will be respectively multiplied or divided at edition,
+ranging from 0.01 to 10. By default this value is set to 2.</li>
+</ul>
+</ul>
+
+<ul>
+<li><b>Geometry</b></li>
+<ul>
+<li><b>Size of points (%)</b> defines a value that will be multiplied
+by a reference length (representative of the average size of cells of
+the mesh) to define the size of points during rendering (at
+magnification = 100%). Default values 10%.</li>
+<li><b>Color</b> - allows to select the color of points used for
+presentations. Click on the colored line to access to the \ref
+select_color_and_font_page "Select Color" dialog box.</li>
+</ul>
+</ul>
+
+<ul>
+<li><b>Gauss Points Scalar Bar</b></li>
+<ul>
+<li><b>Active Bar</b> - this option allows to choose <b>Local</b> or
+<b>Global</b> Bar as active.</li>
+<li><b>Display Global Bar</b> - this option allows to visualize or to
+hide the Global Bar.</li>
+<li><b>Scalar Bar Mode</b> - this option allows to choose between
+<b>Bicolor</b> and <b>Rainbow</b> Scalar Bar Mode.</li>
+<li><b>Spacing</b> - allows to define Spacing from 0.01 to 1.</li>
+</ul>
+</ul>
+
+<br><br><b>Inside<b> and </b>Outside Cursor Preferences</b> allow to set
+<b>Primitives</b>, <b>Size</b> and <b>Magnification</b> for the
+respective zones.
+
+<br><h2>Picking Preferences</h2>
+
+\image html pref37.png
+
+<ul>
+<li><b>Cursor</b> - allows to adjust the Size of the cursor used for
+Picking (ranging from 0.1 to 1), the Height of the pyramids (ranging
+from 0 to 10) and the Selection cursor color.</li>
+<li><b>Tolerance</b> - defines at which distance of the cursor from
+the point it becomes selected (ranges from 0.001 to 10).</li>
+<li><b>Information window</b> - allows to define the
+<b>Transparency</b> (from 0% = opaque to 100% = transparent) and
+<b>Position</b> of the window, which can be:</li>
+<ul>
+<li><b>Centred below the point</b>, or</li>
+<li>located at <b>Top-left corner of the 3D view</b></li>
+</ul>
+<li><b>Movement of the Camera</b> can also be define by the user.</li>
+<ul>
+<li><b>Zoom at first selected point</b> - This value is used to define
+the focal distance at the first selected point (at the end of the
+movement of the camera). This value is a ratio that will be multiplied
+by the current zoom value.</li>
+<li><b>Number of steps between two positions</b> - defines the
+smoothness of camera movement at selection by the number of
+iterations. If set to 1 the camera is zoomed and centered at the point
+momentarily. Greater numbers mean very slow camera movement.</li>
+</ul>
+<li><b>Display parent mesh element</b> - allows to visualize or hide
+the patent mesh element of the selected gauss point.</li>
+</ul>
+
+<br><h2>Navigation Preferences</h2>
+
+\image html pref38.png
+
+<br>
+<ul>
+<li><b>Mouse</b></li>
+<ul>
+<li><b>Mouse Behaviour</b> - this option allows to choose one of the
+modes of work with mouse in Gauss Viewer.</li>
+<ul>
+<li><b>Salome Standard Controls</b> - allows to manipulate objects in the
+viewer with the mouse and locked Ctrl button: increase or decrease the
+zoom ratio with the left mouse button, translate object in any
+direction with the central mouse button or rotate it with the right
+mouse button.</li>
+<li><b>Keyboard Free</b> - allows to manipulate objects in the viewer
+with the mouse without locking Ctrl button. In this case the
+operations are assigned to the buttons differently: rotation is made
+with the left button, translation with the right and zoom with both
+pressed in the same time.</li>
+</ul>
+</ul>
+</ul>
+
+<ul>
+<li><b>Keyboard</b></li>
+<ul>
+<li><b>[+]/[-] Speed Increment</b> - defines the number of units by
+which the speed increases or respectively decreases after pressing [+]
+or [-] keyboard buttons.</li>
+</ul>
+</ul>
+
+<ul>
+<li><b>Spacemouse</b> - a mouse-like manipulator device specially designed
+for working with 3D presentations, objects, etc. You can reassign the
+actions listed below to any of its buttons.</li>
+<ul>
+<li><b>Decrease Speed Increment</b> - decreases by 1 the speed increment used for the keyboard (same as [-] key).</li>
+<li><b>Increase Speed Increment</b> - increase by 1 the speed increment used for the keyboard (same as [+] key).</li>
+<li><b>Decrease Gauss Points Magnification</b> - divides the current magnification by the magnification ratio.</li>
+<li><b>Increase Gauss Points Magnification</b> - multiplies the current magnification by the magnification ratio.</li>
+<li><b>Dominant / combined switch</b> - toggles button to switch to dominant or combined movements.</li>
+</ul>
+</ul>
+
+<br><h2>Recorder Preferences</h2>
+
+\image html pref38.png
+
+<ul>
+<li><b>Settings</b></li>
+<ul>
+<li><b>Mode</b> - allows to choose from two recording regimes:</li>
+<ul>
+<li><b>Recording all displayed frames</b> - records exactly at the FPS rate specified by the user.</li>
+<li><b>Recording at a given FPS</b> - records only when the contents
+of the viewer change (some activity is performed). In the AVI file
+non-recorded images are substituted with the copies of the latest
+recorded image, which produces files with lower quality but requires
+less system resources. </li>
+</ul>
+<li><b>FPS</b> - allows to define the FPS (frames per second) rate for
+the clip. Set greater value for better quality.</li>
+<li><b>Quality</b> - allows to set the quality of the clip in the
+interval between 0 and 100.</li>
+<li><b>Progressive</b> - allows to record a progressive API
+file.</li>
+</ul>
+</ul>
+
+*/
--- /dev/null
+/*!
+
+\page running_salome_page Running SALOME
+
+<em>To launch SALOME:</em>
+<ol>
+<li>Install the SALOME package into a definite directory (ex. \b SALOME)
+on your hard disk. It is preferable if you use the special
+installation procedure allowing to install the SALOME platform and
+all corresponding applications.</li>
+<li>The installation shell script will create a special file:
+<b>salome.csh</b> (CShell file) in your SALOME/KERNEL directory. This file
+contains all environment variables necessary for launching SALOME
+platform with other application products provided with SALOME
+installation package. You have a possibility to add one of them into
+your profile if you enter in the command console the following: <br><br>
+<tt>source salome.csh</tt>
+
+<b>Tip:</b> During the installation procedure you have a possibility to set your profile automatically.</li>
+
+<li> Launch SALOME platform, using the following Python script located
+in the <b>SALOME/KERNEL/bin/salome</b> directory:<br><br>
+<ul>
+<li>\b runSalome.py [command line options]
+</ul>
+</li>
+</ol>
+
+\anchor batch_mode_run
+
+<table>
+<tr>
+<td><h2>Options</h2></td>
+<td><h2>Description</h2></td>
+</tr>
+<tr>
+<td>--\b help or -\b h</td>
+<td>print this help</td>
+</tr>
+<tr>
+<td>--\b gui or -\b g</td>
+<td>launch with GUI</td>
+</tr>
+<tr>
+<td> --\b terminal or -\b t</td>
+<td>launch without GUI in batch mode</td>
+</tr>
+<tr>
+<td>--\b logger or -\b l</td>
+<td>redirects log messages in the file <em>logger.log</em></td>
+</tr>
+<tr>
+<td>--\b file=<b>\<FILE\></b> or -\b f=<b>\<FILE\></b></td>
+<td>redirects log messages in a custom file</td>
+</tr>
+<tr>
+<td>--\b xterm or -\b x</td>
+<td>the servers open an xterm window and log messages are displayed in this window</td>
+</tr>
+<tr>
+<td>--\b modules=\b module1,\b module2,... or -\b m=\b module1,\b module2,...</td>
+<td>list of SALOME modules which will be loaded into the module catalogue</td>
+</tr>
+<tr>
+<td>--\b embedded=<b>registry,study,moduleCatalog,cppContainer</b>,
+or -\b e=<b>registry,study,moduleCatalog,cppContainer</b></td>
+<td>embedded CORBA servers (default: registry,study,moduleCatalog,cppContainer)
+note that logger,pyContainer,supervContainer can't be embedded</td>
+</tr>
+<tr>
+<td>--\b standalone=<b>registry,study,moduleCatalog,cppContainer,pyContainer,supervContainer</b>, or
+-\b s=<b>registry,study,moduleCatalog,cppContainer,pyContainer,supervContainer</b></td>
+<td>standalone CORBA servers (default: pyContainer,supervContainer)</td>
+</tr>
+<tr>
+<td>--\b containers=<b>cpp,python,superv</b>
+or -\b c=<b>cpp,python,superv</b></td>
+<td>launch of cpp, python and supervision containers</td>
+</tr>
+<tr>
+<td>--\b portkill or -\b p</td>
+<td>kill SALOME launched with the current port</td>
+</tr>
+<tr>
+<td>--\b killall or -\b k</td>
+<td>kill SALOME</td>
+</tr>
+<tr>
+<td>--<b>interp</b>=<b>n</b> or -<b>i</b>=<b>n</b></td>
+<td>number of additional xterm to open, with session environment</td>
+</tr>
+<tr>
+<td>-\b z</td>
+<td>display splash screen</td>
+</tr>
+<tr>
+<td>-\b r</td>
+<td>disable centralized exception handling mechanism</td>
+</tr>
+</table>
+
+<b>Tip:</b> If the \b runSalome.py script is launched without prompting
+any options, they will be taken by default from the file <b>SalomeApp.xml
+(SALOME/GUI/share/salome/resources/SalomeApp.xml)</b>. 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.
+
+*/
\ No newline at end of file
--- /dev/null
+/*!
+
+\page salome_architecture_page SALOME architecture
+
+
+\b SALOME architecture is based on \b CORBA technology using
+distributed system model of applications. This architecture takes the
+concept of multitier client/server to its natural conclusion. The
+distributed system model exposes all functionality of the application
+as objects, each of which can use any of the services provided by
+other objects in the system, or even objects in other systems. The
+architecture can also blur the distinction between "client" and
+"server" because the client components can also create objects that
+behave in server-like roles. This architecture provides the ultimate
+in flexibility.
+
+
+
+The distributed system architecture achieves its flexibility by
+encouraging (or enforcing) the definition of specific component
+interfaces. The interface of a component specifies to other components
+what services are offered by that component and how they are used. As
+long as the interface of a component remains constant, that
+component's implementation can change dramatically without affecting
+other components.
+
+
+
+All software components (Post-Pro, Geometry, Mesh...) integrated into
+\b SALOME platform implement predefined interfaces. Each component
+provides data for the \b SALOME study in a form of links (stored in
+the Study) to the specific data created and stored in the
+component. All components represent \b CORBA servers and it allows to
+run them on different host stations.
+
+\image html image67.gif
+
+
+It is equally possible to create engine-independent modules. These
+modules may not use CORBA at all, and can have internal data structure
+which can be written in pure C++ (or python). Such modules are located
+inside SALOME GUI process and from the point of view of the end user
+have no difference with standard components. Such modules not using
+the standard tools of SALOME platform are defined on a special
+separated level named CAM. CAM component is the basis for new SALOME
+GUI and contains all basic functionality for working with modules
+(loading; saving, closing, customization of toolbar and menu).
+
+
+
+Another fundamental piece of the \b SALOME architecture is the use of
+the Interface Definition Language (IDL). IDL, which specifies
+interfaces between CORBA components, is instrumental in ensuring
+CORBA's language independence. Because interfaces described in IDL can
+be mapped to any programming language, CORBA applications and
+components are thus independent of the language(s) used to implement
+them.
+
+
+Additional information about CORBA technology
+is available at http://www.omg.org
+
+\note In \b SALOME there is a possibility to run
+definite components in the so-called \ref batch_mode_run "batch mode" without GUI provided
+by GUI component. In this case you can work with these components with
+the help of Python commands and scripts.
+
+
+The architecture of this all-inclusive
+platform for numerical components responds to the following
+objectives:
+<ol>
+<li>\b Flexibility : the creation and modification of computation
+schemes must be easy. The developer must have easy access to all
+modeling parameters to create domain-specific tools adapted to new
+situations or to test new numerical algorithms. SALOME allows
+integration and implementation of numerical and physical components
+derived from existing code.</li>
+<li>\b Productivity : the implementation of code is simple for the
+user and the reuse of components (within other environments for
+macro-components) is noticeably facilitated.</li>
+<li> \b Performance :\b SALOME is able to more finely simulate
+phenomena that is more complex in scale and in physical coupling
+requirements. \b SALOME economically exploits the performance of used
+machines (massively parallel processors, PC clusters, etc).</li>
+<li> \b Expandability: on the one hand, software technologies and
+physical architectures evolve rapidly compared to the development
+time, validation and use of a scientific application while on the
+other hand, the development of a database model adapted to the
+totality of exchanges between components can be achieved
+incrementally. \b SALOME is able to easily follow these
+developments.</li>
+</ol>
+
+*/
\ No newline at end of file
--- /dev/null
+/*!
+
+\page salome_desktop_page SALOME desktop
+
+The main SALOME Desktop consists of the following sections and
+toolbars:
+
+\image html geomview-alt.png
+
+<b>Basic parts of the SALOME Desktop:</b>
+<ul>
+<li><b>Main menu</b> - This is a set of context-sensitive menus, which will
+be updated according the functionality of the loaded component. In
+general, these menus contain all functional options of SALOME
+platform.</li>
+<li><b>Standard Toolbar</b> - This toolbar contains icons allowing
+creating/saving studies, correcting mistakes, copying/pasting
+objects.</li>
+<li><b>Components Toolbar</b> - This toolbar is destined for uploading
+components in SALOME platform.</li>
+<li><b>Module Toolbar</b> - This toolbar contains icons specific to the
+loaded module.</li>
+<li><b>Viewer Toolbar</b> - This is a set of tools destined for visualization
+of the presentations in the viewer.</li>
+</ul>
+
+ All toolbars in the
+\b SALOME Platform are context-sensitive. Loading of a definite component
+(Geometry, Post-Pro, Mesh etc.) will automatically add some additional
+toolbars specific to this component. To display/hide a definite
+toolbar, in the main menu choose <b>View > Toolbars</b>, and from this
+submenu check or uncheck the toolbar, you would like to display/hide.
+
+ By default all
+toolbars are located on the top of the SALOME desktop. But you can
+relocate toolbars by dragging with the mouse and dropping it in any
+place of the window.
+
+<b>Parts of the study window:</b>
+<ul>
+<li><b>Object Browser</b> - Management of objects created or imported into
+SALOME application.</li>
+<li>\b Viewer - This window is destined for visualization of
+presentations.</li>
+<li><b>Python console</b> - Window for Python interpreter. This window
+functions like a standard document: the pop-up menu invoked by
+right-click in this window gives access to
+<b>Copy/Paste/SelectAll/ClearAll</b> options.</li>
+</ul>
+
+ Object Browser, Python
+Console, MenuBar, etc are, in fact, separate dockable windows.
+Dockable windows can be placed in special areas, on the borders of
+desktop like toolbars. You can change the size and the position of
+dockable windows, hide them or even place outside desktop. SALOME
+saves in the same file all positions and sizes of dockable windows. It
+means that the difference in settings of the same windows (for example
+Python console) is possible between different modules (the same window
+can have different size and position when other module is
+activated). Also each module can indicate which common windows are
+necessary for working, and only they will be displayed when this
+module is active.
+
+ Starting from the
+version 3.0.0 Salome uses a <b>Multi-Desktop Approach</b>. Multi-desktop
+Approach means that now there is separate Desktop for each document
+(Study) and all windows connected to a Study (viewers, dockable
+windows etc) are placed in one container. It is very comfortable,
+because you can't mix up windows from different studies. This approach
+positively differs from the classic multi document interface in case
+if many windows are used, i.e. when one document contains a lot of
+viewers, dialogs, etc. Each desktop also has its own menu and toolbar.
+
+*/
\ No newline at end of file
--- /dev/null
+/*!
+
+\page salome_preferences_page SALOME preferences
+
+To begin setting preferences for your study, select \b Preferences in the
+main menu, the following dialog box will appear:
+
+\image html pref11.png
+If you've just started your study and haven't yet loaded other
+modules, you'll be able to change only those settings, which refer to
+the whole GUI SALOME session. These settings will be valid for the
+whole study session.
+
+<h2>General Preferences</h2>
+
+<ul>
+<li><b>Study Properties</b></li>
+<ul>
+<li><b>MultiFile Save</b> - if checked in, your study will be saved in
+several HDF files (one file for the data created by each component
+used during the study session).</li>
+<li><b>ASCII Save</b> - if checked in, your study will be saved in
+ASCII format file (or files).</li>
+<li><b>Store positions of windows</b> - if checked in, positions of windows
+will be saved in a special file at the end of the current session and
+then restored for a new session.</li>
+<li><b>Store/restore last GUI state</b> - if checked in, all GUI settings are
+saved with the rest of the data whenever you save the study. When the
+study is reopened, the GUI state is restored.</li>
+</ul>
+<li><b>External browser</b></li>
+<ul>
+<li>\b Application - this option allows you to set an external browser (IE,
+Netscape) which will be used for viewing SALOME reference manuals. By
+default, Mozilla is used. Press the "<b>...</b>" button(see
+the picture below) to browse for the application you need in the data
+tree of your computer.</li>
+<li>\b Parameters</li>
+</ul>
+<li><b>Python console properties</b> - here you can quickly set the
+parameters (style, size, face) of the font used in your Python
+console.</li>
+</ul>
+\par
+For detailed settings in \ref select_color_and_font_page "Select Font"
+dialog box press the "<b>...</b>" button(see the picture below).
+
+\image html image69.gif ""..." button"
+
+<br><h2>Viewers Preferences</h2>
+
+\image html pref12.png
+
+<ul>
+<li><b>OCC and VTK 3D Viewers</b></li>
+<ul>
+<li><b>Trihedron size</b> - this submenu allows to set the size of
+coordinate axes displayed in the viewer.</li>
+<li><b>Background Color</b> - this submenu allows to select background
+color. Click on the colored line to access to the
+\ref select_color_and_font_page "Select Color" dialog box.</li>
+<li><b>Number of isolines along U</b> (or <b>V</b>) - this submenu allows to specify
+the number of isolines along the axes of coordinates.</li>
+<li><b>Relative size</b> - if checked in, trihedron axes scale to fit the
+size of the area displayed in 3D Viewer.</li>
+</ul>
+<br>
+<li><b>Plot2d Viewer</b></li>
+<ul>
+<li><b>Legend Position</b> - this submenu allows to set the default position
+of the legend, it can be located to the left, to the right, on top or
+on bottom of the graph.</li>
+<li><b>Curve Type</b> - this allows to set the representation of graphs in
+your presentations. You can see only <b>Points</b>, points connected with
+<b>Lines</b> or points connected with smooth <b>Splines</b>.</li>
+<li><b>Marker Size</b> - this submenu allows you to set the size of
+markers in your graphs</li>
+<li><b>Horizontal & Vertical Axis Scale</b> - this submenu allows you to set
+the scale for vertical and horizontal axes. It can be either <b>Linear</b> or
+<b>Logarithmic</b></li>
+<li>Background Color - this submenu allows to select the background
+color. Click on the colored line to access to the
+\ref select_color_and_font_page "Select Color" dialog box.</li>
+</ul>
+<br>
+<li><b>Graph Supervisor</b></li>
+<ul>
+<li><b>Background Color</b> - this submenu allows to select background
+color. Click on the colored line to access to the
+\ref select_color_and_font_page "Select Color" dialog box.</li>
+<li><b>Title Color</b> - this submenu allows to select title color. Click on
+the colored line to access to the
+\ref select_color_and_font_page "Select Color" dialog box.</li>
+</ul>
+</ul>
+
+<br><h2>Directories Preferences</h2>
+
+\image html pref13.png
+
+<ul>
+<li>
+<b>Quick Directory List</b> - this section allows to create and manage
+a custom quick directory list. To add a directory in the list, press
+the "Add directory" button:
+\image html image70.gif
+
+then the "<b>...</b>" button and browse the data tree for the
+directory you need.
+The "Up" and "Down" buttons(see the picture below) help you to sort
+the directories in the list:
+\image html image73.gif
+
+\image html image75.gif
+To remove the selected directory from the list, press the "Delete"
+button:
+\image html image72.gif
+</li>
+</ul>
+
+<br><h2>Object Browser Preferences</h2>
+
+\image html pref14.png
+
+<ul>
+<li><b>Object browser settings</b></li>
+<ul>
+<li><b>Auto size for the first column</b> - this checkbox enables automatic
+resizing for the first column.</li>
+<li><b>Auto size for other columns</b> - this checkbox enables
+automatic resizing for the other columns.</li>
+<li><b>Resize columns after expanding an item</b> - this checkbox enables
+resizing columns on expanding an object browser item.</li>
+</ul>
+</ul>
+
+<ul>
+<li><b>Default columns</b> - these checkboxes allow to display or hide <b>Value</b>,
+<b>Entry</b>, <b>IOR</b> and <b>Reference entry</b> columns in the Object Browser.</li>
+</ul>
+
+*/
\ No newline at end of file
--- /dev/null
+/*!
+
+\page saving_and_closing_studies_page Saving and closing studies
+
+In \b SALOME a study can be saved in \b HDF binary (by default) or \b ASCII
+files (see also: \ref salome_preferences_page "Setting ASCII save option").
+
+You can also specify two options of saving your study:
+<ul>
+<li><b>In one HDF file:</b> in this case all components used during this
+study session will write their data into one common HDF file.
+</li>
+<li>
+<b>In multiple files</b> (see also: \ref salome_preferences_page
+"Setting Multifile save option") : in this
+case SALOME will create one base HDF file which will store the main
+information about the saved study and several other special files with
+particular extensions storing the data written by each component which
+has been used during this study session. Opening of this study
+requires that \b ALL saved files should be stored in the \b SAME directory.
+If you would like to copy your saved study in another directory or
+machine, you should copy all stored files. Otherwise, if you try to
+open this study, some data will be lost and it will lead to invalid
+functioning of the SALOME platform.
+</li>
+</ul>
+
+Saving a study you also save its layout, i.e. all positions and sizes
+of dockable windows. It means that the difference in settings of the
+same windows (for example Python console) is possible between
+different modules (the same window can have different size and
+position when other module is activated). Also each module can
+indicate which common windows are necessary for working, and only they
+will be displayed when this module is active.
+
+<em>To save an existing study:</em>
+\par
+In the main toolbar click "Save document" button or from the main menu
+select <b>File > Save</b> option. Your study will be automatically
+updated.
+
+\image html save.jpg ""Save document" button"
+
+\note If your study hasn't been previously saved, this option will
+call the standard Search File dialog box where you can enter the name
+for your study and save it.
+
+<em>To save a study with a new name:</em>
+\par
+From the main menu select <b>File > Save as</b> option. In the standard
+Search File dialog box enter a new name for your study and click \b Save
+button.
+
+<em>To save the current layout of the GUI:</em>
+\par
+From the main menu select <b>File > Save VISU State</b>. The current
+state of the graphic interface is published in Object Browser in the
+folder GUI states and can be at any time \b Restored, \b Renamed or \b
+Deleted. This operation saves and allows to
+restore almost all GUI settings: names, position, zooming and panning
+of viewers and all displayed objects (in Post-Pro module only).
+
+<em>To close a study:</em>
+\par
+In the main toolbar click "Close document" button or from the main menu select <b>File > Close</b>
+option or click on the cross in the upper right corner of the study
+window.
+
+\image html image94.gif ""Close document" button"
+
+\note If your study hasn't been previously saved, this option will
+call the following dialog box with several options:
+
+\image html closestudy.png
+
+\n\b Unload option allows to unload your current study from the SALOME
+Desktop. In the same working session you can reload it again (see:
+\ref opening_studies_page "Opening studies"). But if you quit the SALOME application, all changes
+in the unloaded study will be lost.
+
+*/
--- /dev/null
+/*!
+
+\page select_color_and_font_page Select Color and Font
+
+<b>Select Color</b> and <b>Select Font</b> menus are used in many
+Preferences.
+
+<br><h2>Select color</h2>
+
+\image html selectcolor.png
+
+This menu allows to choose from either predefined <b>Basic Colors</b>
+grouped in the upper left corner of the window or <b>Custom Colors</b>, which
+you can define yourselves. To define a Custom Color, click on one of
+the Custom Color cells, select the color you need in the field of
+colors or by typing in its numeric parameters in the lower right
+corner of the window, then click <b>Add to Custom Colors</b> button. The
+chosen color will be added to <b>Custom Colors</b> table.
+
+<br><h2>Select font</h2>
+
+\image html selectfont.png
+
+This menu provides a wide choice of \b Fonts, <b>Font Styles</b> and
+\b Sizes. Characters can be underlined or struck out. It is possible to
+preview them in the \b Sample window. \b Script dialog-box gives the
+possibility to use not only Latin and Latin Extended but also
+Cyrillic, Greek, Arabic, Runic and many other subsets.
+
+*/
\ No newline at end of file
--- /dev/null
+/*!
+
+\page setting_preferences_subpage Setting Preferences
+
+In \b SALOME you can set preferences for each module in the common editor
+of preferences. SALOME preferences refer to the whole GUI SALOME
+session, other preferences are module-specific and are accessible only
+after you load a respective module.
+\n When you change settings (click \b OK or \b Apply button) each module
+receives the notification about what preferences are changed. You can
+also click \b Defaults button to restore default preferences or \b Close
+button to quit the menu without any changes.
+\n \b Import button allows to load a user file containing preferences
+from your home directory through a standard Import dialog box.
+
+\image html import.png
+
+This file has no extension and by default starts with
+.SalomeApprc. followed by Salome version number. There exists one file
+for each Salome version in use.
+\n The preferences, set during the current study session, are
+automatically saved in this file at the end of the session. Next time
+you launch SALOME application, these preferences will be restored.
+
+\note The preferences you set will be default preferences for all \b new
+objects, but they are not retroactive and do not automatically apply
+to the existing objects.
+
+*/
\ No newline at end of file
--- /dev/null
+/*!
+
+\page setting_preferences_page Setting Preferences
+
+<ul>
+<li>\subpage setting_preferences_subpage</li>
+<li>\subpage select_color_and_font_page</li>
+<li>\subpage salome_preferences_page</li>
+<li>\subpage geometry_preferences_page</li>
+<li>\subpage mesh_preferences_page</li>
+<li>\subpage postpro_preferences_page</li>
+</ul>
+
+*/
\ No newline at end of file
--- /dev/null
+/*!
+
+\page setting_study_properties_page Setting study properties
+
+<em>To view the properties of the current study:</em>
+\par
+From the main menu select \b File > \b Properties option. The following
+dialog box will appear:
+
+\image html studyproperties.png
+
+This dialog box gives complete information about your study.
+
+<em>To change the name of the study author:</em>
+\par
+In this dialog box click on the \b Author field and enter a new name.
+
+<em>To view the list of changes made with your study:</em>
+\par
+In this dialog box click on the \b Modifications field and scroll it
+down. Each record contains the following information: date and time of
+modification of the study, name of the user, who has made these
+changes.
+
+<em>To lock your study for modifications:</em>
+\par
+In the dialog box shown on the picture above click on the \b Locked
+field and choose \b Yes item.
+
+In this case your study will be locked for any kind of modifications
+for all users. Next time you try to edit it, you will see the
+following warning message:
+
+\image html lockedstudy.png
+
+*/
\ No newline at end of file
--- /dev/null
+/*!
+
+\page study_management_page Study management
+
+<ul>
+<li>\subpage creating_new_study_page</li>
+<li>\subpage opening_studies_page</li>
+<li>\subpage saving_and_closing_studies_page</li>
+<li>\subpage editing_studies_page</li>
+<li>\subpage displaying_studies_page</li>
+<li>\subpage working_with_python_scripts_page</li>
+<li>\subpage setting_study_properties_page</li>
+</ul>
+
+*/
\ No newline at end of file
--- /dev/null
+/*!
+
+\page using_catalog_generator_page Using Catalog Generator (for advanced users)
+
+SALOME platform is an open platform for
+integration of your custom components, which can used in the same way
+as typical modules provided in the standard installed package. The
+<b>Catalog Generator</b> tool serves for implementation of the interface of
+your custom component. It allows to generate from IDL description of
+your component interface its xml description. The component xml
+description allows SALOME application to know about the component and
+its services and provides the possibility to call the component
+services, for example, inside Supervisor module.
+
+If you have a look at runSalome,
+runSalomeWithPort scripts running SALOME application, which are stored
+in build/bin directory you will see that SALOME_ModuleCatalog_Server
+is started with two xml files as its input parameters:
+\b CatalogModuleGeneral.xml and \b CatalogModulePersonnel.xml. These two
+files store the descriptions of interfaces and services of all
+components, provided with typical SALOME package. To add a new
+component into SALOME platform you should either update one of these
+existing xml files with generated xml description of your component or
+create a new one.
+
+<em>To open the Catalog Generator:</em>
+\par
+From the main menu choose <b>Tools > Catalog Generator</b>, the following
+dialog box will appear:
+
+\image html cataloggenerator.png
+
+<br>In this dialog box you can specify:
+<ul>
+<li>Name and location of the IDL file describing the interface of your
+component (Click the \b Browse button to find it using the data tree).</li>
+<li>Name and location of an existing XML file, which will be updated
+with the interface of you component or name and desired location of a
+new XML file, which will be generated (Click the \b Browse button to find
+it using the data tree).</li>
+<li>Name of the author.</li>
+<li>Name of the component.</li>
+<li>Name of the user.</li>
+<li>Version.</li>
+<li>Capability of multi study support.</li>
+<li>Type of the component.</li>
+<li>Icon of your component (Click the \b Browse button to find it using
+the data tree).</li>
+</ul>
+
+\note If you have chosen to create a new xml file containing the
+description of your component, don't forget to specify it as
+input parameter for SALOME_ModuleCatalog_Server in the file, you are
+using as a running script of SALOME platform (in runSalomeWithPort,
+for example).
+
+When launching SALOME next time you will see your module alongside other components.
+
+\b Tip: You can use the <b>Catalog Generator</b> tool, if you would like to \b
+test the functionality of your new component. After implementation of
+your component interface, launch SUPERVISION module where you can try
+using the services of your new component. (see also: Adding factory
+nodes)
+
+*/
\ No newline at end of file
--- /dev/null
+/*!
+
+\page using_find_tool_page Using Find toolbox
+
+The <b>Object Browser</b> is supplied with the \b Find toolbox. This tool
+allows performing context search of the items in the Object Browser:
+
+\image html findtool1.png
+
+The \b Find toolbox can be invoked in several ways:
+- Pressing \a <Ctrl>-<F> key combination starts new
+search; the text previously entered by the user in the edit control of
+the \b Find toolbox is automatically selected.
+- Pressing \a </> (slash) key starts new search; the text
+previously entered by the user is cleared.
+- Pressing \a <F3> key repeats previous search in the forward
+direction (from top to bottom).
+- Pressing \a <Shift>-<F3> key repeats previous search in
+the backward direction (from bottom to top).
+- Activating \a Find command from the Object Browser context popup
+menu starts new search (the same as \a <Ctrl>-<F>).
+
+Pressing \a <Escape> key closes the \b Find toolbox.
+
+The search is always started beginning from the first selected item in
+the Object Browser. If there are no selected items, the search is
+started from the top of the Object Browser contents. If there is an
+item which satisfies the search conditions, it is selected and
+Object Browser is expanded to show this item (if it is collapsed).
+
+The \b Find toolbox provides a set of widgets which are used to
+perform the search operations or affect on the search conditions:
+- \a "Close" button closes the \b Find toolbox.
+- Line edit box is used to enter the text to be searched. Note that
+search is alwasy done by the object name, i.e. by the data displayed
+in the "Name" column of the Object Browser.
+- \a "Find first item" button searches the very first item
+which satisfies the search condition.
+- \a "Find previous item" button searches the previous item
+which satisfies the search condition.
+- \a "Find next item" button searches the next item
+which satisfies the search condition.
+- \a "Find last item" button searches the very last item
+which satisfies the search condition.
+- \a "Case sensitive" check box allows performing case sensitive
+search.
+- \a "Regular Expression" check box allow performing the search of the
+items by the regular expression, for example:
+ - <i>Face</i> - matches all faces
+ - <i>Face_[\\d]</i> - matches Face_1, Face_2, etc.. (all faces)
+ - <i>Face_[\\d]$</i> - matches Face_1, Face_2, but not matches Face_11, Face_12.
+ - <i>^Face_[\\d]$</i> - same as above
+ - <i>^ Face_[\\d]$</i> - matches nothing
+
+- \a "Wrap search" check box: when it is switched on and search
+reaches last item, satisfying the search conditions, pressing \a "Find
+Next" button moves the selection to the very first item which matches
+search conditions (i.e. cyclic search is performed).
+
+If there are no items in the Object Browser which satisfy the search
+conditions, the edit control of the \b Find toolbox becomes
+red-colored:
+
+\image html findtool2.png
+
+The \b Find toolbox has also auto-hiding feature. This works as
+follows:
+- If input focus is inside the \b Find toolbox, auto-hiding is
+automatically deactivated.
+- If input focus moves outside the \b Find toolbox, it hides
+automatically in 10 seconds after the last search operation (which can
+be done by clicking \a "Find Next", \a "Find Previous" button, or typing
+something in the edit field); it means that each new search operation
+restarts the auto-hide timer.
+
+*/
--- /dev/null
+/*!
+
+\page using_object_browser_page Using Object Browser
+
+The <b>Object Browser</b> in SALOME is destined for displaying the
+structure of the current study in a tree-like form. It contains:
+
+<ul>
+<li>components, loaded during the current session</li>
+<li>objects created with the help of different components (The objects
+created with the help of a definite component are located in the
+folder having the name of this component)
+</li>
+<li>references to different objects (they are highlighted in red)</li>
+</ul>
+
+\image html objectbrowser1.png
+
+\note The <b>Object Browser</b> is destined to getting quick access to
+different objects created during SALOME session. All pop-up menus
+associated with the objects displayed in the Object Browser are
+context-sensitive. So it depends on a definite currently loaded SALOME
+component what options you will see in the pop-up menu, if you
+right-click on a definite object in the Object Browser.
+
+The Object Browser may contain supplementary attributes of the objects
+displayed in additional columns. By default, these columns are not
+displayed - displaying/hiding these columns is possible through
+\ref salome_preferences_page "setting study preferences" or
+right-clicking on the attributes bar and toggling the necessary
+attributes.
+
+\image html objectbrowser2.png
+
+<ul>
+<li>\b Entry - Identification index of the object in the structure of
+the study</li>
+<li>\b IOR - Interoperable Object Reference</li>
+<li><b>Reference entry</b> - Identification index of the references
+to the objects</li>
+<li>\b Value - Displays the value of the first object attribute</li>
+</ul>
+
+\note <b>Entry, IOR and Reference entry</b> attributes are displayed for debugging purposes only.
+
+*/
\ No newline at end of file
--- /dev/null
+/*!
+
+\page using_registry_tool_page Using Registry tool
+
+\b Registry tool is in the SALOME platform is destined for providing
+information about the processes (components), which have ever been
+launched in the current study session.
+
+<em>To view the Registry:</em>
+\par
+From the main menu choose <b>Tools > Registry display</b>, the
+following dialog box will appear:
+
+\image html registry1.png
+
+\b Running tab of this dialog box displays a list of the currently
+started processes (components) with supplementary information on each
+of them divided into columns:
+
+<ul>
+<li>\b Component: name of the started component
+<li>\b PID: process identification number
+<li>\b User \b Name: name of the user launching the component
+<li>\b Machine: name of the machine, on which the process has been started
+<li>\b begins: date and time of the starting of the component
+<li>\b hello: date and time of the last call to the component
+</ul>
+
+\b History tab displays a list of all processes, which have ever been
+launched within this study session. It contains the same supplementary
+information on each of the processes (components).
+
+\b Refresh button allows to refresh the current list of processes
+(components).
+
+\b Interval button allows to set an interval for refreshment of the
+current list of processes (components).
+
+\image html registry3.png
+
+<em>To display complete information on a definite process
+(component):</em>
+\par
+Double-click on this process (component). The following window will
+appear:
+
+\image html registry4.png
+
+*/
\ No newline at end of file
--- /dev/null
+/*!
+
+\page viewers_page Viewers
+
+<ul>
+<li>\subpage occ_3d_viewer_page</li>
+<li>\subpage vtk_3d_viewer_page</li>
+<li>\subpage plot2d_viewer_page</li>
+</ul>
+
+*/
--- /dev/null
+/*!
+
+\page vtk_3d_viewer_page VTK 3D Viewer
+
+<b>VTK 3D viewer</b> is the default viewer for Mesh Module, allowing to
+visualize meshes. It is also used in Post-Pro module for all 3D
+presentations except for Gauss Points.
+
+The functionalities of VTK viewer are available via its Viewer
+Toolbar. Buttons marked with small downward triangles have extended
+functionality which can be accessed by locking on them with left mouse
+button.
+
+\image html image157.gif "Viewer Toolbar"
+
+<hr>
+\image html image77.gif
+\n <center><b>Dump View</b> - exports an object from the viewer in bmp, png, jpg
+or jpeg image format.</center>
+<hr>
+
+\image html image88.gif
+\n <center><b>Show/Hide Trihedron</b> - shows or hides coordinate axes.</center>
+<hr>
+
+\image html image96.gif
+\n <center><b>Fit all</b> - scales the presentation so that it could
+fit within the Viewer boundaries. </center>
+<hr>
+
+\image html image97.gif
+\n <center><b>Fit area</b> - resizes the view to place in the visible area
+only the contents of a frame drawn with pressed left mouse button.</center>
+<hr>
+
+\image html image98.gif
+\n <center><b>Zoom</b> - allows to zoom in and out.</center>
+<hr>
+
+\image html image99.gif
+\n <center><b>Panning</b> - if the represented objects are greater that the
+visible area and you don't wish to use <b>Fit all</b> functionality, click on
+this button and you'll be able to drag the scene to see its remote
+parts.</center>
+<hr>
+
+\image html image100.gif
+\n <center><b>Global panning</b> - allows to select a point to be the
+center of the presentation showing all displayeed objects in the
+visible ares <center>
+<hr>
+
+\image html view_rotation_point.png
+\n <center><b>Change rotation point</b> - allows to to choose the point around
+which the rotation is performed.</center>
+
+\image html set_rotation_point_dialog1.png
+
+<center>By default the rotation point is located in the Center of the bounding
+box of an object.</center>
+
+\image html set_rotation_point_dialog2.png
+
+<center>Unchecking <b>Use Bounding Box Center</b> checkbox allows you to
+define the coordinates of the rotation point manually.</center>
+
+<b>Set to Origin</b> button restores the default rotation point
+coordinates.\n
+<b>Select Point from View</b> button allows to select the rotation
+point in the 3D Viewer.
+<hr>
+
+\image html image89.gif
+\n <center><b>Rotation</b> - allows to rotate the selected object using the
+mouse.</center>
+
+\image html image102.gif
+
+<center>These buttons orientate the scene strictly about coordinate axes.</center>
+<hr>
+
+\image html image91.gif
+\n <center><b>Reset</b> - restores the default position (isometric) of
+objects in the scene.</center>
+<hr>
+
+\image html urbutton.png
+\n <center><b>Update Rate</b> - allows to define the Update Rate for
+the presentations displayed in the viewer</center>
+
+\image html updaterate.png
+
+<ul>
+<li><b>Desired Update Rate, FPS</b> - allows to set the target Update
+Rate</li>
+<li><b>Still Update Rate, FPS</b> - allows to set the Update Rate for
+the periods when both the user and the application do not perform any
+actions in the viewer</li>
+<li><b>Current Update Rate, FPS</b> - shows the Update Rate currently
+available on your configuration</li>
+<li><b>Number of Cells</b> - shows the number of cells currently in
+display</li>
+</ul>
+
+\image html image108.gif
+\n <center><b>Scaling</b> - represents objects deformed (stretched or
+stuffed) along the axes of coordinates.</center>
+<hr>
+
+\image html image109.gif
+\n <center><b>Graduated axes</b> - allows to define parameters of axes
+and graduate them.</center>
+
+\image html graduatedaxes1.png
+
+<ul>
+<li><b>Axis name</b></li>
+<ul>
+<li><b>Is visible</b> - if checked the axis name is displayed in the
+viewer.</li>
+<li><b>Name</b> - allows to redefine the name of the axis.</li>
+<li><b>Font</b> - allows to define color and properties of the font of
+axis name.</li>
+</ul>
+<li><b>Labels</b></li>
+<ul>
+<li><b>Is visible</b> - if checked the labels are displayed in the
+viewer.</li>
+<li><b>Number</b> - allows to define the number of labels.</li>
+<li><b>Offset</b> - allows to define the distance between labels.</li>
+<li><b>Font</b> - allows to define color and properties of the font of
+labels names.</li>
+</ul>
+<li><b>Tick marks</b></li>
+<ul>
+<li><b>Is visible</b> - if checked the tick marks are displayed in the
+viewer.</li>
+<li><b>Length</b> - allows to define the length of tick marks.</li>
+</ul>
+<li><b>Is visible</b> - if checked the axis is displayed in the
+viewer. </li>
+</ul>
+
+*/
\ No newline at end of file
--- /dev/null
+/*!
+
+\page working_with_python_scripts_page Working with Python Scripts
+
+\b SALOME Platform can be launched in the batch mode, without Graphical
+User Interface, and operated with the use of Python scripts, which can
+fulfill most of the necessary tasks, however, the process of scripting
+is quite time consuming and rather error-prone.
+\n This problem has been resolved by the possibility to automatically
+generate a set of Python scripts from data created with SALOME GUI,
+which greatly increases the productivity of using SALOME platform in
+the batch mode. This mechanism can convert a SALOME Study in one or
+several Python scripts, which can be stored and imported later to
+re-create the content of the original study. The first script is a
+SALOME document, which re-creates the SALOME Study, adds the
+stored Salome components to the SALOME and automatically calls
+Python scripts of the second type containing component specific Python
+function calls. This architecture gives great flexibility in manual
+modification of the generated scripts because you can modify only one
+of the component specific Python scripts without touching others, thus
+avoiding expert knowledge of Python API of unused components.
+
+To Dump a SALOME Study in one or several scripts, in the main menu
+select \b File --> <b>Dump study</b>
+\n The following dialog box allowing to browse for the location and
+define the name for a Python file will appear:
+
+\image html dumpstudy.png
+
+\par
+<ul>
+<li>
+<b>Publish in study</b> - if checked in, the component objects created by
+Python commands will be published in the created Study when the script
+is played, otherwise the objects will not be published in the Study.
+</li>
+<li>
+<b>Save GUI state</b> - if checked in, the current application layout will be
+saved in the Python file.
+</li>
+</ul>
+To confirm your choice click \b Save.
+
+Reversibly it is possible to load a saved Python Script selecting in
+the main menu \b File -> <b>Load Script</b>.
+
+\image html loadscript.png
+
+\par
+To confirm your choice click \b Open.
+
+*/
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+</head>
+<body>
+<hr style="width: 100%; height: 2px;">
+<div style="text-align: center;">Copyright © 2003-2007 CEA, EDF<br>
+</div>
+</body>
+</html>
--- /dev/null
+<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+ <title>$title</title>
+ <link href="doxygen.css" rel="stylesheet" type="text/css">
+</head>
+<hr>
+<center>
+SALOME documentation central
+</center>
+<hr>
+++ /dev/null
-# Doxyfile 1.4.6
-
-#---------------------------------------------------------------------------
-# Project related configuration options
-#---------------------------------------------------------------------------
-PROJECT_NAME = "SALOME - GUI - v.@VERSION@"
-PROJECT_NUMBER =
-OUTPUT_DIRECTORY = ../
-CREATE_SUBDIRS = NO
-OUTPUT_LANGUAGE = English
-USE_WINDOWS_ENCODING = NO
-BRIEF_MEMBER_DESC = YES
-REPEAT_BRIEF = NO
-ABBREVIATE_BRIEF =
-ALWAYS_DETAILED_SEC = YES
-INLINE_INHERITED_MEMB = YES
-FULL_PATH_NAMES = YES
-STRIP_FROM_PATH = ../../../share/salome \
- ../../../build/salome
-STRIP_FROM_INC_PATH =
-SHORT_NAMES = NO
-JAVADOC_AUTOBRIEF = YES
-MULTILINE_CPP_IS_BRIEF = NO
-DETAILS_AT_TOP = NO
-INHERIT_DOCS = NO
-SEPARATE_MEMBER_PAGES = NO
-TAB_SIZE = 5
-ALIASES =
-OPTIMIZE_OUTPUT_FOR_C = YES
-OPTIMIZE_OUTPUT_JAVA = YES
-BUILTIN_STL_SUPPORT = NO
-DISTRIBUTE_GROUP_DOC = NO
-SUBGROUPING = YES
-
-#---------------------------------------------------------------------------
-# Build related configuration options
-#---------------------------------------------------------------------------
-EXTRACT_ALL = YES
-EXTRACT_PRIVATE = YES
-EXTRACT_STATIC = YES
-EXTRACT_LOCAL_CLASSES = YES
-EXTRACT_LOCAL_METHODS = NO
-HIDE_UNDOC_MEMBERS = YES
-HIDE_UNDOC_CLASSES = YES
-HIDE_FRIEND_COMPOUNDS = NO
-HIDE_IN_BODY_DOCS = NO
-INTERNAL_DOCS = YES
-CASE_SENSE_NAMES = YES
-HIDE_SCOPE_NAMES = NO
-SHOW_INCLUDE_FILES = YES
-INLINE_INFO = YES
-SORT_MEMBER_DOCS = NO
-SORT_BRIEF_DOCS = NO
-SORT_BY_SCOPE_NAME = NO
-GENERATE_TODOLIST = YES
-GENERATE_TESTLIST = YES
-GENERATE_BUGLIST = YES
-GENERATE_DEPRECATEDLIST= YES
-ENABLED_SECTIONS =
-MAX_INITIALIZER_LINES = 25
-SHOW_USED_FILES = NO
-SHOW_DIRECTORIES = NO
-FILE_VERSION_FILTER =
-
-#---------------------------------------------------------------------------
-# configuration options related to warning and progress messages
-#---------------------------------------------------------------------------
-QUIET = NO
-WARNINGS = YES
-WARN_IF_UNDOCUMENTED = YES
-WARN_IF_DOC_ERROR = YES
-WARN_NO_PARAMDOC = NO
-WARN_FORMAT = "$file:$line: $text"
-WARN_LOGFILE = log.txt
-
-#---------------------------------------------------------------------------
-# configuration options related to the input files
-#---------------------------------------------------------------------------
-INPUT = ../../../share/salome/src \
- ../../../share/salome/bin \
- ../../../share/salome/idl \
- ../../../build/salome/bin
-FILE_PATTERNS = *.idl *.hxx *.cxx *.h *.c *.hh *.cc python_extension_must_be_here
-RECURSIVE = YES
-EXCLUDE =
-EXCLUDE_SYMLINKS = NO
-EXCLUDE_PATTERNS =
-EXAMPLE_PATH =
-EXAMPLE_PATTERNS =
-EXAMPLE_RECURSIVE = YES
-IMAGE_PATH = sources/
-INPUT_FILTER =
-FILTER_PATTERNS =
-FILTER_SOURCE_FILES = YES
-
-#---------------------------------------------------------------------------
-# configuration options related to source browsing
-#---------------------------------------------------------------------------
-SOURCE_BROWSER = NO
-INLINE_SOURCES = NO
-STRIP_CODE_COMMENTS = YES
-REFERENCED_BY_RELATION = NO
-REFERENCES_RELATION = YES
-USE_HTAGS = NO
-VERBATIM_HEADERS = YES
-
-#---------------------------------------------------------------------------
-# configuration options related to the alphabetical class index
-#---------------------------------------------------------------------------
-ALPHABETICAL_INDEX = YES
-COLS_IN_ALPHA_INDEX = 3
-IGNORE_PREFIX =
-
-#---------------------------------------------------------------------------
-# configuration options related to the HTML output
-#---------------------------------------------------------------------------
-GENERATE_HTML = YES
-HTML_OUTPUT = GUI
-HTML_FILE_EXTENSION = .html
-HTML_HEADER = sources/myheader.html
-HTML_FOOTER = sources/footer.html
-HTML_STYLESHEET = sources/doxygen.css
-HTML_ALIGN_MEMBERS = YES
-GENERATE_HTMLHELP = NO
-CHM_FILE =
-HHC_LOCATION =
-GENERATE_CHI = NO
-BINARY_TOC = YES
-TOC_EXPAND = YES
-DISABLE_INDEX = NO
-ENUM_VALUES_PER_LINE = 4
-GENERATE_TREEVIEW = NO
-TREEVIEW_WIDTH = 250
-
-#---------------------------------------------------------------------------
-# configuration options related to the LaTeX output
-#---------------------------------------------------------------------------
-GENERATE_LATEX = NO
-LATEX_OUTPUT = latex
-LATEX_CMD_NAME = latex
-MAKEINDEX_CMD_NAME = makeindex
-COMPACT_LATEX = NO
-PAPER_TYPE = a4wide
-EXTRA_PACKAGES =
-LATEX_HEADER =
-PDF_HYPERLINKS = NO
-USE_PDFLATEX = NO
-LATEX_BATCHMODE = NO
-LATEX_HIDE_INDICES = NO
-
-#---------------------------------------------------------------------------
-# configuration options related to the RTF output
-#---------------------------------------------------------------------------
-GENERATE_RTF = NO
-RTF_OUTPUT = rtf
-COMPACT_RTF = NO
-RTF_HYPERLINKS = NO
-RTF_STYLESHEET_FILE =
-RTF_EXTENSIONS_FILE =
-
-#---------------------------------------------------------------------------
-# configuration options related to the man page output
-#---------------------------------------------------------------------------
-GENERATE_MAN = NO
-MAN_OUTPUT = man
-MAN_EXTENSION = .3
-MAN_LINKS = NO
-
-#---------------------------------------------------------------------------
-# configuration options related to the XML output
-#---------------------------------------------------------------------------
-GENERATE_XML = NO
-XML_OUTPUT = xml
-XML_SCHEMA =
-XML_DTD =
-XML_PROGRAMLISTING = YES
-
-#---------------------------------------------------------------------------
-# configuration options for the AutoGen Definitions output
-#---------------------------------------------------------------------------
-GENERATE_AUTOGEN_DEF = NO
-
-#---------------------------------------------------------------------------
-# configuration options related to the Perl module output
-#---------------------------------------------------------------------------
-GENERATE_PERLMOD = NO
-PERLMOD_LATEX = NO
-PERLMOD_PRETTY = YES
-PERLMOD_MAKEVAR_PREFIX =
-
-#---------------------------------------------------------------------------
-# Configuration options related to the preprocessor
-#---------------------------------------------------------------------------
-ENABLE_PREPROCESSING = YES
-MACRO_EXPANSION = YES
-EXPAND_ONLY_PREDEF = NO
-SEARCH_INCLUDES = YES
-INCLUDE_PATH =
-INCLUDE_FILE_PATTERNS =
-PREDEFINED =
-EXPAND_AS_DEFINED =
-SKIP_FUNCTION_MACROS = NO
-
-#---------------------------------------------------------------------------
-# Configuration::additions related to external references
-#---------------------------------------------------------------------------
-TAGFILES =
-GENERATE_TAGFILE =
-ALLEXTERNALS = NO
-EXTERNAL_GROUPS = YES
-PERL_PATH = /usr/bin/perl
-
-#---------------------------------------------------------------------------
-# Configuration options related to the dot tool
-#---------------------------------------------------------------------------
-CLASS_DIAGRAMS = YES
-HIDE_UNDOC_RELATIONS = NO
-HAVE_DOT = YES
-CLASS_GRAPH = YES
-COLLABORATION_GRAPH = NO
-GROUP_GRAPHS = NO
-UML_LOOK = NO
-TEMPLATE_RELATIONS = YES
-INCLUDE_GRAPH = YES
-INCLUDED_BY_GRAPH = NO
-CALL_GRAPH = NO
-GRAPHICAL_HIERARCHY = YES
-DIRECTORY_GRAPH = YES
-DOT_IMAGE_FORMAT = jpg
-DOT_PATH =
-DOTFILE_DIRS =
-MAX_DOT_GRAPH_WIDTH = 1024
-MAX_DOT_GRAPH_HEIGHT = 1200
-MAX_DOT_GRAPH_DEPTH = 0
-DOT_TRANSPARENT = NO
-DOT_MULTI_TARGETS = NO
-GENERATE_LEGEND = NO
-DOT_CLEANUP = YES
-
-#---------------------------------------------------------------------------
-# Configuration::additions related to the search engine
-#---------------------------------------------------------------------------
-SEARCHENGINE = NO
+++ /dev/null
-H1 {
- text-align: center;
-}
-
-CAPTION {
- font-weight: bold
-}
-
-/* Link in the top navbar */
-A.qindex {}
-
-A.qindexRef {}
-
-/* Link to any cross-referenced Doxygen element */
-A.el {
- text-decoration: none;
- font-weight: bold
-}
-
-A.elRef {
- font-weight: bold
-}
-
-/* Link to any cross-referenced Doxygen element inside a code section
- (ex: header)
-*/
-A.code {
- text-decoration: none;
- font-weight: normal;
- color: #4444ee
-}
-
-A.codeRef {
- font-weight: normal;
- color: #4444ee
-}
-
-A:hover {
- text-decoration: none;
- background-color: lightblue
-}
-
-DL.el {
- margin-left: -1cm
-}
-
-/* A code fragment (ex: header) */
-DIV.fragment {
- width: 100%;
- border: none;
- background-color: #CCCCCC
-}
-
-/* In the alpha list (coumpound index), style of an alphabetical index letter */
-DIV.ah {
- background-color: #CCCCCC;
- font-weight: bold;
- color: #ffffff;
- margin-bottom: 3px;
- margin-top: 3px
-}
-
-/* Method name (+ type) */
-TD.md {
- background-color: lightblue;
- font-weight: bold;
-}
-
-/* Method parameter (some of them) */
-TD.mdname1 {
- background-color: lightblue;
- font-weight: bold; color: #602020;
-}
-
-/* Method parameter (some of them) */
-TD.mdname {
- background-color: lightblue;
- font-weight: bold;
- color: #602020;
- width: 600px;
-}
-
-/* Separator between methods group (usually empty, seems not supported by IE) */
-DIV.groupHeader {
- margin-left: 16px;
- margin-top: 12px;
- margin-bottom: 6px;
- font-weight: bold
-}
-
-DIV.groupText {
- margin-left: 16px;
- font-style: italic;
- font-size: smaller
-}
-
-BODY { background: #FFFFFF
-}
-
-/* BODY {
- background: url(sources/bg_salome.gif)
-} */
-
-div.tabs {
- text-align: justify;
- font-weight: bold;
- color: #FFFFFF;
-}
-
-DIV.div-footer {
- margin-left: 1em;
- margin-right: 1em;
- margin-bottom: 0.2em;
- text-align: right;
- font-size: 9pt;
-}
-
-/* In File List, Coumpound List, etc, 1st column of the index */
-TD.indexkey {
- background-color: #CCCCCC;
- font-weight: bold;
- padding-right : 10px;
- padding-top : 2px;
- padding-left : 10px;
- padding-bottom : 2px;
- margin-left : 0px;
- margin-right : 0px;
- margin-top : 2px;
- margin-bottom : 2px
-}
-
-/* In File List, Coumpound List, etc, 2nd column of the index */
-TD.indexvalue {
- background-color: #CCCCCC;
- font-style: italic;
- padding-right : 10px;
- padding-top : 2px;
- padding-left : 10px;
- padding-bottom : 2px;
- margin-left : 0px;
- margin-right : 0px;
- margin-top : 2px;
- margin-bottom : 2px
-}
-
-span.keyword { color: #008000 }
-span.keywordtype { color: #604020 }
-span.keywordflow { color: #e08000 }
-span.comment { color: #800000 }
-span.preprocessor { color: #806020 }
-span.stringliteral { color: #002080 }
-span.charliteral { color: #008080 }
+++ /dev/null
-</DIV>
-<DIV class="div-footer">
-Generated on $datetime for $projectname by <A href="http://www.doxygen.org/index.html"><img src="doxygen.png" alt="doxygen" align="middle" border="0"></A> $doxygenversion</DIV>
-</BODY>
-</HTML>
+++ /dev/null
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
- <meta name="GENERATOR" content="Mozilla/4.73 [en] (WinNT; I) [Netscape]">
- <title>Main Page</title>
-<link href="doxygen.css" rel="stylesheet" type="text/css">
-<link href="tabs.css" rel="stylesheet" type="text/css">
-</head>
-<body>
-
-</body>
-</html>
include $(top_srcdir)/adm_local/unix/make_common_starter.am
-EXTRA_DIST+=GUI
+EXTRA_DIST += images static
-dev_docs:
- cp -fr $(srcdir)/GUI ./INPUT; \
- cp -f ./GUI/doxyfile ./INPUT; \
- cd INPUT; \
- sed 's|../../../share/salome|$(top_srcdir)|' ./doxyfile > ./doxyfile1; \
- sed 's|../../build/salome|$(top_builddir)|' ./doxyfile1 > ./doxyfile2; \
- mv -f doxyfile2 doxyfile1; \
- echo "DOXYGEN SUPPORT PYTHON - @DOXYGEN_WITH_PYTHON@"; \
- if( test "x@DOXYGEN_WITH_PYTHON@" = "xyes"); then \
- sed 's|python_extension_must_be_here|*.py|' ./doxyfile1 > ./doxyfile2; \
- mv -f doxyfile2 doxyfile1; \
- $(DOXYGEN) -u ./doxyfile1; \
- else \
- sed 's|python_extension_must_be_here||' ./doxyfile1 > ./doxyfile2; \
- mv -f doxyfile2 doxyfile1; \
- fi; \
- if( test "x@DOXYGEN_WITH_STL@" = "xyes"); then \
- sed -e 's|BUILTIN_STL_SUPPORT = NO|BUILTIN_STL_SUPPORT = YES|' ./doxyfile1 > ./doxyfile2; \
- mv -f doxyfile2 doxyfile1; \
- fi; \
- mv -f doxyfile1 doxyfile; \
- echo "Running doxygen in directory:"`pwd`; \
- $(DOXYGEN) ./doxyfile; \
- cd ../; \
- cp -fr $(srcdir)/GUI/sources/ GUI/ ; \
- rm -fr INPUT
+dev_docs: doxyfile
+ echo "Running doxygen in directory: "`pwd`; \
+ $(DOXYGEN) $<;
-doctuidir=$(docdir)/tui/GUI
+clean-local:
+ -rm -fr GUI doxygen.bak
-nodist_doctui_DATA= GUI/doxyfile
-EXTRA_DIST+= GUI/doxyfile.in
+install-data-local:
+ if test -d GUI; then \
+ $(INSTALL) -d $(DESTDIR)$(docdir)/tui ; \
+ cp -rp GUI $(DESTDIR)$(docdir)/tui ; \
+ fi;
+
+uninstall-local:
+ rm -rf $(docdir)/tui
--- /dev/null
+# Doxyfile 1.4.6
+
+#---------------------------------------------------------------------------
+# Project related configuration options
+#---------------------------------------------------------------------------
+PROJECT_NAME = "GUI Module Programming Guide v.@VERSION@"
+PROJECT_NUMBER =
+OUTPUT_DIRECTORY = GUI
+CREATE_SUBDIRS = NO
+OUTPUT_LANGUAGE = English
+USE_WINDOWS_ENCODING = NO
+BRIEF_MEMBER_DESC = YES
+REPEAT_BRIEF = NO
+ABBREVIATE_BRIEF =
+ALWAYS_DETAILED_SEC = YES
+INLINE_INHERITED_MEMB = YES
+FULL_PATH_NAMES = YES
+STRIP_FROM_PATH = @top_srcdir@ @top_builddir@
+STRIP_FROM_INC_PATH =
+SHORT_NAMES = NO
+JAVADOC_AUTOBRIEF = YES
+MULTILINE_CPP_IS_BRIEF = NO
+DETAILS_AT_TOP = NO
+INHERIT_DOCS = NO
+SEPARATE_MEMBER_PAGES = NO
+TAB_SIZE = 5
+ALIASES =
+OPTIMIZE_OUTPUT_FOR_C = YES
+OPTIMIZE_OUTPUT_JAVA = YES
+BUILTIN_STL_SUPPORT = @DOXYGEN_SUPPORT_STL@
+DISTRIBUTE_GROUP_DOC = NO
+SUBGROUPING = YES
+
+#---------------------------------------------------------------------------
+# Build related configuration options
+#---------------------------------------------------------------------------
+EXTRACT_ALL = YES
+EXTRACT_PRIVATE = YES
+EXTRACT_STATIC = YES
+EXTRACT_LOCAL_CLASSES = YES
+EXTRACT_LOCAL_METHODS = NO
+HIDE_UNDOC_MEMBERS = YES
+HIDE_UNDOC_CLASSES = YES
+HIDE_FRIEND_COMPOUNDS = NO
+HIDE_IN_BODY_DOCS = NO
+INTERNAL_DOCS = YES
+CASE_SENSE_NAMES = YES
+HIDE_SCOPE_NAMES = NO
+SHOW_INCLUDE_FILES = YES
+INLINE_INFO = YES
+SORT_MEMBER_DOCS = NO
+SORT_BRIEF_DOCS = NO
+SORT_BY_SCOPE_NAME = NO
+GENERATE_TODOLIST = YES
+GENERATE_TESTLIST = YES
+GENERATE_BUGLIST = YES
+GENERATE_DEPRECATEDLIST= YES
+ENABLED_SECTIONS =
+MAX_INITIALIZER_LINES = 25
+SHOW_USED_FILES = NO
+SHOW_DIRECTORIES = NO
+FILE_VERSION_FILTER =
+
+#---------------------------------------------------------------------------
+# configuration options related to warning and progress messages
+#---------------------------------------------------------------------------
+QUIET = NO
+WARNINGS = YES
+WARN_IF_UNDOCUMENTED = YES
+WARN_IF_DOC_ERROR = YES
+WARN_NO_PARAMDOC = NO
+WARN_FORMAT = "$file:$line: $text"
+WARN_LOGFILE =
+
+#---------------------------------------------------------------------------
+# configuration options related to the input files
+#---------------------------------------------------------------------------
+INPUT = @top_srcdir@/src \
+ @top_srcdir@/bin \
+ @top_srcdir@/idl \
+ @top_builddir@/bin
+FILE_PATTERNS = *.idl *.hxx *.cxx *.h *.c *.hh *.cc @DOXYGEN_PYTHON_EXTENSION@
+RECURSIVE = YES
+EXCLUDE =
+EXCLUDE_SYMLINKS = NO
+EXCLUDE_PATTERNS =
+EXAMPLE_PATH =
+EXAMPLE_PATTERNS =
+EXAMPLE_RECURSIVE = YES
+IMAGE_PATH = @srcdir@/images
+INPUT_FILTER =
+FILTER_PATTERNS =
+FILTER_SOURCE_FILES = YES
+
+#---------------------------------------------------------------------------
+# configuration options related to source browsing
+#---------------------------------------------------------------------------
+SOURCE_BROWSER = NO
+INLINE_SOURCES = NO
+STRIP_CODE_COMMENTS = YES
+REFERENCED_BY_RELATION = NO
+REFERENCES_RELATION = YES
+USE_HTAGS = NO
+VERBATIM_HEADERS = YES
+
+#---------------------------------------------------------------------------
+# configuration options related to the alphabetical class index
+#---------------------------------------------------------------------------
+ALPHABETICAL_INDEX = YES
+COLS_IN_ALPHA_INDEX = 3
+IGNORE_PREFIX =
+
+#---------------------------------------------------------------------------
+# configuration options related to the HTML output
+#---------------------------------------------------------------------------
+GENERATE_HTML = YES
+HTML_OUTPUT = .
+HTML_FILE_EXTENSION = .html
+HTML_HEADER = @srcdir@/static/myheader.html
+HTML_FOOTER = @srcdir@/static/footer.html
+HTML_STYLESHEET = @srcdir@/static/doxygen.css
+HTML_ALIGN_MEMBERS = YES
+GENERATE_HTMLHELP = NO
+CHM_FILE =
+HHC_LOCATION =
+GENERATE_CHI = NO
+BINARY_TOC = YES
+TOC_EXPAND = YES
+DISABLE_INDEX = NO
+ENUM_VALUES_PER_LINE = 4
+GENERATE_TREEVIEW = NO
+TREEVIEW_WIDTH = 250
+
+#---------------------------------------------------------------------------
+# configuration options related to the LaTeX output
+#---------------------------------------------------------------------------
+GENERATE_LATEX = NO
+LATEX_OUTPUT = latex
+LATEX_CMD_NAME = latex
+MAKEINDEX_CMD_NAME = makeindex
+COMPACT_LATEX = NO
+PAPER_TYPE = a4wide
+EXTRA_PACKAGES =
+LATEX_HEADER =
+PDF_HYPERLINKS = NO
+USE_PDFLATEX = NO
+LATEX_BATCHMODE = NO
+LATEX_HIDE_INDICES = NO
+
+#---------------------------------------------------------------------------
+# configuration options related to the RTF output
+#---------------------------------------------------------------------------
+GENERATE_RTF = NO
+RTF_OUTPUT = rtf
+COMPACT_RTF = NO
+RTF_HYPERLINKS = NO
+RTF_STYLESHEET_FILE =
+RTF_EXTENSIONS_FILE =
+
+#---------------------------------------------------------------------------
+# configuration options related to the man page output
+#---------------------------------------------------------------------------
+GENERATE_MAN = NO
+MAN_OUTPUT = man
+MAN_EXTENSION = .3
+MAN_LINKS = NO
+
+#---------------------------------------------------------------------------
+# configuration options related to the XML output
+#---------------------------------------------------------------------------
+GENERATE_XML = NO
+XML_OUTPUT = xml
+XML_SCHEMA =
+XML_DTD =
+XML_PROGRAMLISTING = YES
+
+#---------------------------------------------------------------------------
+# configuration options for the AutoGen Definitions output
+#---------------------------------------------------------------------------
+GENERATE_AUTOGEN_DEF = NO
+
+#---------------------------------------------------------------------------
+# configuration options related to the Perl module output
+#---------------------------------------------------------------------------
+GENERATE_PERLMOD = NO
+PERLMOD_LATEX = NO
+PERLMOD_PRETTY = YES
+PERLMOD_MAKEVAR_PREFIX =
+
+#---------------------------------------------------------------------------
+# Configuration options related to the preprocessor
+#---------------------------------------------------------------------------
+ENABLE_PREPROCESSING = YES
+MACRO_EXPANSION = YES
+EXPAND_ONLY_PREDEF = NO
+SEARCH_INCLUDES = YES
+INCLUDE_PATH =
+INCLUDE_FILE_PATTERNS =
+PREDEFINED =
+EXPAND_AS_DEFINED =
+SKIP_FUNCTION_MACROS = NO
+
+#---------------------------------------------------------------------------
+# Configuration::additions related to external references
+#---------------------------------------------------------------------------
+TAGFILES =
+GENERATE_TAGFILE =
+ALLEXTERNALS = NO
+EXTERNAL_GROUPS = YES
+PERL_PATH = /usr/bin/perl
+
+#---------------------------------------------------------------------------
+# Configuration options related to the dot tool
+#---------------------------------------------------------------------------
+CLASS_DIAGRAMS = YES
+HIDE_UNDOC_RELATIONS = NO
+HAVE_DOT = YES
+CLASS_GRAPH = YES
+COLLABORATION_GRAPH = NO
+GROUP_GRAPHS = NO
+UML_LOOK = NO
+TEMPLATE_RELATIONS = YES
+INCLUDE_GRAPH = YES
+INCLUDED_BY_GRAPH = NO
+CALL_GRAPH = NO
+GRAPHICAL_HIERARCHY = YES
+DIRECTORY_GRAPH = YES
+DOT_IMAGE_FORMAT = jpg
+DOT_PATH =
+DOTFILE_DIRS =
+MAX_DOT_GRAPH_WIDTH = 1024
+MAX_DOT_GRAPH_HEIGHT = 1200
+MAX_DOT_GRAPH_DEPTH = 0
+DOT_TRANSPARENT = NO
+DOT_MULTI_TARGETS = NO
+GENERATE_LEGEND = NO
+DOT_CLEANUP = YES
+
+#---------------------------------------------------------------------------
+# Configuration::additions related to the search engine
+#---------------------------------------------------------------------------
+SEARCHENGINE = NO
--- /dev/null
+H1 {
+ text-align: center;
+}
+
+CAPTION {
+ font-weight: bold
+}
+
+/* Link in the top navbar */
+A.qindex {}
+
+A.qindexRef {}
+
+/* Link to any cross-referenced Doxygen element */
+A.el {
+ text-decoration: none;
+ font-weight: bold
+}
+
+A.elRef {
+ font-weight: bold
+}
+
+/* Link to any cross-referenced Doxygen element inside a code section
+ (ex: header)
+*/
+A.code {
+ text-decoration: none;
+ font-weight: normal;
+ color: #4444ee
+}
+
+A.codeRef {
+ font-weight: normal;
+ color: #4444ee
+}
+
+A:hover {
+ text-decoration: none;
+ background-color: lightblue
+}
+
+DL.el {
+ margin-left: -1cm
+}
+
+/* A code fragment (ex: header) */
+DIV.fragment {
+ width: 100%;
+ border: none;
+ background-color: #CCCCCC
+}
+
+/* In the alpha list (coumpound index), style of an alphabetical index letter */
+DIV.ah {
+ background-color: #CCCCCC;
+ font-weight: bold;
+ color: #ffffff;
+ margin-bottom: 3px;
+ margin-top: 3px
+}
+
+/* Method name (+ type) */
+TD.md {
+ background-color: lightblue;
+ font-weight: bold;
+}
+
+/* Method parameter (some of them) */
+TD.mdname1 {
+ background-color: lightblue;
+ font-weight: bold; color: #602020;
+}
+
+/* Method parameter (some of them) */
+TD.mdname {
+ background-color: lightblue;
+ font-weight: bold;
+ color: #602020;
+ width: 600px;
+}
+
+/* Separator between methods group (usually empty, seems not supported by IE) */
+DIV.groupHeader {
+ margin-left: 16px;
+ margin-top: 12px;
+ margin-bottom: 6px;
+ font-weight: bold
+}
+
+DIV.groupText {
+ margin-left: 16px;
+ font-style: italic;
+ font-size: smaller
+}
+
+BODY { background: #FFFFFF
+}
+
+/* BODY {
+ background: url(sources/bg_salome.gif)
+} */
+
+div.tabs {
+ text-align: justify;
+ font-weight: bold;
+ color: #FFFFFF;
+}
+
+DIV.div-footer {
+ margin-left: 1em;
+ margin-right: 1em;
+ margin-bottom: 0.2em;
+ text-align: right;
+ font-size: 9pt;
+}
+
+/* In File List, Coumpound List, etc, 1st column of the index */
+TD.indexkey {
+ background-color: #CCCCCC;
+ font-weight: bold;
+ padding-right : 10px;
+ padding-top : 2px;
+ padding-left : 10px;
+ padding-bottom : 2px;
+ margin-left : 0px;
+ margin-right : 0px;
+ margin-top : 2px;
+ margin-bottom : 2px
+}
+
+/* In File List, Coumpound List, etc, 2nd column of the index */
+TD.indexvalue {
+ background-color: #CCCCCC;
+ font-style: italic;
+ padding-right : 10px;
+ padding-top : 2px;
+ padding-left : 10px;
+ padding-bottom : 2px;
+ margin-left : 0px;
+ margin-right : 0px;
+ margin-top : 2px;
+ margin-bottom : 2px
+}
+
+span.keyword { color: #008000 }
+span.keywordtype { color: #604020 }
+span.keywordflow { color: #e08000 }
+span.comment { color: #800000 }
+span.preprocessor { color: #806020 }
+span.stringliteral { color: #002080 }
+span.charliteral { color: #008080 }
--- /dev/null
+</DIV>
+<DIV class="div-footer">
+Generated on $datetime for $projectname by <A href="http://www.doxygen.org/index.html"><img src="doxygen.png" alt="doxygen" align="middle" border="0"></A> $doxygenversion</DIV>
+</BODY>
+</HTML>
--- /dev/null
+<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+ <meta name="GENERATOR" content="Mozilla/4.73 [en] (WinNT; I) [Netscape]">
+ <title>Main Page</title>
+<link href="doxygen.css" rel="stylesheet" type="text/css">
+<link href="tabs.css" rel="stylesheet" type="text/css">
+</head>
+<body>
+
+</body>
+</html>
include $(top_srcdir)/adm_local/unix/make_common_starter.am
-BASEIDL_FILES= SalomeApp_Engine.idl
-
-EXTRA_DIST+= $(BASEIDL_FILES)
+BASEIDL_FILES = SalomeApp_Engine.idl
# This variable defines the files to be installed
-salomeidl_DATA = $(BASEIDL_FILES)
+dist_salomeidl_DATA = $(BASEIDL_FILES)
# GUI idl common library
lib_LTLIBRARIES = libSalomeIDLGUI.la
# Sources built from idl files
-nodist_libSalomeIDLGUI_la_SOURCES= SalomeApp_EngineSK.cc
+nodist_libSalomeIDLGUI_la_SOURCES = SalomeApp_EngineSK.cc
# header files must be exported: other modules have to use this library
-nodist_salomeinclude_HEADERS= $(BASEIDL_FILES:%.idl=%.hh)
+nodist_salomeinclude_HEADERS = $(BASEIDL_FILES:%.idl=%.hh)
-libSalomeIDLGUI_la_CPPFLAGS =\
+libSalomeIDLGUI_la_CPPFLAGS = \
-I$(top_builddir)/salome_adm/unix \
-I$(top_builddir)/idl \
@CORBA_CXXFLAGS@ @CORBA_INCLUDES@ @KERNEL_CXXFLAGS@
$(OMNIORB_IDL) $(IDLCXXFLAGS) $(OMNIORB_IDLCXXFLAGS) $<
install-exec-local: $(BASEIDL_FILES:%=$(top_srcdir)/idl/%)
- $(INSTALL) -d $(pkgpythondir)
+ $(INSTALL) -d $(DESTDIR)$(salomepythondir)
ls $^ | while read file; do \
- $(OMNIORB_IDL) $(IDLPYFLAGS) -C$(pkgpythondir) $$file ; \
+ $(OMNIORB_IDL) $(IDLPYFLAGS) -C$(DESTDIR)$(salomepythondir) $$file ; \
done
# uninstall-local removes too much, but it works in distcheck
uninstall-local:
- rm -rf $(pkgpythondir)/*
+ rm -rf $(DESTDIR)$(salomepythondir)/*
mostlyclean-local:
-rm -f *.hh *.cc .depidl
include $(top_srcdir)/adm_local/unix/make_common_starter.am
-#
-# ===============================================================
-# Files to be installed
-# ===============================================================
-#
-
#
# add resource files here ...
#
-dist_salomeres_DATA=
+dist_salomeres_DATA =
lib_LTLIBRARIES = libcaf.la
-salomeinclude_HEADERS= \
- CAF.h \
- CAF_Application.h \
- CAF_Operation.h \
- CAF_Study.h \
+salomeinclude_HEADERS = \
+ CAF.h \
+ CAF_Application.h \
+ CAF_Operation.h \
+ CAF_Study.h \
CAF_Tools.h
-dist_libcaf_la_SOURCES= \
- CAF_Application.cxx \
- CAF_Operation.cxx \
- CAF_Study.cxx \
+dist_libcaf_la_SOURCES = \
+ CAF_Application.cxx \
+ CAF_Operation.cxx \
+ CAF_Study.cxx \
CAF_Tools.cxx
-MOC_FILES= \
- CAF_Application_moc.cxx \
- CAF_Operation_moc.cxx \
+MOC_FILES = \
+ CAF_Application_moc.cxx \
+ CAF_Operation_moc.cxx \
CAF_Study_moc.cxx
-nodist_libcaf_la_SOURCES= $(MOC_FILES)
+nodist_libcaf_la_SOURCES = $(MOC_FILES)
nodist_salomeres_DATA = \
CAF_msg_en.qm
-libcaf_la_CPPFLAGS=$(QT_INCLUDES) $(CAS_CPPFLAGS) -I$(srcdir)/../STD -I$(srcdir)/../SUIT -I$(srcdir)/../Qtx
-libcaf_la_LDFLAGS=$(QT_MT_LIBS) $(CAS_OCAF) $(CAS_OCAFVIS)
-libcaf_la_LIBADD=../Qtx/libqtx.la ../SUIT/libsuit.la ../STD/libstd.la
+libcaf_la_CPPFLAGS = $(QT_INCLUDES) $(CAS_CPPFLAGS) -I$(srcdir)/../STD -I$(srcdir)/../SUIT -I$(srcdir)/../Qtx
+libcaf_la_LDFLAGS = $(QT_MT_LIBS) $(CAS_OCAF) $(CAS_OCAFVIS)
+libcaf_la_LIBADD = ../Qtx/libqtx.la ../SUIT/libsuit.la ../STD/libstd.la
lib_LTLIBRARIES = libCAM.la
-salomeinclude_HEADERS= \
- CAM.h \
- CAM_Application.h \
- CAM_DataModel.h \
- CAM_DataObject.h \
- CAM_Module.h \
+salomeinclude_HEADERS = \
+ CAM.h \
+ CAM_Application.h \
+ CAM_DataModel.h \
+ CAM_DataObject.h \
+ CAM_Module.h \
CAM_Study.h
-dist_libCAM_la_SOURCES= \
- CAM_Application.cxx \
- CAM_DataModel.cxx \
- CAM_DataObject.cxx \
- CAM_Module.cxx \
+dist_libCAM_la_SOURCES = \
+ CAM_Application.cxx \
+ CAM_DataModel.cxx \
+ CAM_DataObject.cxx \
+ CAM_Module.cxx \
CAM_Study.cxx
-MOC_FILES= \
- CAM_Application_moc.cxx \
- CAM_Module_moc.cxx \
- CAM_Study_moc.cxx \
+MOC_FILES = \
+ CAM_Application_moc.cxx \
+ CAM_Module_moc.cxx \
+ CAM_Study_moc.cxx \
CAM_DataModel_moc.cxx
-nodist_libCAM_la_SOURCES= $(MOC_FILES)
+nodist_libCAM_la_SOURCES = $(MOC_FILES)
-nodist_salomeres_DATA=CAM_msg_en.qm
+nodist_salomeres_DATA = CAM_msg_en.qm
-libCAM_la_CPPFLAGS=$(QT_INCLUDES) -I$(srcdir)/../SUIT -I$(srcdir)/../STD -I$(srcdir)/../Qtx
-libCAM_la_LDFLAGS=$(QT_MT_LIBS)
-libCAM_la_LIBADD=../Qtx/libqtx.la ../SUIT/libsuit.la ../STD/libstd.la
-
-# what is that?
-#LDFLAGSFORBIN= -lSUITApp
+libCAM_la_CPPFLAGS = $(QT_INCLUDES) -I$(srcdir)/../SUIT -I$(srcdir)/../STD -I$(srcdir)/../Qtx
+libCAM_la_LDFLAGS = $(QT_MT_LIBS)
+libCAM_la_LIBADD = ../Qtx/libqtx.la ../SUIT/libsuit.la ../STD/libstd.la
include $(top_srcdir)/adm_local/unix/make_common_starter.am
-salomeinclude_HEADERS = CASCatch.hxx \
- CASCatch_CatchSignals.hxx \
- CASCatch_ErrorHandler.hxx \
+salomeinclude_HEADERS = CASCatch.hxx \
+ CASCatch_CatchSignals.hxx \
+ CASCatch_ErrorHandler.hxx \
CASCatch_Failure.hxx
lib_LTLIBRARIES = libCASCatch.la
-libCASCatch_la_SOURCES = \
- CASCatch_CatchSignals.cxx \
- CASCatch_ErrorHandler.cxx \
+libCASCatch_la_SOURCES = \
+ CASCatch_CatchSignals.cxx \
+ CASCatch_ErrorHandler.cxx \
CASCatch_Failure.cxx
COMMON_CPPFLAGS = \
@CAS_CPPFLAGS@ @CAS_CXXFLAGS@
libCASCatch_la_CPPFLAGS = $(COMMON_CPPFLAGS)
-libCASCatch_la_LIBADD = $(CAS_KERNEL)
+libCASCatch_la_LIBADD = $(CAS_KERNEL)
DDS_Dictionary.cxx \
DDS_KeyWords.cxx
-libDDS_la_CPPFLAGS=$(CAS_CPPFLAGS)
+libDDS_la_CPPFLAGS = $(CAS_CPPFLAGS)
-libDDS_la_LDFLAGS= $(CAS_KERNEL) $(CAS_OCAF)
+libDDS_la_LDFLAGS = $(CAS_KERNEL) $(CAS_OCAF)
lib_LTLIBRARIES = libEvent.la
-salomeinclude_HEADERS= \
- Event.h \
+salomeinclude_HEADERS = \
+ Event.h \
SALOME_Event.h
dist_libEvent_la_SOURCES = SALOME_Event.cxx
-libEvent_la_CPPFLAGS=$(QT_INCLUDES)
-libEvent_la_LDFLAGS=$(QT_MT_LIBS)
+libEvent_la_CPPFLAGS = $(QT_INCLUDES)
+libEvent_la_LDFLAGS = $(QT_MT_LIBS)
lib_LTLIBRARIES = libGLViewer.la
-salomeinclude_HEADERS= \
- GLViewer.h \
- GLViewer_AspectLine.h \
- GLViewer_BaseDrawers.h \
- GLViewer_BaseObjects.h \
- GLViewer_Compass.h \
- GLViewer_Context.h \
- GLViewer_CoordSystem.h \
- GLViewer_Defs.h \
- GLViewer_Drawer.h \
- GLViewer_Geom.h \
- GLViewer_Grid.h \
- GLViewer_Group.h \
- GLViewer_MimeData.h \
- GLViewer_Object.h \
- GLViewer_Selector.h \
- GLViewer_Selector2d.h \
- GLViewer_Text.h \
- GLViewer_Tools.h \
- GLViewer_ToolTip.h \
- GLViewer_ViewFrame.h \
- GLViewer_ViewManager.h \
- GLViewer_ViewPort.h \
- GLViewer_ViewPort2d.h \
- GLViewer_Viewer.h \
- GLViewer_Viewer2d.h \
+salomeinclude_HEADERS = \
+ GLViewer.h \
+ GLViewer_AspectLine.h \
+ GLViewer_BaseDrawers.h \
+ GLViewer_BaseObjects.h \
+ GLViewer_Compass.h \
+ GLViewer_Context.h \
+ GLViewer_CoordSystem.h \
+ GLViewer_Defs.h \
+ GLViewer_Drawer.h \
+ GLViewer_Geom.h \
+ GLViewer_Grid.h \
+ GLViewer_Group.h \
+ GLViewer_MimeData.h \
+ GLViewer_Object.h \
+ GLViewer_Selector.h \
+ GLViewer_Selector2d.h \
+ GLViewer_Text.h \
+ GLViewer_Tools.h \
+ GLViewer_ToolTip.h \
+ GLViewer_ViewFrame.h \
+ GLViewer_ViewManager.h \
+ GLViewer_ViewPort.h \
+ GLViewer_ViewPort2d.h \
+ GLViewer_Viewer.h \
+ GLViewer_Viewer2d.h \
GLViewer_Widget.h
-dist_libGLViewer_la_SOURCES= \
- GLViewer_AspectLine.cxx \
- GLViewer_BaseDrawers.cxx \
- GLViewer_BaseObjects.cxx \
- GLViewer_Compass.cxx \
- GLViewer_Context.cxx \
- GLViewer_CoordSystem.cxx \
- GLViewer_Drawer.cxx \
- GLViewer_Geom.cxx \
- GLViewer_Grid.cxx \
- GLViewer_Group.cxx \
- GLViewer_MimeData.cxx \
- GLViewer_Object.cxx \
- GLViewer_Selector.cxx \
- GLViewer_Selector2d.cxx \
- GLViewer_Text.cxx \
- GLViewer_Tools.cxx \
- GLViewer_ToolTip.cxx \
- GLViewer_ViewFrame.cxx \
- GLViewer_ViewManager.cxx \
- GLViewer_ViewPort.cxx \
- GLViewer_ViewPort2d.cxx \
- GLViewer_Viewer.cxx \
- GLViewer_Viewer2d.cxx \
+dist_libGLViewer_la_SOURCES = \
+ GLViewer_AspectLine.cxx \
+ GLViewer_BaseDrawers.cxx \
+ GLViewer_BaseObjects.cxx \
+ GLViewer_Compass.cxx \
+ GLViewer_Context.cxx \
+ GLViewer_CoordSystem.cxx \
+ GLViewer_Drawer.cxx \
+ GLViewer_Geom.cxx \
+ GLViewer_Grid.cxx \
+ GLViewer_Group.cxx \
+ GLViewer_MimeData.cxx \
+ GLViewer_Object.cxx \
+ GLViewer_Selector.cxx \
+ GLViewer_Selector2d.cxx \
+ GLViewer_Text.cxx \
+ GLViewer_Tools.cxx \
+ GLViewer_ToolTip.cxx \
+ GLViewer_ViewFrame.cxx \
+ GLViewer_ViewManager.cxx \
+ GLViewer_ViewPort.cxx \
+ GLViewer_ViewPort2d.cxx \
+ GLViewer_Viewer.cxx \
+ GLViewer_Viewer2d.cxx \
GLViewer_Widget.cxx
-MOC_FILES= \
- GLViewer_Selector_moc.cxx \
- GLViewer_Selector2d_moc.cxx \
- GLViewer_ToolTip_moc.cxx \
- GLViewer_ViewFrame_moc.cxx \
- GLViewer_ViewManager_moc.cxx \
- GLViewer_ViewPort_moc.cxx \
- GLViewer_ViewPort2d_moc.cxx \
- GLViewer_Viewer_moc.cxx \
- GLViewer_Viewer2d_moc.cxx \
+MOC_FILES = \
+ GLViewer_Selector_moc.cxx \
+ GLViewer_Selector2d_moc.cxx \
+ GLViewer_ToolTip_moc.cxx \
+ GLViewer_ViewFrame_moc.cxx \
+ GLViewer_ViewManager_moc.cxx \
+ GLViewer_ViewPort_moc.cxx \
+ GLViewer_ViewPort2d_moc.cxx \
+ GLViewer_Viewer_moc.cxx \
+ GLViewer_Viewer2d_moc.cxx \
GLViewer_Widget_moc.cxx
-nodist_libGLViewer_la_SOURCES= $(MOC_FILES)
+nodist_libGLViewer_la_SOURCES = $(MOC_FILES)
-dist_salomeres_DATA= \
- resources/gl_cursor_rotate.png \
- resources/gl_cursor_sketch.png \
- resources/gl_cursor_zoom.png \
- resources/gl_view_dump.png \
- resources/gl_view_fitall.png \
- resources/gl_view_fitarea.png \
- resources/gl_view_fitselect.png \
- resources/gl_view_glpan.png \
- resources/gl_view_pan.png \
- resources/gl_view_reset.png \
+dist_salomeres_DATA = \
+ resources/gl_cursor_rotate.png \
+ resources/gl_cursor_sketch.png \
+ resources/gl_cursor_zoom.png \
+ resources/gl_view_dump.png \
+ resources/gl_view_fitall.png \
+ resources/gl_view_fitarea.png \
+ resources/gl_view_fitselect.png \
+ resources/gl_view_glpan.png \
+ resources/gl_view_pan.png \
+ resources/gl_view_reset.png \
resources/gl_view_zoom.png
-nodist_salomeres_DATA= \
- GLViewer_images.qm \
+nodist_salomeres_DATA = \
+ GLViewer_images.qm \
GLViewer_msg_en.qm
-libGLViewer_la_CPPFLAGS=$(QT_INCLUDES) $(CAS_CPPFLAGS) -I$(srcdir)/../SUIT -I$(srcdir)/../Qtx
-libGLViewer_la_LDFLAGS=$(QT_MT_LIBS) $(CAS_KERNEL)
-
-libGLViewer_la_LIBADD= ../SUIT/libsuit.la
+libGLViewer_la_CPPFLAGS = $(QT_INCLUDES) $(CAS_CPPFLAGS) -I$(srcdir)/../SUIT -I$(srcdir)/../Qtx
+libGLViewer_la_LDFLAGS = $(QT_MT_LIBS) $(CAS_KERNEL)
+libGLViewer_la_LIBADD = ../SUIT/libsuit.la
lib_LTLIBRARIES = libLightApp.la
-salomeinclude_HEADERS= \
- LightApp.h \
- LightApp_AboutDlg.h \
- LightApp_Application.h \
- LightApp_DataModel.h \
- LightApp_DataObject.h \
- LightApp_DataOwner.h \
- LightApp_DataSubOwner.h \
- LightApp_Dialog.h \
- LightApp_Displayer.h \
- LightApp_Driver.h \
- LightApp_EventFilter.h \
- LightApp_HDFDriver.h \
- LightApp_Module.h \
- LightApp_ModuleAction.h \
- LightApp_ModuleDlg.h \
- LightApp_NameDlg.h \
- LightApp_OBSelector.h \
- LightApp_Operation.h \
- LightApp_Selection.h \
- LightApp_SelectionMgr.h \
- LightApp_ShowHideOp.h \
- LightApp_Study.h \
- LightApp_SwitchOp.h \
- LightApp_Preferences.h \
- LightApp_PreferencesDlg.h \
+salomeinclude_HEADERS = \
+ LightApp.h \
+ LightApp_AboutDlg.h \
+ LightApp_Application.h \
+ LightApp_DataModel.h \
+ LightApp_DataObject.h \
+ LightApp_DataOwner.h \
+ LightApp_DataSubOwner.h \
+ LightApp_Dialog.h \
+ LightApp_Displayer.h \
+ LightApp_Driver.h \
+ LightApp_EventFilter.h \
+ LightApp_HDFDriver.h \
+ LightApp_Module.h \
+ LightApp_ModuleAction.h \
+ LightApp_ModuleDlg.h \
+ LightApp_NameDlg.h \
+ LightApp_OBSelector.h \
+ LightApp_Operation.h \
+ LightApp_Selection.h \
+ LightApp_SelectionMgr.h \
+ LightApp_ShowHideOp.h \
+ LightApp_Study.h \
+ LightApp_SwitchOp.h \
+ LightApp_Preferences.h \
+ LightApp_PreferencesDlg.h \
LightApp_UpdateFlags.h
# LightApp_OBFilter.h
if ENABLE_VTKVIEWER
if ENABLE_SALOMEOBJECT
- salomeinclude_HEADERS+= LightApp_VTKSelector.h
+ salomeinclude_HEADERS += LightApp_VTKSelector.h
endif
endif
if ENABLE_OCCVIEWER
- salomeinclude_HEADERS+= LightApp_OCCSelector.h
+ salomeinclude_HEADERS += LightApp_OCCSelector.h
endif
if ENABLE_GLVIEWER
- salomeinclude_HEADERS+= LightApp_GLSelector.h
-endif
-
-dist_libLightApp_la_SOURCES= \
- LightApp_AboutDlg.cxx \
- LightApp_Application.cxx \
- LightApp_DataModel.cxx \
- LightApp_DataObject.cxx \
- LightApp_DataOwner.cxx \
- LightApp_DataSubOwner.cxx \
- LightApp_Dialog.cxx \
- LightApp_Displayer.cxx \
- LightApp_Driver.cxx \
- LightApp_EventFilter.cxx \
- LightApp_HDFDriver.cxx \
- LightApp_Module.cxx \
- LightApp_ModuleAction.cxx \
- LightApp_ModuleDlg.cxx \
- LightApp_NameDlg.cxx \
- LightApp_OBSelector.cxx \
- LightApp_Operation.cxx \
- LightApp_Selection.cxx \
- LightApp_SelectionMgr.cxx \
- LightApp_ShowHideOp.cxx \
- LightApp_Study.cxx \
- LightApp_SwitchOp.cxx \
- LightApp_Preferences.cxx \
+ salomeinclude_HEADERS += LightApp_GLSelector.h
+endif
+
+dist_libLightApp_la_SOURCES = \
+ LightApp_AboutDlg.cxx \
+ LightApp_Application.cxx \
+ LightApp_DataModel.cxx \
+ LightApp_DataObject.cxx \
+ LightApp_DataOwner.cxx \
+ LightApp_DataSubOwner.cxx \
+ LightApp_Dialog.cxx \
+ LightApp_Displayer.cxx \
+ LightApp_Driver.cxx \
+ LightApp_EventFilter.cxx \
+ LightApp_HDFDriver.cxx \
+ LightApp_Module.cxx \
+ LightApp_ModuleAction.cxx \
+ LightApp_ModuleDlg.cxx \
+ LightApp_NameDlg.cxx \
+ LightApp_OBSelector.cxx \
+ LightApp_Operation.cxx \
+ LightApp_Selection.cxx \
+ LightApp_SelectionMgr.cxx \
+ LightApp_ShowHideOp.cxx \
+ LightApp_Study.cxx \
+ LightApp_SwitchOp.cxx \
+ LightApp_Preferences.cxx \
LightApp_PreferencesDlg.cxx
# LightApp_OBFilter.cxx
if ENABLE_VTKVIEWER
if ENABLE_SALOMEOBJECT
- dist_libLightApp_la_SOURCES+= LightApp_VTKSelector.cxx
+ dist_libLightApp_la_SOURCES += LightApp_VTKSelector.cxx
endif
endif
if ENABLE_OCCVIEWER
- dist_libLightApp_la_SOURCES+= LightApp_OCCSelector.cxx
+ dist_libLightApp_la_SOURCES += LightApp_OCCSelector.cxx
endif
if ENABLE_GLVIEWER
- dist_libLightApp_la_SOURCES+= LightApp_GLSelector.cxx
-endif
-
-MOC_FILES= \
- LightApp_AboutDlg_moc.cxx \
- LightApp_Application_moc.cxx \
- LightApp_DataModel_moc.cxx \
- LightApp_Dialog_moc.cxx \
- LightApp_OBSelector_moc.cxx \
- LightApp_Operation_moc.cxx \
- LightApp_Module_moc.cxx \
- LightApp_ModuleAction_moc.cxx \
- LightApp_ModuleDlg_moc.cxx \
- LightApp_NameDlg_moc.cxx \
- LightApp_SelectionMgr_moc.cxx \
- LightApp_ShowHideOp_moc.cxx \
- LightApp_Study_moc.cxx \
- LightApp_SwitchOp_moc.cxx \
- LightApp_Preferences_moc.cxx \
+ dist_libLightApp_la_SOURCES += LightApp_GLSelector.cxx
+endif
+
+MOC_FILES = \
+ LightApp_AboutDlg_moc.cxx \
+ LightApp_Application_moc.cxx \
+ LightApp_DataModel_moc.cxx \
+ LightApp_Dialog_moc.cxx \
+ LightApp_OBSelector_moc.cxx \
+ LightApp_Operation_moc.cxx \
+ LightApp_Module_moc.cxx \
+ LightApp_ModuleAction_moc.cxx \
+ LightApp_ModuleDlg_moc.cxx \
+ LightApp_NameDlg_moc.cxx \
+ LightApp_SelectionMgr_moc.cxx \
+ LightApp_ShowHideOp_moc.cxx \
+ LightApp_Study_moc.cxx \
+ LightApp_SwitchOp_moc.cxx \
+ LightApp_Preferences_moc.cxx \
LightApp_PreferencesDlg_moc.cxx
if ENABLE_VTKVIEWER
if ENABLE_SALOMEOBJECT
- MOC_FILES+= LightApp_VTKSelector_moc.cxx
+ MOC_FILES += LightApp_VTKSelector_moc.cxx
endif
endif
if ENABLE_OCCVIEWER
- MOC_FILES+= LightApp_OCCSelector_moc.cxx
+ MOC_FILES += LightApp_OCCSelector_moc.cxx
endif
if ENABLE_GLVIEWER
- MOC_FILES+= LightApp_GLSelector_moc.cxx
-endif
-nodist_libLightApp_la_SOURCES= $(MOC_FILES)
-
-dist_salomeres_DATA= \
- resources/icon_about.png \
- resources/icon_applogo.png \
- resources/icon_default.png \
- resources/icon_module.png \
- resources/icon_module_big.png \
- resources/icon_select.png \
- resources/LightApp.ini \
+ MOC_FILES += LightApp_GLSelector_moc.cxx
+endif
+nodist_libLightApp_la_SOURCES = $(MOC_FILES)
+
+dist_salomeres_DATA = \
+ resources/icon_about.png \
+ resources/icon_applogo.png \
+ resources/icon_default.png \
+ resources/icon_module.png \
+ resources/icon_module_big.png \
+ resources/icon_select.png \
+ resources/LightApp.ini \
resources/LightApp.xml
-nodist_salomeres_DATA= \
- LightApp_images.qm \
+nodist_salomeres_DATA = \
+ LightApp_images.qm \
LightApp_msg_en.qm
-libLightApp_la_CPPFLAGS=$(PYTHON_INCLUDES) $(QT_INCLUDES) $(CAS_CPPFLAGS) \
- $(HDF5_INCLUDES) @KERNEL_CXXFLAGS@ -I$(srcdir)/../SUIT -I$(srcdir)/../STD \
- -I$(srcdir)/../CAM -I$(srcdir)/../ObjBrowser -I$(srcdir)/../LogWindow \
+libLightApp_la_CPPFLAGS = $(PYTHON_INCLUDES) $(QT_INCLUDES) $(CAS_CPPFLAGS) \
+ $(HDF5_INCLUDES) @KERNEL_CXXFLAGS@ -I$(srcdir)/../SUIT -I$(srcdir)/../STD \
+ -I$(srcdir)/../CAM -I$(srcdir)/../ObjBrowser -I$(srcdir)/../LogWindow \
-I$(srcdir)/../Prs -I$(srcdir)/../Qtx -I$(srcdir)/../Event -I$(srcdir)/../Style
-libLightApp_la_LDFLAGS=$(QT_MT_LIBS)
+libLightApp_la_LDFLAGS = $(QT_MT_LIBS)
if ENABLE_VTKVIEWER
- libLightApp_la_CPPFLAGS+= $(VTK_INCLUDES) -I$(srcdir)/../VTKViewer
+ libLightApp_la_CPPFLAGS += $(VTK_INCLUDES) -I$(srcdir)/../VTKViewer
else
- libLightApp_la_CPPFLAGS+= -DDISABLE_VTKVIEWER
+ libLightApp_la_CPPFLAGS += -DDISABLE_VTKVIEWER
endif
if ENABLE_PLOT2DVIEWER
- libLightApp_la_CPPFLAGS+= $(QWT_INCLUDES) -I$(srcdir)/../Plot2d
+ libLightApp_la_CPPFLAGS += $(QWT_INCLUDES) -I$(srcdir)/../Plot2d
else
- libLightApp_la_CPPFLAGS+= -DDISABLE_PLOT2DVIEWER
+ libLightApp_la_CPPFLAGS += -DDISABLE_PLOT2DVIEWER
endif
if ENABLE_OCCVIEWER
- libLightApp_la_CPPFLAGS+= -I$(srcdir)/../OCCViewer
+ libLightApp_la_CPPFLAGS += -I$(srcdir)/../OCCViewer
else !ENABLE_OCCVIEWER
- libLightApp_la_CPPFLAGS+= -DDISABLE_OCCVIEWER
+ libLightApp_la_CPPFLAGS += -DDISABLE_OCCVIEWER
endif
if ENABLE_PYCONSOLE
- libLightApp_la_CPPFLAGS+= $(PYTHON_INCLUDES) -I$(srcdir)/../PyConsole -I$(srcdir)/../PyInterp
- libLightApp_la_LDFLAGS+= $(PYTHON_LIBS)
+ libLightApp_la_CPPFLAGS += $(PYTHON_INCLUDES) -I$(srcdir)/../PyConsole -I$(srcdir)/../PyInterp
+ libLightApp_la_LDFLAGS += $(PYTHON_LIBS)
else !ENABLE_PYCONSOLE
- libLightApp_la_CPPFLAGS+= -DDISABLE_PYCONSOLE
+ libLightApp_la_CPPFLAGS += -DDISABLE_PYCONSOLE
endif
if ENABLE_GLVIEWER
- libLightApp_la_CPPFLAGS+= -I$(srcdir)/../GLViewer
+ libLightApp_la_CPPFLAGS += -I$(srcdir)/../GLViewer
else !ENABLE_GLVIEWER
- libLightApp_la_CPPFLAGS+= -DDISABLE_GLVIEWER
+ libLightApp_la_CPPFLAGS += -DDISABLE_GLVIEWER
endif
if ENABLE_SUPERVGRAPHVIEWER
- libLightApp_la_CPPFLAGS+= -I$(srcdir)/../SUPERVGraph
+ libLightApp_la_CPPFLAGS += -I$(srcdir)/../SUPERVGraph
else !ENABLE_SUPERVGRAPHVIEWER
- libLightApp_la_CPPFLAGS+= -DDISABLE_SUPERVGRAPHVIEWER
+ libLightApp_la_CPPFLAGS += -DDISABLE_SUPERVGRAPHVIEWER
endif
if ENABLE_QXGRAPHVIEWER
- libLightApp_la_CPPFLAGS+= -I$(srcdir)/../QxGraph
+ libLightApp_la_CPPFLAGS += -I$(srcdir)/../QxGraph
else !ENABLE_QXGRAPHVIEWER
- libLightApp_la_CPPFLAGS+= -DDISABLE_QXGRAPHVIEWER
+ libLightApp_la_CPPFLAGS += -DDISABLE_QXGRAPHVIEWER
endif
if ENABLE_SALOMEOBJECT
- libLightApp_la_CPPFLAGS+= -I$(srcdir)/../OBJECT
+ libLightApp_la_CPPFLAGS += -I$(srcdir)/../OBJECT
if ENABLE_PLOT2DVIEWER
- libLightApp_la_CPPFLAGS+= -I$(srcdir)/../SPlot2d
+ libLightApp_la_CPPFLAGS += -I$(srcdir)/../SPlot2d
endif
if ENABLE_OCCVIEWER
- libLightApp_la_CPPFLAGS+= -I$(srcdir)/../SOCC
+ libLightApp_la_CPPFLAGS += -I$(srcdir)/../SOCC
endif
if ENABLE_VTKVIEWER
- libLightApp_la_CPPFLAGS+= -I$(srcdir)/../SVTK
+ libLightApp_la_CPPFLAGS += -I$(srcdir)/../SVTK
endif
else !ENABLE_SALOMEOBJECT
- libLightApp_la_CPPFLAGS+= -DDISABLE_SALOMEOBJECT
+ libLightApp_la_CPPFLAGS += -DDISABLE_SALOMEOBJECT
endif
-libLightApp_la_LIBADD= ../SUIT/libsuit.la ../STD/libstd.la ../CAM/libCAM.la \
- ../LogWindow/libLogWindow.la $(CAS_KERNEL) \
- ../Prs/libSalomePrs.la ../ObjBrowser/libObjBrowser.la ../Style/libSalomeStyle.la \
- ../Event/libEvent.la \
+libLightApp_la_LIBADD = ../SUIT/libsuit.la ../STD/libstd.la ../CAM/libCAM.la \
+ ../LogWindow/libLogWindow.la $(CAS_KERNEL) \
+ ../Prs/libSalomePrs.la ../ObjBrowser/libObjBrowser.la ../Style/libSalomeStyle.la \
+ ../Event/libEvent.la \
$(HDF5_LIBS) $(KERNEL_LDFLAGS) -lSalomeHDFPersist
if ENABLE_SALOMEOBJECT
- libLightApp_la_LIBADD+= ../OBJECT/libSalomeObject.la
+ libLightApp_la_LIBADD += ../OBJECT/libSalomeObject.la
endif
if ENABLE_VTKVIEWER
- libLightApp_la_LIBADD+= ../VTKViewer/libVTKViewer.la
+ libLightApp_la_LIBADD += ../VTKViewer/libVTKViewer.la
if ENABLE_SALOMEOBJECT
- libLightApp_la_LIBADD+= ../SVTK/libSVTK.la
+ libLightApp_la_LIBADD += ../SVTK/libSVTK.la
endif
endif
if ENABLE_OCCVIEWER
- libLightApp_la_LIBADD+= ../OCCViewer/libOCCViewer.la
+ libLightApp_la_LIBADD += ../OCCViewer/libOCCViewer.la
if ENABLE_SALOMEOBJECT
- libLightApp_la_LIBADD+= ../SOCC/libSOCC.la
+ libLightApp_la_LIBADD += ../SOCC/libSOCC.la
endif
endif
if ENABLE_GLVIEWER
- libLightApp_la_LIBADD+= ../GLViewer/libGLViewer.la
+ libLightApp_la_LIBADD += ../GLViewer/libGLViewer.la
endif
if ENABLE_PLOT2DVIEWER
- libLightApp_la_LIBADD+= ../Plot2d/libPlot2d.la
+ libLightApp_la_LIBADD += ../Plot2d/libPlot2d.la
if ENABLE_SALOMEOBJECT
- libLightApp_la_LIBADD+= ../SPlot2d/libSPlot2d.la
+ libLightApp_la_LIBADD += ../SPlot2d/libSPlot2d.la
endif
endif
if ENABLE_PYCONSOLE
- libLightApp_la_LIBADD+= ../PyInterp/libPyInterp.la ../PyConsole/libPyConsole.la
+ libLightApp_la_LIBADD += ../PyInterp/libPyInterp.la ../PyConsole/libPyConsole.la
endif
if ENABLE_SUPERVGRAPHVIEWER
- libLightApp_la_LIBADD+= ../SUPERVGraph/libSUPERVGraph.la
+ libLightApp_la_LIBADD += ../SUPERVGraph/libSUPERVGraph.la
endif
if ENABLE_QXGRAPHVIEWER
- libLightApp_la_LIBADD+= ../QxGraph/libQxGraph.la
+ libLightApp_la_LIBADD += ../QxGraph/libQxGraph.la
endif
lib_LTLIBRARIES = libLogWindow.la
-salomeinclude_HEADERS= LogWindow.h
+salomeinclude_HEADERS = LogWindow.h
-dist_libLogWindow_la_SOURCES= LogWindow.cxx
+dist_libLogWindow_la_SOURCES = LogWindow.cxx
-MOC_FILES= LogWindow_moc.cxx
+MOC_FILES = LogWindow_moc.cxx
nodist_libLogWindow_la_SOURCES = $(MOC_FILES)
-libLogWindow_la_CPPFLAGS=$(QT_INCLUDES) -I$(srcdir)/../SUIT -I$(srcdir)/../Qtx
+nodist_salomeres_DATA = \
+ LogWindow_msg_en.qm
-libLogWindow_la_LDFLAGS=$(QT_MT_LIBS)
-libLogWindow_la_LIBADD=../Qtx/libqtx.la ../SUIT/libsuit.la
+libLogWindow_la_CPPFLAGS = $(QT_INCLUDES) -I$(srcdir)/../SUIT -I$(srcdir)/../Qtx
+libLogWindow_la_LDFLAGS = $(QT_MT_LIBS)
+libLogWindow_la_LIBADD = ../Qtx/libqtx.la ../SUIT/libsuit.la
if GUI_ENABLE_CORBA
SUBDIRS += TOOLSGUI Session SalomeApp SALOME_SWIG SALOME_PY SALOME_PYQT
endif
+
+DIST_SUBDIRS = CASCatch Qtx Style DDS QDS ObjBrowser SUIT SUITApp STD CAF CAM LogWindow Prs Event \
+ OBJECT GLViewer VTKViewer SVTK OCCViewer SOCC PyInterp PyConsole Plot2d SPlot2d SUPERVGraph \
+ QxGraph LightApp ResExporter TOOLSGUI Session SalomeApp SALOME_SWIG SALOME_PY SALOME_PYQT
lib_LTLIBRARIES = libSalomeObject.la
-salomeinclude_HEADERS= \
- SALOME_InteractiveObject.hxx \
- Handle_SALOME_InteractiveObject.hxx \
- SALOME_AISShape.hxx \
- Handle_SALOME_AISShape.hxx \
- SALOME_AISObject.hxx \
- Handle_SALOME_AISObject.hxx \
- SALOME_ListIO.hxx \
- SALOME_ListIteratorOfListIO.hxx \
- Handle_SALOME_ListNodeOfListIO.hxx \
- SALOME_ListNodeOfListIO.hxx \
- Handle_SALOME_Filter.hxx \
- SALOME_Filter.hxx \
- Handle_SALOME_TypeFilter.hxx \
- SALOME_TypeFilter.hxx \
- SALOME_DataMapOfIOMapOfInteger.hxx \
- SALOME_DataMapIteratorOfDataMapOfIOMapOfInteger.hxx \
- Handle_SALOME_DataMapNodeOfDataMapOfIOMapOfInteger.hxx \
+salomeinclude_HEADERS = \
+ SALOME_InteractiveObject.hxx \
+ Handle_SALOME_InteractiveObject.hxx \
+ SALOME_AISShape.hxx \
+ Handle_SALOME_AISShape.hxx \
+ SALOME_AISObject.hxx \
+ Handle_SALOME_AISObject.hxx \
+ SALOME_ListIO.hxx \
+ SALOME_ListIteratorOfListIO.hxx \
+ Handle_SALOME_ListNodeOfListIO.hxx \
+ SALOME_ListNodeOfListIO.hxx \
+ Handle_SALOME_Filter.hxx \
+ SALOME_Filter.hxx \
+ Handle_SALOME_TypeFilter.hxx \
+ SALOME_TypeFilter.hxx \
+ SALOME_DataMapOfIOMapOfInteger.hxx \
+ SALOME_DataMapIteratorOfDataMapOfIOMapOfInteger.hxx \
+ SALOME_DataMapNodeOfDataMapOfIOMapOfInteger.hxx \
+ Handle_SALOME_DataMapNodeOfDataMapOfIOMapOfInteger.hxx \
SALOME_Selection.h
-dist_libSalomeObject_la_SOURCES= \
- SALOME_InteractiveObject.cxx \
- SALOME_AISShape.cxx\
- SALOME_AISObject.cxx\
- SALOME_ListIO_0.cxx \
- SALOME_ListIteratorOfListIO_0.cxx \
- SALOME_ListNodeOfListIO_0.cxx \
- SALOME_Filter.cxx \
- SALOME_TypeFilter.cxx \
- SALOME_DataMapOfIOMapOfInteger_0.cxx \
- SALOME_DataMapNodeOfDataMapOfIOMapOfInteger_0.cxx \
+dist_libSalomeObject_la_SOURCES = \
+ SALOME_InteractiveObject.cxx \
+ SALOME_AISShape.cxx \
+ SALOME_AISObject.cxx \
+ SALOME_ListIO_0.cxx \
+ SALOME_ListIteratorOfListIO_0.cxx \
+ SALOME_ListNodeOfListIO_0.cxx \
+ SALOME_Filter.cxx \
+ SALOME_TypeFilter.cxx \
+ SALOME_DataMapOfIOMapOfInteger_0.cxx \
+ SALOME_DataMapNodeOfDataMapOfIOMapOfInteger_0.cxx \
SALOME_DataMapIteratorOfDataMapOfIOMapOfInteger_0.cxx
-libSalomeObject_la_CPPFLAGS=$(QT_INCLUDES) $(CAS_CPPFLAGS)
-libSalomeObject_la_LDFLAGS=$(QT_LIBS) $(CAS_LDPATH) -lTKV3d
+libSalomeObject_la_CPPFLAGS = $(QT_INCLUDES) $(CAS_CPPFLAGS)
+libSalomeObject_la_LDFLAGS = $(QT_LIBS) $(CAS_LDPATH) -lTKV3d
-EXTRA_DIST+= \
- SALOME_AISObject.ixx \
- SALOME_AISObject.jxx \
- SALOME_AISShape.ixx \
- SALOME_AISShape.jxx \
- SALOME_Filter.ixx \
- SALOME_Filter.jxx \
- SALOME_InteractiveObject.ixx \
- SALOME_InteractiveObject.jxx \
- SALOME_TypeFilter.ixx \
- SALOME_TypeFilter.jxx \
- SALOME_DataMapNodeOfDataMapOfIOMapOfInteger.hxx
+# internal (non-distributed) headers
+EXTRA_DIST += \
+ SALOME_AISObject.ixx \
+ SALOME_AISObject.jxx \
+ SALOME_AISShape.ixx \
+ SALOME_AISShape.jxx \
+ SALOME_Filter.ixx \
+ SALOME_Filter.jxx \
+ SALOME_InteractiveObject.ixx \
+ SALOME_InteractiveObject.jxx \
+ SALOME_TypeFilter.ixx \
+ SALOME_TypeFilter.jxx
lib_LTLIBRARIES = libOCCViewer.la
-salomeinclude_HEADERS= \
- OCCViewer_AISSelector.h \
- OCCViewer_ViewManager.h \
- OCCViewer_ViewModel.h \
- OCCViewer_ViewPort3d.h \
- OCCViewer_ViewPort.h \
- OCCViewer_ViewSketcher.h \
- OCCViewer_ViewWindow.h \
- OCCViewer_VService.h \
- OCCViewer_CreateRestoreViewDlg.h \
- OCCViewer.h \
- OCCViewer_ClippingDlg.h \
- OCCViewer_AxialScaleDlg.h \
- OCCViewer_SetRotationPointDlg.h \
+salomeinclude_HEADERS = \
+ OCCViewer_AISSelector.h \
+ OCCViewer_ViewManager.h \
+ OCCViewer_ViewModel.h \
+ OCCViewer_ViewPort3d.h \
+ OCCViewer_ViewPort.h \
+ OCCViewer_ViewSketcher.h \
+ OCCViewer_ViewWindow.h \
+ OCCViewer_VService.h \
+ OCCViewer_CreateRestoreViewDlg.h \
+ OCCViewer.h \
+ OCCViewer_ClippingDlg.h \
+ OCCViewer_AxialScaleDlg.h \
+ OCCViewer_SetRotationPointDlg.h \
OCCViewer_Trihedron.h
-dist_libOCCViewer_la_SOURCES= \
- OCCViewer.cxx \
- OCCViewer_AISSelector.cxx \
- OCCViewer_ViewManager.cxx \
- OCCViewer_ViewModel.cxx \
- OCCViewer_ViewPort3d.cxx \
- OCCViewer_ViewPort.cxx \
- OCCViewer_ViewSketcher.cxx \
- OCCViewer_ViewWindow.cxx \
- OCCViewer_VService.cxx \
- OCCViewer_CreateRestoreViewDlg.cxx \
- OCCViewer_SetRotationPointDlg.cxx \
- OCCViewer_ClippingDlg.cxx \
- OCCViewer_AxialScaleDlg.cxx \
+dist_libOCCViewer_la_SOURCES = \
+ OCCViewer.cxx \
+ OCCViewer_AISSelector.cxx \
+ OCCViewer_ViewManager.cxx \
+ OCCViewer_ViewModel.cxx \
+ OCCViewer_ViewPort3d.cxx \
+ OCCViewer_ViewPort.cxx \
+ OCCViewer_ViewSketcher.cxx \
+ OCCViewer_ViewWindow.cxx \
+ OCCViewer_VService.cxx \
+ OCCViewer_CreateRestoreViewDlg.cxx \
+ OCCViewer_SetRotationPointDlg.cxx \
+ OCCViewer_ClippingDlg.cxx \
+ OCCViewer_AxialScaleDlg.cxx \
OCCViewer_Trihedron.cxx
-MOC_FILES= \
- OCCViewer_AISSelector_moc.cxx \
- OCCViewer_ViewModel_moc.cxx \
- OCCViewer_ViewPort3d_moc.cxx \
- OCCViewer_ViewPort_moc.cxx \
- OCCViewer_ViewSketcher_moc.cxx \
- OCCViewer_ViewWindow_moc.cxx \
- OCCViewer_ViewManager_moc.cxx \
- OCCViewer_CreateRestoreViewDlg_moc.cxx \
- OCCViewer_SetRotationPointDlg_moc.cxx \
- OCCViewer_ClippingDlg_moc.cxx \
+MOC_FILES = \
+ OCCViewer_AISSelector_moc.cxx \
+ OCCViewer_ViewModel_moc.cxx \
+ OCCViewer_ViewPort3d_moc.cxx \
+ OCCViewer_ViewPort_moc.cxx \
+ OCCViewer_ViewSketcher_moc.cxx \
+ OCCViewer_ViewWindow_moc.cxx \
+ OCCViewer_ViewManager_moc.cxx \
+ OCCViewer_CreateRestoreViewDlg_moc.cxx \
+ OCCViewer_SetRotationPointDlg_moc.cxx \
+ OCCViewer_ClippingDlg_moc.cxx \
OCCViewer_AxialScaleDlg_moc.cxx
-nodist_libOCCViewer_la_SOURCES= $(MOC_FILES)
+nodist_libOCCViewer_la_SOURCES = $(MOC_FILES)
-dist_salomeres_DATA = \
- resources/occ_view_back.png \
- resources/occ_view_bottom.png \
- resources/occ_view_camera_dump.png \
- resources/occ_view_clone.png \
- resources/occ_view_clipping.png \
- resources/occ_view_clipping_pressed.png \
- resources/occ_view_scaling.png \
- resources/occ_view_fitall.png \
- resources/occ_view_fitarea.png \
- resources/occ_view_front.png \
- resources/occ_view_glpan.png \
- resources/occ_view_left.png \
- resources/occ_view_pan.png \
- resources/occ_view_presets.png \
- resources/occ_view_reset.png \
- resources/occ_view_right.png \
- resources/occ_view_rotate.png \
- resources/occ_view_shoot.png \
- resources/occ_view_top.png \
- resources/occ_view_triedre.png \
- resources/occ_view_zoom.png \
+dist_salomeres_DATA = \
+ resources/occ_view_back.png \
+ resources/occ_view_bottom.png \
+ resources/occ_view_camera_dump.png \
+ resources/occ_view_clone.png \
+ resources/occ_view_clipping.png \
+ resources/occ_view_clipping_pressed.png \
+ resources/occ_view_scaling.png \
+ resources/occ_view_fitall.png \
+ resources/occ_view_fitarea.png \
+ resources/occ_view_front.png \
+ resources/occ_view_glpan.png \
+ resources/occ_view_left.png \
+ resources/occ_view_pan.png \
+ resources/occ_view_presets.png \
+ resources/occ_view_reset.png \
+ resources/occ_view_right.png \
+ resources/occ_view_rotate.png \
+ resources/occ_view_shoot.png \
+ resources/occ_view_top.png \
+ resources/occ_view_triedre.png \
+ resources/occ_view_zoom.png \
resources/occ_view_rotation_point.png
-nodist_salomeres_DATA = \
- OCCViewer_images.qm \
+nodist_salomeres_DATA = \
+ OCCViewer_images.qm \
OCCViewer_msg_en.qm
-libOCCViewer_la_CPPFLAGS=$(QT_INCLUDES) $(OGL_INCLUDES) $(CAS_CPPFLAGS) \
+libOCCViewer_la_CPPFLAGS = $(QT_INCLUDES) $(OGL_INCLUDES) $(CAS_CPPFLAGS) \
-I$(srcdir)/../SUIT -I$(srcdir)/../Qtx
-libOCCViewer_la_LDFLAGS=$(OGL_LIBS) $(QT_MT_LIBS) $(CAS_KERNEL) $(CAS_VIEWER) -lTKOpenGl
-libOCCViewer_la_LIBADD=../Qtx/libqtx.la ../SUIT/libsuit.la
+libOCCViewer_la_LDFLAGS = $(OGL_LIBS) $(QT_MT_LIBS) $(CAS_KERNEL) $(CAS_VIEWER) -lTKOpenGl
+libOCCViewer_la_LIBADD = ../Qtx/libqtx.la ../SUIT/libsuit.la
lib_LTLIBRARIES = libObjBrowser.la
-salomeinclude_HEADERS= \
+salomeinclude_HEADERS = \
OB.h \
OB_Browser.h
-# OB_ListItem.h \
- OB_ListView.h
- OB_Filter.h
+# OB_Filter.h
-dist_libObjBrowser_la_SOURCES= \
+dist_libObjBrowser_la_SOURCES = \
OB_Browser.cxx
-# OB_ListView.cxx
- OB_ListItem.cxx \
- OB_ListView.cxx \
- OB_Filter.cxx
+# OB_Filter.cxx
-MOC_FILES= \
+MOC_FILES = \
OB_Browser_moc.cxx
-# OB_ListView_moc.cxx
-
-nodist_libObjBrowser_la_SOURCES= $(MOC_FILES)
+nodist_libObjBrowser_la_SOURCES = $(MOC_FILES)
nodist_salomeres_DATA = OB_msg_en.qm
-libObjBrowser_la_CPPFLAGS=$(QT_INCLUDES) -I$(srcdir)/../Qtx
-
-libObjBrowser_la_LDFLAGS=$(QT_MT_LIBS)
-libObjBrowser_la_LIBADD= ../Qtx/libqtx.la
+libObjBrowser_la_CPPFLAGS = $(QT_INCLUDES) -I$(srcdir)/../Qtx
+libObjBrowser_la_LDFLAGS = $(QT_MT_LIBS)
+libObjBrowser_la_LIBADD = ../Qtx/libqtx.la
include $(top_srcdir)/adm_local/unix/make_common_starter.am
-lib_LTLIBRARIES= libPlot2d.la
+lib_LTLIBRARIES = libPlot2d.la
# header files
-salomeinclude_HEADERS= \
- Plot2d.h \
- Plot2d_Curve.h \
- Plot2d_FitDataDlg.h \
- Plot2d_Prs.h \
- Plot2d_SetupViewDlg.h \
- Plot2d_ViewFrame.h \
- Plot2d_ViewManager.h \
- Plot2d_ViewModel.h \
- Plot2d_ViewWindow.h \
- Plot2d_SetupCurveDlg.h \
+salomeinclude_HEADERS = \
+ Plot2d.h \
+ Plot2d_Curve.h \
+ Plot2d_FitDataDlg.h \
+ Plot2d_Prs.h \
+ Plot2d_SetupViewDlg.h \
+ Plot2d_ViewFrame.h \
+ Plot2d_ViewManager.h \
+ Plot2d_ViewModel.h \
+ Plot2d_ViewWindow.h \
+ Plot2d_SetupCurveDlg.h \
Plot2d_ToolTip.h
-dist_libPlot2d_la_SOURCES= \
- Plot2d.cxx \
- Plot2d_Curve.cxx \
- Plot2d_FitDataDlg.cxx \
- Plot2d_Prs.cxx \
- Plot2d_SetupViewDlg.cxx \
- Plot2d_ViewFrame.cxx \
- Plot2d_ViewManager.cxx \
- Plot2d_ViewModel.cxx \
- Plot2d_ViewWindow.cxx \
- Plot2d_SetupCurveDlg.cxx \
+dist_libPlot2d_la_SOURCES = \
+ Plot2d.cxx \
+ Plot2d_Curve.cxx \
+ Plot2d_FitDataDlg.cxx \
+ Plot2d_Prs.cxx \
+ Plot2d_SetupViewDlg.cxx \
+ Plot2d_ViewFrame.cxx \
+ Plot2d_ViewManager.cxx \
+ Plot2d_ViewModel.cxx \
+ Plot2d_ViewWindow.cxx \
+ Plot2d_SetupCurveDlg.cxx \
Plot2d_ToolTip.cxx
-MOC_FILES = \
- Plot2d_FitDataDlg_moc.cxx \
- Plot2d_SetupViewDlg_moc.cxx \
- Plot2d_ViewFrame_moc.cxx \
- Plot2d_ViewManager_moc.cxx \
- Plot2d_ViewModel_moc.cxx \
- Plot2d_ViewWindow_moc.cxx \
- Plot2d_SetupCurveDlg_moc.cxx \
+MOC_FILES = \
+ Plot2d_FitDataDlg_moc.cxx \
+ Plot2d_SetupViewDlg_moc.cxx \
+ Plot2d_ViewFrame_moc.cxx \
+ Plot2d_ViewManager_moc.cxx \
+ Plot2d_ViewModel_moc.cxx \
+ Plot2d_ViewWindow_moc.cxx \
+ Plot2d_SetupCurveDlg_moc.cxx \
Plot2d_ToolTip_moc.cxx
-nodist_libPlot2d_la_SOURCES= $(MOC_FILES)
+nodist_libPlot2d_la_SOURCES = $(MOC_FILES)
-dist_salomeres_DATA = \
- resources/plot2d_clone.png \
- resources/plot2d_camera_dump.png \
- resources/plot2d_fitall.png \
- resources/plot2d_fitarea.png \
- resources/plot2d_glpan.png \
- resources/plot2d_legend.png \
- resources/plot2d_linear.png \
- resources/plot2d_linear_y.png \
- resources/plot2d_lines.png \
- resources/plot2d_log.png \
- resources/plot2d_log_y.png \
- resources/plot2d_pan.png \
- resources/plot2d_points.png \
- resources/plot2d_settings.png \
- resources/plot2d_splines.png \
+dist_salomeres_DATA = \
+ resources/plot2d_clone.png \
+ resources/plot2d_camera_dump.png \
+ resources/plot2d_fitall.png \
+ resources/plot2d_fitarea.png \
+ resources/plot2d_glpan.png \
+ resources/plot2d_legend.png \
+ resources/plot2d_linear.png \
+ resources/plot2d_linear_y.png \
+ resources/plot2d_lines.png \
+ resources/plot2d_log.png \
+ resources/plot2d_log_y.png \
+ resources/plot2d_pan.png \
+ resources/plot2d_points.png \
+ resources/plot2d_settings.png \
+ resources/plot2d_splines.png \
resources/plot2d_zoom.png
-nodist_salomeres_DATA= \
- Plot2d_images.qm \
+nodist_salomeres_DATA = \
+ Plot2d_images.qm \
Plot2d_msg_en.qm
-libPlot2d_la_CPPFLAGS=$(QT_INCLUDES) $(PYTHON_INCLUDES) $(QWT_INCLUDES) \
+libPlot2d_la_CPPFLAGS = $(QT_INCLUDES) $(PYTHON_INCLUDES) $(QWT_INCLUDES) \
-I$(srcdir)/../Qtx -I$(srcdir)/../SUIT
-libPlot2d_la_LDFLAGS=$(QWT_LIBS) $(QT_MT_LIBS) ../SUIT/libsuit.la
+libPlot2d_la_LDFLAGS = $(QWT_LIBS) $(QT_MT_LIBS) ../SUIT/libsuit.la
lib_LTLIBRARIES = libPyConsole.la
-salomeinclude_HEADERS= \
+salomeinclude_HEADERS = \
PyConsole.h \
PyConsole_Console.h \
PyConsole_Editor.h \
PyConsole_Interp.h
-dist_libPyConsole_la_SOURCES= \
+dist_libPyConsole_la_SOURCES = \
PyConsole_Console.cxx \
PyConsole_Editor.cxx \
PyConsole_Interp.cxx
-MOC_FILES= \
+MOC_FILES = \
PyConsole_Editor_moc.cxx \
PyConsole_Console_moc.cxx
-nodist_libPyConsole_la_SOURCES= $(MOC_FILES)
+nodist_libPyConsole_la_SOURCES = $(MOC_FILES)
-nodist_salomeres_DATA= \
+nodist_salomeres_DATA = \
PyConsole_msg_en.qm
-libPyConsole_la_CPPFLAGS= $(PYTHON_INCLUDES) $(QT_INCLUDES) \
+libPyConsole_la_CPPFLAGS = $(PYTHON_INCLUDES) $(QT_INCLUDES) \
-I$(srcdir)/../PyInterp -I$(srcdir)/../SUIT -I$(srcdir)/../Qtx
-libPyConsole_la_LDFLAGS= $(PYTHON_LIBS) $(QT_MT_LIBS)
-libPyConsole_la_LIBADD=../Qtx/libqtx.la ../SUIT/libsuit.la ../PyInterp/libPyInterp.la
+libPyConsole_la_LDFLAGS = $(PYTHON_LIBS) $(QT_MT_LIBS)
+libPyConsole_la_LIBADD = ../Qtx/libqtx.la ../SUIT/libsuit.la ../PyInterp/libPyInterp.la
lib_LTLIBRARIES = libPyInterp.la
-salomeinclude_HEADERS= \
+salomeinclude_HEADERS = \
PyInterp.h \
PyInterp_Interp.h \
PyInterp_Dispatcher.h
-dist_libPyInterp_la_SOURCES= \
+dist_libPyInterp_la_SOURCES = \
PyInterp_Interp.cxx \
PyInterp_Dispatcher.cxx
-MOC_FILES= PyInterp_Watcher_moc.cxx
-nodist_libPyInterp_la_SOURCES= $(MOC_FILES)
+MOC_FILES = PyInterp_Watcher_moc.cxx
+nodist_libPyInterp_la_SOURCES = $(MOC_FILES)
-libPyInterp_la_CPPFLAGS= $(PYTHON_INCLUDES) $(QT_INCLUDES) \
+libPyInterp_la_CPPFLAGS = $(PYTHON_INCLUDES) $(QT_INCLUDES) \
-I$(srcdir)/../Event
-libPyInterp_la_LDFLAGS= $(PYTHON_LIBS) $(QT_MT_LIBS) ../Event/libEvent.la
+libPyInterp_la_LDFLAGS = $(PYTHON_LIBS) $(QT_MT_LIBS) ../Event/libEvent.la
# header files
#MKR: already migrated to Qt4 files
-salomeinclude_HEADERS= \
+salomeinclude_HEADERS = \
QDS.h \
QDS_CheckBox.h \
QDS_ComboBox.h \
QDS_Table.h
#MKR: already migrated to Qt4 files
-dist_libQDS_la_SOURCES= \
+dist_libQDS_la_SOURCES = \
QDS.cxx \
QDS_CheckBox.cxx \
QDS_ComboBox.cxx \
QDS_Table.cxx
#MKR: already migrated to Qt4 files
-MOC_FILES= \
- QDS_CheckBox_moc.cxx \
- QDS_ComboBox_moc.cxx \
- QDS_Datum_moc.cxx \
- QDS_LineEdit_moc.cxx \
- QDS_SpinBox_moc.cxx \
- QDS_SpinBoxDbl_moc.cxx \
- QDS_TextEdit_moc.cxx \
+MOC_FILES = \
+ QDS_CheckBox_moc.cxx \
+ QDS_ComboBox_moc.cxx \
+ QDS_Datum_moc.cxx \
+ QDS_LineEdit_moc.cxx \
+ QDS_SpinBox_moc.cxx \
+ QDS_SpinBoxDbl_moc.cxx \
+ QDS_TextEdit_moc.cxx \
QDS_RadioBox_moc.cxx
#MKR: not yet migrated to Qt4 files
# \
QDS_Table_moc.cxx
-nodist_libQDS_la_SOURCES= $(MOC_FILES)
+nodist_libQDS_la_SOURCES = $(MOC_FILES)
-# may be neccessary for the external projects or future improvements
-EXTRA_DIST+= QDS_RadioBox.cxx QDS_RadioBox.h resources/QDS_msg_en.po
+nodist_salomeres_DATA = QDS_msg_en.qm
-libQDS_la_CPPFLAGS=$(QT_INCLUDES) $(CAS_CPPFLAGS) \
+libQDS_la_CPPFLAGS = $(QT_INCLUDES) $(CAS_CPPFLAGS) \
-I$(srcdir)/../Qtx -I$(srcdir)/../DDS
-libQDS_la_LDFLAGS=$(QT_MT_LIBS) $(CAS_KERNEL)
-libQDS_la_LIBADD=../DDS/libDDS.la ../Qtx/libqtx.la
+libQDS_la_LDFLAGS = $(QT_MT_LIBS) $(CAS_KERNEL)
+libQDS_la_LIBADD = ../DDS/libDDS.la ../Qtx/libqtx.la
# header files
#VSR: already migrated to Qt4 files
-salomeinclude_HEADERS= \
+salomeinclude_HEADERS = \
Qtx.h \
QtxAction.h \
QtxActionMenuMgr.h \
# Libraries targets
-lib_LTLIBRARIES= libqtx.la
+lib_LTLIBRARIES = libqtx.la
#VSR: already migrated to Qt4 files
-dist_libqtx_la_SOURCES= \
+dist_libqtx_la_SOURCES = \
Qtx.cxx \
QtxAction.cxx \
QtxActionMenuMgr.cxx \
QtxTable.cxx
#VSR: already migrated to Qt4 files
-MOC_FILES= \
+MOC_FILES = \
QtxAction_moc.cxx \
QtxActionMenuMgr_moc.cxx \
QtxActionMgr_moc.cxx \
QtxListBox_moc.cxx \
QtxTable_moc.cxx
-nodist_libqtx_la_SOURCES= $(MOC_FILES)
+nodist_libqtx_la_SOURCES = $(MOC_FILES)
-libqtx_la_CPPFLAGS=$(QT_INCLUDES)
-
-libqtx_la_LDFLAGS=$(QT_MT_LIBS)
+libqtx_la_CPPFLAGS = $(QT_INCLUDES)
+libqtx_la_LDFLAGS = $(QT_MT_LIBS)
lib_LTLIBRARIES = libQxGraph.la
-salomeinclude_HEADERS= \
- QxGraph_ActiveItem.h \
- QxGraph_Prs.h \
- QxGraph_Canvas.h \
- QxGraph_CanvasView.h \
- QxGraph_ViewWindow.h \
- QxGraph_ViewManager.h \
- QxGraph_ViewModel.h \
- QxGraph_Def.h \
+salomeinclude_HEADERS = \
+ QxGraph_ActiveItem.h \
+ QxGraph_Prs.h \
+ QxGraph_Canvas.h \
+ QxGraph_CanvasView.h \
+ QxGraph_ViewWindow.h \
+ QxGraph_ViewManager.h \
+ QxGraph_ViewModel.h \
+ QxGraph_Def.h \
QxGraph.h
-dist_libQxGraph_la_SOURCES= \
- QxGraph_Prs.cxx \
- QxGraph_Canvas.cxx \
- QxGraph_CanvasView.cxx \
- QxGraph_ViewWindow.cxx \
- QxGraph_ViewManager.cxx \
+dist_libQxGraph_la_SOURCES = \
+ QxGraph_Prs.cxx \
+ QxGraph_Canvas.cxx \
+ QxGraph_CanvasView.cxx \
+ QxGraph_ViewWindow.cxx \
+ QxGraph_ViewManager.cxx \
QxGraph_ViewModel.cxx
-MOC_FILES= \
- QxGraph_Canvas_moc.cxx \
- QxGraph_CanvasView_moc.cxx \
- QxGraph_ViewWindow_moc.cxx \
- QxGraph_ViewManager_moc.cxx \
+MOC_FILES = \
+ QxGraph_Canvas_moc.cxx \
+ QxGraph_CanvasView_moc.cxx \
+ QxGraph_ViewWindow_moc.cxx \
+ QxGraph_ViewManager_moc.cxx \
QxGraph_ViewModel_moc.cxx
-nodist_libQxGraph_la_SOURCES= $(MOC_FILES)
+nodist_libQxGraph_la_SOURCES = $(MOC_FILES)
-dist_salomeres_DATA= \
- resources/qx_view_fitall.png \
- resources/qx_view_fitarea.png \
- resources/qx_view_glpan.png \
- resources/qx_view_pan.png \
- resources/qx_view_reset.png \
+dist_salomeres_DATA = \
+ resources/qx_view_fitall.png \
+ resources/qx_view_fitarea.png \
+ resources/qx_view_glpan.png \
+ resources/qx_view_pan.png \
+ resources/qx_view_reset.png \
resources/qx_view_zoom.png
-nodist_salomeres_DATA= \
- QxGraph_images.qm \
+nodist_salomeres_DATA = \
+ QxGraph_images.qm \
QxGraph_msg_en.qm
-libQxGraph_la_CPPFLAGS=$(QT_INCLUDES) $(CAS_CPPFLAGS) $(PYTHON_INCLUDES) $(BOOST_CPPFLAGS) \
- -I$(srcdir)/../Qtx -I$(srcdir)/../SUIT
-libQxGraph_la_LDFLAGS=$(QT_MT_LIBS) ../SUIT/libsuit.la
+libQxGraph_la_CPPFLAGS = $(QT_INCLUDES) $(CAS_CPPFLAGS) $(PYTHON_INCLUDES) $(BOOST_CPPFLAGS) \
+ -I$(srcdir)/../Qtx -I$(srcdir)/../SUIT
+libQxGraph_la_LDFLAGS = $(QT_MT_LIBS) ../SUIT/libsuit.la
include $(top_srcdir)/adm_local/unix/make_common_starter.am
-bin_PROGRAMS= ResourceExporter
+bin_PROGRAMS = ResourceExporter
-dist_ResourceExporter_SOURCES=ResourceExporter.cxx
+dist_ResourceExporter_SOURCES = ResourceExporter.cxx
-ResourceExporter_CPPFLAGS= $(QT_INCLUDES) -I$(srcdir)/../Qtx -I$(srcdir)/../SUIT
-
-ResourceExporter_LDFLAGS= $(QT_MT_LIBS)
-ResourceExporter_LDADD= ../SUIT/libsuit.la ../Qtx/libqtx.la
+ResourceExporter_CPPFLAGS = $(QT_INCLUDES) -I$(srcdir)/../Qtx -I$(srcdir)/../SUIT
+ResourceExporter_LDFLAGS = $(QT_MT_LIBS)
+ResourceExporter_LDADD = ../SUIT/libsuit.la ../Qtx/libqtx.la
include $(top_srcdir)/adm_local/unix/make_common_starter.am
-lib_LTLIBRARIES= libSalomePy.la
-dist_libSalomePy_la_SOURCES= SalomePy.cxx
+lib_LTLIBRARIES = libSalomePy.la
+dist_libSalomePy_la_SOURCES = SalomePy.cxx
-libSalomePy_la_CPPFLAGS=$(QT_INCLUDES) $(PYTHON_INCLUDES) $(VTK_INCLUDES) \
+libSalomePy_la_CPPFLAGS = $(QT_INCLUDES) $(PYTHON_INCLUDES) $(VTK_INCLUDES) \
$(OGL_INCLUDES) $(CAS_CXXFLAGS) $(BOOST_CPPFLAGS) @KERNEL_CXXFLAGS@ \
-DHAVE_CONFIG_H -I$(srcdir)/../SalomeApp -I$(srcdir)/../LightApp \
-I$(srcdir)/../Event -I$(srcdir)/../Session -I$(srcdir)/../SVTK \
-I$(srcdir)/../STD -I$(srcdir)/../VTKViewer -I$(srcdir)/../OBJECT \
@CAS_CPPFLAGS@ \
-I$(top_builddir)/salome_adm/unix @CORBA_CXXFLAGS@ @CORBA_INCLUDES@
-libSalomePy_la_LDFLAGS=$(PYTHON_LIBS) $(QT_MT_LIBS) $(VTK_LIBS) $(OGL_LIBS) \
+libSalomePy_la_LDFLAGS = $(PYTHON_LIBS) $(QT_MT_LIBS) $(VTK_LIBS) $(OGL_LIBS) \
../SalomeApp/libSalomeApp.la \
-lvtkCommonPythonD -lvtkGraphicsPythonD -lvtkImagingPythonD
######################
-# Library target
-lib_LTLIBRARIES= libSalomePyQtGUI.la
+# library target
+lib_LTLIBRARIES = libSalomePyQtGUI.la
-SIP_SRC = sipSalomePyQtGUIcmodule.cc
+# extra source files (generated by sip)
+SIP_SRC = sipAPISalomePyQtGUI.h \
+ sipSalomePyQtGUIcmodule.cc
+
+# Sip definition file
SIP_FILES = SALOME_PYQT_GUI.sip
+# extra dist files
EXTRA_DIST += $(SIP_FILES)
-salomeinclude_HEADERS = \
- SALOME_PYQT_GUI.h \
- SALOME_PYQT_PyInterp.h \
- SALOME_PYQT_Module.h
+# extra clean files
+CLEANFILES = $(SIP_SRC)
-dist_libSalomePyQtGUI_la_SOURCES= \
- SALOME_PYQT_PyInterp.cxx \
- SALOME_PYQT_Module.cxx
+# moc files (generated my moc)
+MOC_FILES = SALOME_PYQT_Module_moc.cxx
-dist_libSalomePyQtGUI_la_SOURCES: $(SIP_SRC)
-
-# moc pre-processing
-MOC_FILES= SALOME_PYQT_Module_moc.cxx
-nodist_libSalomePyQtGUI_la_SOURCES= $(MOC_FILES) $(SIP_SRC)
+# exported header files
+salomeinclude_HEADERS = \
+ SALOME_PYQT_GUI.h \
+ SALOME_PYQT_PyInterp.h \
+ SALOME_PYQT_Module.h
-libSalomePyQtGUI_la_CPPFLAGS= $(QT_INCLUDES) $(SIP_INCLUDES) $(PYTHON_INCLUDES) \
- $(CAS_CPPFLAGS) $(VTK_INCLUDES) $(OGL_INCLUDES) $(BOOST_CPPFLAGS) \
- -DHAVE_CONFIG_H @KERNEL_CXXFLAGS@ -DCALL_OLD_METHODS \
- -I$(srcdir)/../../PyInterp -I$(srcdir)/../../SalomeApp \
- -I$(srcdir)/../../SUIT -I$(srcdir)/../../Qtx -I$(srcdir)/../../LightApp \
- -I$(srcdir)/../../Plot2d -I$(srcdir)/../../OCCViewer \
- -I$(srcdir)/../../SalomeApp -I$(srcdir)/../../CAM -I$(srcdir)/../../STD \
+# library sources
+dist_libSalomePyQtGUI_la_SOURCES = \
+ SALOME_PYQT_PyInterp.cxx \
+ SALOME_PYQT_Module.cxx
+nodist_libSalomePyQtGUI_la_SOURCES = $(MOC_FILES) $(SIP_SRC)
+
+# compilation flags
+libSalomePyQtGUI_la_CPPFLAGS = $(QT_INCLUDES) $(SIP_INCLUDES) $(PYTHON_INCLUDES) \
+ $(CAS_CPPFLAGS) $(VTK_INCLUDES) $(OGL_INCLUDES) $(BOOST_CPPFLAGS) \
+ -DHAVE_CONFIG_H @KERNEL_CXXFLAGS@ -DCALL_OLD_METHODS \
+ -I$(srcdir)/../../PyInterp -I$(srcdir)/../../SalomeApp \
+ -I$(srcdir)/../../SUIT -I$(srcdir)/../../Qtx -I$(srcdir)/../../LightApp \
+ -I$(srcdir)/../../Plot2d -I$(srcdir)/../../OCCViewer \
+ -I$(srcdir)/../../SalomeApp -I$(srcdir)/../../CAM -I$(srcdir)/../../STD \
-I$(top_builddir)/salome_adm/unix @CORBA_CXXFLAGS@ @CORBA_INCLUDES@
-libSalomePyQtGUI_la_LIBADD= $(PYTHON_LIBS) $(SIP_LIBS) $(PYQT_LIBS) $(VTK_LIBS) \
- $(OGL_LIBS) ../../PyInterp/libPyInterp.la ../../SalomeApp/libSalomeApp.la \
- ../../OCCViewer/libOCCViewer.la ../../Plot2d/libPlot2d.la
-##################################
+# linkage flags
+libSalomePyQtGUI_la_LIBADD = $(PYTHON_LIBS) $(SIP_LIBS) $(PYQT_LIBS) $(VTK_LIBS) \
+ $(OGL_LIBS) ../../PyInterp/libPyInterp.la ../../SalomeApp/libSalomeApp.la \
+ ../../OCCViewer/libOCCViewer.la ../../Plot2d/libPlot2d.la
# Custom build step: generate C++ wrapping according to $(SIP_FILES)
-
$(SIP_SRC): $(SIP_FILES)
$(SIP) $(PYQT_SIPFLAGS) $<
+# extra dependency (SALOME_PYQT_Module.cxx depends on header files generated by sip)
$(dist_libSalomePyQtGUI_la_SOURCES): $(SIP_SRC)
-###################################
-
-mostlyclean-local:
- rm -f sip*
include $(top_srcdir)/adm_local/unix/make_common_starter.am
-# Sip common sources
-SIP_SRC = sipSalomePyQtSalomePyQt.cc \
+# extra source files (generated by sip)
+SIP_SRC = sipAPISalomePyQt.h \
+ sipSalomePyQtSalomePyQt.cc \
sipSalomePyQtSALOME_Selection.cc \
- sipSalomePyQtQtxAction.cc \
- sipSalomePyQtcmodule.cc
+ sipSalomePyQtQtxAction.cc \
+ sipSalomePyQtcmodule.cc
# Sip definition file
SIP_FILES = SalomePyQt.sip
-EXTRA_DIST += SalomePyQt.sip
+# extra dist files
+EXTRA_DIST += $(SIP_FILES)
-# Libraries targets
+# extra clean files
+CLEANFILES = $(SIP_SRC)
+
+# moc files (generated my moc)
MOC_FILES = SalomePyQt_moc.cxx
-COMMON_CPP_FLAGS=$(QT_INCLUDES) $(QWT_INCLUDES) $(SIP_INCLUDES) $(PYTHON_INCLUDES) \
- $(CAS_CPPFLAGS) $(VTK_INCLUDES) $(OGL_INCLUDES) $(BOOST_CPPFLAGS) \
- -DHAVE_CONFIG_H @KERNEL_CXXFLAGS@ -I$(top_builddir)/salomeadn/unix \
- -I$(top_builddir)/idl \
- -I$(srcdir)/../../SUIT -I$(srcdir)/../../CAM -I$(srcdir)/../../STD \
- -I$(srcdir)/../../Qtx -I$(srcdir)/../../SalomeApp -I$(srcdir)/../../Event \
- -I$(srcdir)/../../SalomeSession -I$(srcdir)/../../LogWindow \
- -I$(srcdir)/../../VTKViewer -I$(srcdir)/../../TOOLSGUI \
- -I$(srcdir)/../../OCCViewer -I$(srcdir)/../../Plot2d \
- -I$(srcdir)/../SALOME_PYQT_GUI -I$(srcdir)/../../PyInterp \
- -I$(srcdir)/../../LightApp -I$(srcdir)/../../ObjBrowser \
- -I$(srcdir)/../../OBJECT \
+# compilation flags
+COMMON_CPP_FLAGS = $(QT_INCLUDES) $(QWT_INCLUDES) $(SIP_INCLUDES) $(PYTHON_INCLUDES) \
+ $(CAS_CPPFLAGS) $(VTK_INCLUDES) $(OGL_INCLUDES) $(BOOST_CPPFLAGS) \
+ -DHAVE_CONFIG_H @KERNEL_CXXFLAGS@ -I$(top_builddir)/salomeadn/unix \
+ -I$(top_builddir)/idl \
+ -I$(srcdir)/../../SUIT -I$(srcdir)/../../CAM -I$(srcdir)/../../STD \
+ -I$(srcdir)/../../Qtx -I$(srcdir)/../../SalomeApp -I$(srcdir)/../../Event \
+ -I$(srcdir)/../../SalomeSession -I$(srcdir)/../../LogWindow \
+ -I$(srcdir)/../../VTKViewer -I$(srcdir)/../../TOOLSGUI \
+ -I$(srcdir)/../../OCCViewer -I$(srcdir)/../../Plot2d \
+ -I$(srcdir)/../SALOME_PYQT_GUI -I$(srcdir)/../../PyInterp \
+ -I$(srcdir)/../../LightApp -I$(srcdir)/../../ObjBrowser \
+ -I$(srcdir)/../../OBJECT \
-I$(top_builddir)/salome_adm/unix @CORBA_CXXFLAGS@ @CORBA_INCLUDES@
-COMMON_LIBS=$(PYTHON_LIBS) $(SIP_LIBS) $(PYQT_LIBS) $(VTK_LIBS) $(QWT_LIBS) \
- $(OGL_LIBS) ../../SUIT/libsuit.la ../../CAM/libCAM.la ../../STD/libstd.la \
- ../../Qtx/libqtx.la ../../SalomeApp/libSalomeApp.la ../../Event/libEvent.la \
- ../../Session/libSalomeSession.la ../../LogWindow/libLogWindow.la \
- ../../VTKViewer/libVTKViewer.la ../../TOOLSGUI/libToolsGUI.la \
- ../SALOME_PYQT_GUI/libSalomePyQtGUI.la ../../OCCViewer/libOCCViewer.la \
+# linkage flags
+COMMON_LIBS = $(PYTHON_LIBS) $(SIP_LIBS) $(PYQT_LIBS) $(VTK_LIBS) $(QWT_LIBS) \
+ $(OGL_LIBS) ../../SUIT/libsuit.la ../../CAM/libCAM.la ../../STD/libstd.la \
+ ../../Qtx/libqtx.la ../../SalomeApp/libSalomeApp.la ../../Event/libEvent.la \
+ ../../Session/libSalomeSession.la ../../LogWindow/libLogWindow.la \
+ ../../VTKViewer/libVTKViewer.la ../../TOOLSGUI/libToolsGUI.la \
+ ../SALOME_PYQT_GUI/libSalomePyQtGUI.la ../../OCCViewer/libOCCViewer.la \
../../Plot2d/libPlot2d.la
+# libraries targets
lib_LTLIBRARIES = libSalomePyQt.la
-dist_libSalomePyQt_la_SOURCES= SalomePyQt.cxx
-nodist_libSalomePyQt_la_SOURCES= $(MOC_FILES) $(SIP_SRC)
+
+# library sources / rules
+dist_libSalomePyQt_la_SOURCES = SalomePyQt.cxx
+nodist_libSalomePyQt_la_SOURCES = $(MOC_FILES) $(SIP_SRC)
libSalomePyQt_la_CPPFLAGS = $(COMMON_CPP_FLAGS)
libSalomePyQt_la_LIBADD = $(COMMON_LIBS)
-# Custom build step: generate C++ wrapping according to $(SIP_FILES)
+# custom build step: generate C++ wrapping according to $(SIP_FILES)
$(SIP_SRC): $(SIP_FILES)
$(SIP) $(PYQT_SIPFLAGS) $<
-install-exec-hook: $(libdir)/SalomePyQt.so
-$(libdir)/SalomePyQt.so:
- (cd $(libdir); ln -s libSalomePyQt.so SalomePyQt.so;)
+# custom install step: create symbolic link
+install-exec-hook:
+ (cd $(DESTDIR)$(libdir); ln -sf libSalomePyQt.so SalomePyQt.so)
-mostlyclean-local:
- rm -f sip*
+# custom uninstall step: remove symbolic link
+uninstall-hook:
+ rm -f $(DESTDIR)$(libdir)/SalomePyQt.so
#
# The file libSALOME_Swig.py will be installed in the
# <prefix>/lib/python<version>/site-package/salome folder.
-# The library libSALOME_Swigcmodule.so will be installed in
+# The library _libSALOME_Swig.so will be installed in
# the <prefix>/lib/salome folder.
#
-# this option puts it to dist
-#BUILT_SOURCES = swig_wrap.cpp
-
SWIG_FLAGS = @SWIG_FLAGS@ -I$(srcdir)
SWIG_SOURCES = libSALOME_Swig.i
-nodist_pkgpython_DATA = libSALOME_Swig.py
+nodist_salomepython_PYTHON = libSALOME_Swig.py
libSALOME_Swig.py: swig_wrap.cpp
# library
-lib_LTLIBRARIES = libSALOME_Swigcmodule.la
-libSALOME_Swigcmodule_la_SOURCES = $(BUILT_SOURCES) $(SWIG_SOURCES) SALOMEGUI_Swig.cxx
-nodist_libSALOME_Swigcmodule_la_SOURCES = swig_wrap.cpp
-salomeinclude_HEADERS= SALOMEGUI_Swig.hxx SALOMEGUI_Swig.i
-
-libSALOME_Swigcmodule_la_CPPFLAGS =\
- $(QT_INCLUDES) $(QWT_INCLUDES) $(PYTHON_INCLUDES) $(CAS_CPPFLAGS) $(VTK_INCLUDES) \
- $(OGL_INCLUDES) $(BOOST_CPPFLAGS) -DHAVE_CONFIG_H @KERNEL_CXXFLAGS@ \
- -I$(top_builddir)/salome_adm/unix -I$(top_builddir)/idl \
- -I$(srcdir)/../SalomeApp -I$(srcdir)/../Qtx -I$(srcdir)/../SUIT \
- -I$(srcdir)/../ObjBrowser -I$(srcdir)/../LightApp -I$(srcdir)/../SOCC \
- -I$(srcdir)/../SVTK -I$(srcdir)/../Event -I$(srcdir)/../OBJECT \
- -I$(srcdir)/../CAM -I$(srcdir)/../STD -I$(srcdir)/../OCCViewer \
- -I$(srcdir)/../Prs -I$(srcdir)/../VTKViewer -I$(srcdir)/../SPlot2d \
- -I$(srcdir)/../Plot2d \
+lib_LTLIBRARIES = _libSALOME_Swig.la
+_libSALOME_Swig_la_SOURCES = $(SWIG_SOURCES) SALOMEGUI_Swig.cxx
+nodist__libSALOME_Swig_la_SOURCES = swig_wrap.cpp
+salomeinclude_HEADERS = $(SWIG_SOURCES) SALOMEGUI_Swig.hxx SALOMEGUI_Swig.i
+
+_libSALOME_Swig_la_CPPFLAGS = \
+ $(QT_INCLUDES) $(QWT_INCLUDES) $(PYTHON_INCLUDES) $(CAS_CPPFLAGS) $(VTK_INCLUDES) \
+ $(OGL_INCLUDES) $(BOOST_CPPFLAGS) -DHAVE_CONFIG_H @KERNEL_CXXFLAGS@ \
+ -I$(top_builddir)/salome_adm/unix -I$(top_builddir)/idl \
+ -I$(srcdir)/../SalomeApp -I$(srcdir)/../Qtx -I$(srcdir)/../SUIT \
+ -I$(srcdir)/../ObjBrowser -I$(srcdir)/../LightApp -I$(srcdir)/../SOCC \
+ -I$(srcdir)/../SVTK -I$(srcdir)/../Event -I$(srcdir)/../OBJECT \
+ -I$(srcdir)/../CAM -I$(srcdir)/../STD -I$(srcdir)/../OCCViewer \
+ -I$(srcdir)/../Prs -I$(srcdir)/../VTKViewer -I$(srcdir)/../SPlot2d \
+ -I$(srcdir)/../Plot2d \
@CORBA_CXXFLAGS@ @CORBA_INCLUDES@
-libSALOME_Swigcmodule_la_LDFLAGS = -module
-libSALOME_Swigcmodule_la_LIBADD = \
- ../SalomeApp/libSalomeApp.la \
+_libSALOME_Swig_la_LDFLAGS = -module
+_libSALOME_Swig_la_LIBADD = \
+ ../SalomeApp/libSalomeApp.la \
@PYTHON_LIBS@
swig_wrap.cpp : $(SWIG_SOURCES)
$(SWIG) $(SWIG_FLAGS) -o $@ $<
-CLEANFILES = swig_wrap.cpp
+CLEANFILES = swig_wrap.cpp libSALOME_Swig.py
#
# ===============================================================
#
# Scripts to be installed.
-dist_salomescript_DATA= \
- examplevtk1.py \
- test_table.py \
- test_big_table.py \
- test_many_objects.py \
- test_remove_ref.py \
- libSALOME_Swig.py
-
-nodist_salomescript_DATA= \
- supervisionexample.py \
+dist_salomescript_DATA = \
+ examplevtk1.py \
+ test_table.py \
+ test_big_table.py \
+ test_many_objects.py \
+ test_remove_ref.py
+
+nodist_salomescript_DATA = \
+ supervisionexample.py \
supervisiongeomexample.py
-EXTRA_DIST+= \
- supervisionexample.py.in \
- supervisiongeomexample.py.in
-
-sharedpkgpython_PYTHON= SALOMEGUI_shared_modules.py
-
-install-exec-hook: $(libdir)/_libSALOME_Swig.so
-
-$(libdir)/_libSALOME_Swig.so:
- (cd $(libdir); ln -sf libSALOME_Swigcmodule.so _libSALOME_Swig.so;)
+sharedpkgpython_PYTHON = SALOMEGUI_shared_modules.py
include $(top_srcdir)/adm_local/unix/make_common_starter.am
-lib_LTLIBRARIES=libSOCC.la
+lib_LTLIBRARIES = libSOCC.la
-salomeinclude_HEADERS= \
- SOCC.h \
- SOCC_ViewModel.h \
- SOCC_Prs.h \
+salomeinclude_HEADERS = \
+ SOCC.h \
+ SOCC_ViewModel.h \
+ SOCC_Prs.h \
SOCC_ViewWindow.h
-dist_libSOCC_la_SOURCES= \
- SOCC_ViewModel.cxx \
- SOCC_Prs.cxx \
+dist_libSOCC_la_SOURCES = \
+ SOCC_ViewModel.cxx \
+ SOCC_Prs.cxx \
SOCC_ViewWindow.cxx
-MOC_FILES= \
- SOCC_ViewModel_moc.cxx \
+MOC_FILES = \
+ SOCC_ViewModel_moc.cxx \
SOCC_ViewWindow_moc.cxx
-nodist_libSOCC_la_SOURCES= $(MOC_FILES)
+nodist_libSOCC_la_SOURCES = $(MOC_FILES)
-libSOCC_la_CPPFLAGS=$(QT_INCLUDES) $(CAS_CPPFLAGS) $(BOOST_CPPFLAGS) \
- -I$(srcdir)/../SUIT -I$(srcdir)/../OBJECT -I$(srcdir)/../Prs \
- -I$(srcdir)/../OCCViewer -I$(srcdir)/../Qtx
+libSOCC_la_CPPFLAGS = $(QT_INCLUDES) $(CAS_CPPFLAGS) $(BOOST_CPPFLAGS) \
+ -I$(srcdir)/../SUIT -I$(srcdir)/../OBJECT -I$(srcdir)/../Prs \
+ -I$(srcdir)/../OCCViewer -I$(srcdir)/../Qtx
-libSOCC_la_LDFLAGS=$(QT_MT_LIBS)
-libSOCC_la_LIBADD=../Qtx/libqtx.la ../SUIT/libsuit.la ../OBJECT/libSalomeObject.la \
- ../Prs/libSalomePrs.la ../OCCViewer/libOCCViewer.la
+libSOCC_la_LDFLAGS = $(QT_MT_LIBS)
+libSOCC_la_LIBADD = ../Qtx/libqtx.la ../SUIT/libsuit.la ../OBJECT/libSalomeObject.la \
+ ../Prs/libSalomePrs.la ../OCCViewer/libOCCViewer.la
lib_LTLIBRARIES = libSPlot2d.la
-salomeinclude_HEADERS = \
- SPlot2d.h \
- SPlot2d_Curve.h \
- SPlot2d_Prs.h \
- SPlot2d_ViewModel.h \
+salomeinclude_HEADERS = \
+ SPlot2d.h \
+ SPlot2d_Curve.h \
+ SPlot2d_Prs.h \
+ SPlot2d_ViewModel.h \
SPlot2d_ViewWindow.h
-dist_libSPlot2d_la_SOURCES = \
- SPlot2d_Curve.cxx \
- SPlot2d_Prs.cxx \
- SPlot2d_ViewModel.cxx \
+dist_libSPlot2d_la_SOURCES = \
+ SPlot2d_Curve.cxx \
+ SPlot2d_Prs.cxx \
+ SPlot2d_ViewModel.cxx \
SPlot2d_ViewWindow.cxx
-MOC_FILES = \
- SPlot2d_ViewModel_moc.cxx \
+MOC_FILES = \
+ SPlot2d_ViewModel_moc.cxx \
SPlot2d_ViewWindow_moc.cxx
nodist_libSPlot2d_la_SOURCES = $(MOC_FILES)
-libSPlot2d_la_CPPFLAGS=$(QT_INCLUDES) $(CAS_CPPFLAGS) $(QWT_INCLUDES) $(BOOST_CPPFLAGS) \
- -I$(srcdir)/../Qtx -I$(srcdir)/../SUIT -I$(srcdir)/../Plot2d -I$(srcdir)/../Prs \
- -I$(srcdir)/../OBJECT
-libSPlot2d_la_LDFLAGS=$(QT_MT_LIBS) $(QWT_LIBS) ../SUIT/libsuit.la ../Plot2d/libPlot2d.la ../Prs/libSalomePrs.la
+libSPlot2d_la_CPPFLAGS = $(QT_INCLUDES) $(CAS_CPPFLAGS) $(QWT_INCLUDES) $(BOOST_CPPFLAGS) \
+ -I$(srcdir)/../Qtx -I$(srcdir)/../SUIT -I$(srcdir)/../Plot2d \
+ -I$(srcdir)/../Prs -I$(srcdir)/../OBJECT
+libSPlot2d_la_LDFLAGS = $(QT_MT_LIBS) $(QWT_LIBS) ../SUIT/libsuit.la ../Plot2d/libPlot2d.la ../Prs/libSalomePrs.la
lib_LTLIBRARIES = libstd.la
-salomeinclude_HEADERS= \
+salomeinclude_HEADERS = \
STD.h \
STD_Application.h \
STD_MDIDesktop.h \
STD_SDIDesktop.h \
STD_TabDesktop.h
-dist_libstd_la_SOURCES= \
+dist_libstd_la_SOURCES = \
STD_Application.cxx \
STD_MDIDesktop.cxx \
STD_SDIDesktop.cxx \
STD_TabDesktop.cxx
-MOC_FILES= \
+MOC_FILES = \
STD_Application_moc.cxx \
STD_MDIDesktop_moc.cxx \
STD_SDIDesktop_moc.cxx \
STD_TabDesktop_moc.cxx
-nodist_libstd_la_SOURCES= $(MOC_FILES)
+nodist_libstd_la_SOURCES = $(MOC_FILES)
-dist_salomeres_DATA= \
+dist_salomeres_DATA = \
resources/cascade.png \
resources/close.png \
resources/copy.png \
resources/vtile.png \
resources/std.ini
-nodist_salomeres_DATA= \
+nodist_salomeres_DATA = \
STD_images.qm \
STD_msg_en.qm
-libstd_la_CPPFLAGS=$(QT_INCLUDES) -I$(srcdir)/../SUIT -I$(srcdir)/../Qtx
-libstd_la_LDFLAGS=$(QT_MT_LIBS)
-libstd_la_LIBADD=../Qtx/libqtx.la ../SUIT/libsuit.la
+libstd_la_CPPFLAGS = $(QT_INCLUDES) -I$(srcdir)/../SUIT -I$(srcdir)/../Qtx
+libstd_la_LDFLAGS = $(QT_MT_LIBS)
+libstd_la_LIBADD = ../Qtx/libqtx.la ../SUIT/libsuit.la
lib_LTLIBRARIES = libsuit.la
-salomeinclude_HEADERS= \
+salomeinclude_HEADERS = \
SUIT.h \
SUIT_Accel.h \
SUIT_ActionOperation.h \
SUIT_ViewModel.h \
SUIT_ViewWindow.h
-dist_libsuit_la_SOURCES= \
+dist_libsuit_la_SOURCES = \
SUIT_Accel.cxx \
SUIT_ActionOperation.cxx \
SUIT_Application.cxx \
SUIT_ViewModel.cxx \
SUIT_ViewWindow.cxx
-MOC_FILES= \
+MOC_FILES = \
SUIT_Accel_moc.cxx \
SUIT_ActionOperation_moc.cxx \
SUIT_Application_moc.cxx \
SUIT_ViewModel_moc.cxx \
SUIT_ViewWindow_moc.cxx
-nodist_libsuit_la_SOURCES=$(MOC_FILES)
+nodist_libsuit_la_SOURCES = $(MOC_FILES)
nodist_salomeres_DATA = \
SUIT_msg_en.qm
-libsuit_la_CPPFLAGS=$(QT_INCLUDES) -I$(srcdir)/../Qtx -I$(srcdir)/../ObjBrowser
-libsuit_la_LDFLAGS=$(QT_MT_LIBS)
-libsuit_la_LIBADD=../Qtx/libqtx.la ../ObjBrowser/libObjBrowser.la
+libsuit_la_CPPFLAGS = $(QT_INCLUDES) -I$(srcdir)/../Qtx -I$(srcdir)/../ObjBrowser
+libsuit_la_LDFLAGS = $(QT_MT_LIBS)
+libsuit_la_LIBADD = ../Qtx/libqtx.la ../ObjBrowser/libObjBrowser.la
lib_LTLIBRARIES = libSUITApp.la
-salomeinclude_HEADERS= \
+salomeinclude_HEADERS = \
SUITApp_Application.h
-dist_libSUITApp_la_SOURCES= \
+dist_libSUITApp_la_SOURCES = \
SUITApp.cxx \
SUITApp_Application.cxx
-MOC_FILES= \
+MOC_FILES = \
SUITApp_Application_moc.cxx
-nodist_libSUITApp_la_SOURCES= $(MOC_FILES)
+nodist_libSUITApp_la_SOURCES = $(MOC_FILES)
-nodist_salomeres_DATA= SUITApp_msg_en.qm
+nodist_salomeres_DATA = SUITApp_msg_en.qm
-libSUITApp_la_CPPFLAGS=$(QT_INCLUDES) $(PYTHON_INCLUDES) \
- -I$(srcdir)/../SUIT -I$(srcdir)/../Qtx -I$(srcdir)/../Style
+libSUITApp_la_CPPFLAGS = $(QT_INCLUDES) $(PYTHON_INCLUDES) \
+ -I$(srcdir)/../SUIT -I$(srcdir)/../Qtx -I$(srcdir)/../Style
-libSUITApp_la_LDFLAGS=$(QT_MT_LIBS)
-libSUITApp_la_LIBADD=../Qtx/libqtx.la ../SUIT/libsuit.la ../Style/libSalomeStyle.la
+libSUITApp_la_LDFLAGS = $(QT_MT_LIBS)
+libSUITApp_la_LIBADD = ../Qtx/libqtx.la ../SUIT/libsuit.la ../Style/libSalomeStyle.la
if ENABLE_PYCONSOLE
-libSUITApp_la_LDFLAGS+= -Xlinker -export-dynamic $(PYTHON_LIBS)
+libSUITApp_la_LDFLAGS += -Xlinker -export-dynamic $(PYTHON_LIBS)
endif
# Executable
-bin_PROGRAMS= SUITApp
+bin_PROGRAMS = SUITApp
-dist_SUITApp_SOURCES=SUITApp.cxx
+dist_SUITApp_SOURCES = SUITApp.cxx
-SUITApp_CPPFLAGS=$(QT_INCLUDES) $(PYTHON_INCLUDES) \
- -I$(srcdir)/../SUIT -I$(srcdir)/../Qtx -I$(srcdir)/../Style
+SUITApp_CPPFLAGS = $(QT_INCLUDES) $(PYTHON_INCLUDES) \
+ -I$(srcdir)/../SUIT -I$(srcdir)/../Qtx -I$(srcdir)/../Style
-SUITApp_LDADD= libSUITApp.la ../Qtx/libqtx.la ../SUIT/libsuit.la ../Style/libSalomeStyle.la
+SUITApp_LDADD = libSUITApp.la ../Qtx/libqtx.la ../SUIT/libsuit.la ../Style/libSalomeStyle.la
lib_LTLIBRARIES = libSUPERVGraph.la
-salomeinclude_HEADERS= \
- SUPERVGraph_ViewFrame.h \
- SUPERVGraph_ViewManager.h \
- SUPERVGraph_ViewModel.h \
+salomeinclude_HEADERS = \
+ SUPERVGraph_ViewFrame.h \
+ SUPERVGraph_ViewManager.h \
+ SUPERVGraph_ViewModel.h \
SUPERVGraph.h
-dist_libSUPERVGraph_la_SOURCES= \
- SUPERVGraph.cxx \
- SUPERVGraph_ViewFrame.cxx \
- SUPERVGraph_ViewManager.cxx \
+dist_libSUPERVGraph_la_SOURCES = \
+ SUPERVGraph.cxx \
+ SUPERVGraph_ViewFrame.cxx \
+ SUPERVGraph_ViewManager.cxx \
SUPERVGraph_ViewModel.cxx
-MOC_FILES= \
- SUPERVGraph_moc.cxx \
- SUPERVGraph_ViewFrame_moc.cxx \
- SUPERVGraph_ViewManager_moc.cxx \
+MOC_FILES = \
+ SUPERVGraph_moc.cxx \
+ SUPERVGraph_ViewFrame_moc.cxx \
+ SUPERVGraph_ViewManager_moc.cxx \
SUPERVGraph_ViewModel_moc.cxx
-nodist_libSUPERVGraph_la_SOURCES= $(MOC_FILES)
+nodist_libSUPERVGraph_la_SOURCES = $(MOC_FILES)
-dist_salomeres_DATA= \
- resources/superv_view_pan.png \
+dist_salomeres_DATA = \
+ resources/superv_view_pan.png \
resources/superv_view_reset.png
-nodist_salomeres_DATA= \
- SUPERVGraph_images.qm \
+nodist_salomeres_DATA = \
+ SUPERVGraph_images.qm \
SUPERVGraph_msg_en.qm
-libSUPERVGraph_la_CPPFLAGS=$(QT_INCLUDES) $(CAS_CPPFLAGS) $(PYTHON_INCLUDES) $(BOOST_CPPFLAGS) \
- -I$(srcdir)/../Qtx -I$(srcdir)/../SUIT -I$(srcdir)/../OBJECT
-libSUPERVGraph_la_LDFLAGS=$(QT_MT_LIBS) ../SUIT/libsuit.la
+libSUPERVGraph_la_CPPFLAGS = $(QT_INCLUDES) $(CAS_CPPFLAGS) $(PYTHON_INCLUDES) $(BOOST_CPPFLAGS) \
+ -I$(srcdir)/../Qtx -I$(srcdir)/../SUIT -I$(srcdir)/../OBJECT
+libSUPERVGraph_la_LDFLAGS = $(QT_MT_LIBS) ../SUIT/libsuit.la
lib_LTLIBRARIES = libSVTK.la
-salomeinclude_HEADERS= \
- SVTK.h \
- SVTK_Prs.h \
- SVTK_Actor.h \
- SALOME_Actor.h \
- SVTK_RectPicker.h \
- SVTK_DeviceActor.h \
- SVTK_DialogBase.h \
- SVTK_FontWidget.h \
- SVTK_CubeAxesActor2D.h \
- SVTK_Functor.h \
- SVTK_MainWindow.h \
- SVTK_View.h \
- SVTK_ViewManager.h \
- SVTK_ViewModel.h \
- SVTK_ViewWindow.h \
- SVTK_Renderer.h \
- SVTK_InteractorStyle.h \
- SVTK_RenderWindowInteractor.h \
- SVTK_GenericRenderWindowInteractor.h \
- SVTK_Selector.h \
- SVTK_Selection.h \
- SVTK_SelectionEvent.h \
- SVTK_SpaceMouse.h \
- SVTK_Event.h \
- SVTK_ViewModelBase.h \
- SVTK_SetRotationPointDlg.h \
+salomeinclude_HEADERS = \
+ SVTK.h \
+ SVTK_Prs.h \
+ SVTK_Actor.h \
+ SALOME_Actor.h \
+ SVTK_RectPicker.h \
+ SVTK_DeviceActor.h \
+ SVTK_DialogBase.h \
+ SVTK_FontWidget.h \
+ SVTK_CubeAxesActor2D.h \
+ SVTK_Functor.h \
+ SVTK_MainWindow.h \
+ SVTK_View.h \
+ SVTK_ViewManager.h \
+ SVTK_ViewModel.h \
+ SVTK_ViewWindow.h \
+ SVTK_Renderer.h \
+ SVTK_InteractorStyle.h \
+ SVTK_RenderWindowInteractor.h \
+ SVTK_GenericRenderWindowInteractor.h \
+ SVTK_Selector.h \
+ SVTK_Selection.h \
+ SVTK_SelectionEvent.h \
+ SVTK_SpaceMouse.h \
+ SVTK_Event.h \
+ SVTK_ViewModelBase.h \
+ SVTK_SetRotationPointDlg.h \
SVTK_Extension.h
-dist_libSVTK_la_SOURCES= \
- SVTK_Prs.cxx \
- SVTK_Actor.cxx \
- SALOME_Actor.cxx \
- SVTK_RectPicker.cxx \
- SVTK_DeviceActor.cxx \
- SVTK_CubeAxesActor2D.cxx \
- SVTK_NonIsometricDlg.cxx \
- SVTK_UpdateRateDlg.cxx \
- SVTK_CubeAxesDlg.cxx \
- SVTK_DialogBase.cxx \
- SVTK_FontWidget.cxx \
- SVTK_Trihedron.cxx \
- SVTK_MainWindow.cxx \
- SVTK_View.cxx \
- SVTK_ViewManager.cxx \
- SVTK_ViewModel.cxx \
- SVTK_Renderer.cxx \
- SVTK_ViewWindow.cxx \
- SVTK_InteractorStyle.cxx \
- SVTK_RenderWindowInteractor.cxx \
- SVTK_GenericRenderWindowInteractor.cxx \
- SVTK_SpaceMouse.cxx \
- SVTK_Selector.cxx \
- SVTK_SetRotationPointDlg.cxx \
+dist_libSVTK_la_SOURCES = \
+ SVTK_Prs.cxx \
+ SVTK_Actor.cxx \
+ SALOME_Actor.cxx \
+ SVTK_RectPicker.cxx \
+ SVTK_DeviceActor.cxx \
+ SVTK_CubeAxesActor2D.cxx \
+ SVTK_NonIsometricDlg.cxx \
+ SVTK_UpdateRateDlg.cxx \
+ SVTK_CubeAxesDlg.cxx \
+ SVTK_DialogBase.cxx \
+ SVTK_FontWidget.cxx \
+ SVTK_Trihedron.cxx \
+ SVTK_MainWindow.cxx \
+ SVTK_View.cxx \
+ SVTK_ViewManager.cxx \
+ SVTK_ViewModel.cxx \
+ SVTK_Renderer.cxx \
+ SVTK_ViewWindow.cxx \
+ SVTK_InteractorStyle.cxx \
+ SVTK_RenderWindowInteractor.cxx \
+ SVTK_GenericRenderWindowInteractor.cxx \
+ SVTK_SpaceMouse.cxx \
+ SVTK_Selector.cxx \
+ SVTK_SetRotationPointDlg.cxx \
SVTK_Extension.cxx
-EXTRA_DIST+= SVTK_SelectorDef.h SVTK_Trihedron.h
+# internal headers
+EXTRA_DIST += SVTK_SelectorDef.h SVTK_Trihedron.h
-MOC_FILES= \
- SVTK_GenericRenderWindowInteractor_moc.cxx \
- SVTK_RenderWindowInteractor_moc.cxx \
- SVTK_NonIsometricDlg_moc.cxx \
- SVTK_UpdateRateDlg_moc.cxx \
- SVTK_CubeAxesDlg_moc.cxx \
- SVTK_FontWidget_moc.cxx \
- SVTK_DialogBase_moc.cxx \
- SVTK_ViewModelBase_moc.cxx \
- SVTK_ViewManager_moc.cxx \
- SVTK_ViewWindow_moc.cxx \
- SVTK_MainWindow_moc.cxx \
- SVTK_ViewModel_moc.cxx \
- SVTK_View_moc.cxx \
+MOC_FILES = \
+ SVTK_GenericRenderWindowInteractor_moc.cxx \
+ SVTK_RenderWindowInteractor_moc.cxx \
+ SVTK_NonIsometricDlg_moc.cxx \
+ SVTK_UpdateRateDlg_moc.cxx \
+ SVTK_CubeAxesDlg_moc.cxx \
+ SVTK_FontWidget_moc.cxx \
+ SVTK_DialogBase_moc.cxx \
+ SVTK_ViewModelBase_moc.cxx \
+ SVTK_ViewManager_moc.cxx \
+ SVTK_ViewWindow_moc.cxx \
+ SVTK_MainWindow_moc.cxx \
+ SVTK_ViewModel_moc.cxx \
+ SVTK_View_moc.cxx \
SVTK_SetRotationPointDlg_moc.cxx
-nodist_libSVTK_la_SOURCES= $(MOC_FILES)
+nodist_libSVTK_la_SOURCES = $(MOC_FILES)
-dist_salomeres_DATA=\
- resources/vtk_view_graduated_axes.png \
- resources/vtk_view_scaling.png \
- resources/vtk_view_update_rate.png \
+dist_salomeres_DATA = \
+ resources/vtk_view_graduated_axes.png \
+ resources/vtk_view_scaling.png \
+ resources/vtk_view_update_rate.png \
resources/vtk_view_rotation_point.png
-nodist_salomeres_DATA= \
- SVTK_msg_en.qm \
+nodist_salomeres_DATA = \
+ SVTK_msg_en.qm \
SVTK_images.qm
-libSVTK_la_CPPFLAGS= \
- $(QT_INCLUDES) \
- $(CAS_CPPFLAGS) \
- $(VTK_INCLUDES) \
- $(BOOST_CPPFLAGS) \
- -I$(srcdir)/../Qtx -I$(srcdir)/../SUIT -I$(srcdir)/../OBJECT -I$(srcdir)/../Prs \
+libSVTK_la_CPPFLAGS = \
+ $(QT_INCLUDES) \
+ $(CAS_CPPFLAGS) \
+ $(VTK_INCLUDES) \
+ $(BOOST_CPPFLAGS) \
+ -I$(srcdir)/../Qtx \
+ -I$(srcdir)/../SUIT \
+ -I$(srcdir)/../OBJECT \
+ -I$(srcdir)/../Prs \
-I$(srcdir)/../VTKViewer
-libSVTK_la_LDFLAGS= \
- $(QT_MT_LIBS) \
- $(CAS_KERNEL) $(CAS_VIEWER) \
+libSVTK_la_LDFLAGS = \
+ $(QT_MT_LIBS) \
+ $(CAS_KERNEL) $(CAS_VIEWER) \
$(VTK_LIBS) $(OGL_LIBS)
-libSVTK_la_LIBADD= ../Qtx/libqtx.la ../SUIT/libsuit.la ../OBJECT/libSalomeObject.la \
- ../Prs/libSalomePrs.la ../VTKViewer/libVTKViewer.la
+libSVTK_la_LIBADD = ../Qtx/libqtx.la ../SUIT/libsuit.la ../OBJECT/libSalomeObject.la \
+ ../Prs/libSalomePrs.la ../VTKViewer/libVTKViewer.la
# Executable
bin_PROGRAMS = SVTK
-dist_SVTK_SOURCES= SVTK.cxx
+dist_SVTK_SOURCES = SVTK.cxx
-SVTK_CPPFLAGS=$(libSVTK_la_CPPFLAGS)
-SVTK_LDFLAGS=$(libSVTK_la_LDFLAGS)
-SVTK_LDADD=libSVTK.la $(libSVTK_la_LIBADD)
+SVTK_CPPFLAGS = $(libSVTK_la_CPPFLAGS)
+SVTK_LDFLAGS = $(libSVTK_la_LDFLAGS)
+SVTK_LDADD = libSVTK.la $(libSVTK_la_LIBADD)
if CPPUNIT_IS_OK
if GUI_ENABLE_CORBA
- SUBDIRS=Test
+ SUBDIRS = Test
endif
endif
-lib_LTLIBRARIES= libSalomeApp.la
+lib_LTLIBRARIES = libSalomeApp.la
-salomeinclude_HEADERS= \
- SalomeApp.h \
- SalomeApp_Application.h \
- SalomeApp_DataModel.h \
- SalomeApp_DataObject.h \
- SalomeApp_LoadStudiesDlg.h \
- SalomeApp_Module.h \
- SalomeApp_Study.h \
- SalomeApp_ExceptionHandler.h \
- SalomeApp_EventFilter.h \
- SalomeApp_Tools.h \
- SalomeApp_ImportOperation.h \
- SalomeApp_Filter.h \
- SalomeApp_TypeFilter.h \
- SalomeApp_StudyPropertiesDlg.h \
- SalomeApp_CheckFileDlg.h \
- SalomeApp_VisualState.h \
+salomeinclude_HEADERS = \
+ SalomeApp.h \
+ SalomeApp_Application.h \
+ SalomeApp_DataModel.h \
+ SalomeApp_DataObject.h \
+ SalomeApp_LoadStudiesDlg.h \
+ SalomeApp_Module.h \
+ SalomeApp_Study.h \
+ SalomeApp_ExceptionHandler.h \
+ SalomeApp_EventFilter.h \
+ SalomeApp_PyInterp.h \
+ SalomeApp_Tools.h \
+ SalomeApp_ImportOperation.h \
+ SalomeApp_Filter.h \
+ SalomeApp_TypeFilter.h \
+ SalomeApp_StudyPropertiesDlg.h \
+ SalomeApp_CheckFileDlg.h \
+ SalomeApp_VisualState.h \
SalomeApp_ExitDlg.h
-dist_libSalomeApp_la_SOURCES= \
- SalomeApp_Module.cxx \
- SalomeApp_Application.cxx \
- SalomeApp_DataModel.cxx \
- SalomeApp_DataObject.cxx \
- SalomeApp_LoadStudiesDlg.cxx \
- SalomeApp_Study.cxx \
- SalomeApp_ExceptionHandler.cxx \
- SalomeApp_EventFilter.cxx \
- SalomeApp_PyInterp.cxx \
- SalomeApp_Tools.cxx \
- SalomeApp_ImportOperation.cxx \
- SalomeApp_Filter.cxx \
- SalomeApp_TypeFilter.cxx \
- SalomeApp_StudyPropertiesDlg.cxx \
- SalomeApp_ListView.cxx \
- SalomeApp_CheckFileDlg.cxx \
- SalomeApp_VisualState.cxx \
+dist_libSalomeApp_la_SOURCES = \
+ SalomeApp_Module.cxx \
+ SalomeApp_Application.cxx \
+ SalomeApp_DataModel.cxx \
+ SalomeApp_DataObject.cxx \
+ SalomeApp_LoadStudiesDlg.cxx \
+ SalomeApp_Study.cxx \
+ SalomeApp_ExceptionHandler.cxx \
+ SalomeApp_EventFilter.cxx \
+ SalomeApp_PyInterp.cxx \
+ SalomeApp_Tools.cxx \
+ SalomeApp_ImportOperation.cxx \
+ SalomeApp_Filter.cxx \
+ SalomeApp_TypeFilter.cxx \
+ SalomeApp_StudyPropertiesDlg.cxx \
+ SalomeApp_ListView.cxx \
+ SalomeApp_CheckFileDlg.cxx \
+ SalomeApp_VisualState.cxx \
SalomeApp_ExitDlg.cxx
-MOC_FILES= \
- SalomeApp_Application_moc.cxx \
- SalomeApp_DataModel_moc.cxx \
- SalomeApp_Module_moc.cxx \
- SalomeApp_LoadStudiesDlg_moc.cxx \
- SalomeApp_Study_moc.cxx \
- SalomeApp_StudyPropertiesDlg_moc.cxx \
- SalomeApp_ListView_moc.cxx \
- SalomeApp_CheckFileDlg_moc.cxx \
+MOC_FILES = \
+ SalomeApp_Application_moc.cxx \
+ SalomeApp_DataModel_moc.cxx \
+ SalomeApp_Module_moc.cxx \
+ SalomeApp_LoadStudiesDlg_moc.cxx \
+ SalomeApp_Study_moc.cxx \
+ SalomeApp_StudyPropertiesDlg_moc.cxx \
+ SalomeApp_ListView_moc.cxx \
+ SalomeApp_CheckFileDlg_moc.cxx \
SalomeApp_ExitDlg_moc.cxx
-nodist_libSalomeApp_la_SOURCES= $(MOC_FILES)
+nodist_libSalomeApp_la_SOURCES = $(MOC_FILES)
-dist_salomeres_DATA= \
- resources/SalomeApp.ini \
+dist_salomeres_DATA = \
+ resources/SalomeApp.ini \
resources/SalomeApp.xml
-nodist_salomeres_DATA= \
- SalomeApp_images.qm \
+nodist_salomeres_DATA = \
+ SalomeApp_images.qm \
SalomeApp_msg_en.qm
-libSalomeApp_la_CPPFLAGS=$(PYTHON_INCLUDES) $(QT_INCLUDES) $(QWT_INCLUDES) \
- $(CAS_CPPFLAGS) $(VTK_INCLUDES) $(BOOST_CPPFLAGS) @KERNEL_CXXFLAGS@ \
- -I$(srcdir)/../LightApp -I$(srcdir)/../CAM -I$(srcdir)/../Qtx \
- -I$(srcdir)/../SUIT -I$(srcdir)/../OBJECT -I$(srcdir)/../SVTK \
- -I$(srcdir)/../STD -I$(srcdir)/../VTKViewer -I$(srcdir)/../ObjBrowser \
- -I$(srcdir)/../PyConsole -I$(srcdir)/../TOOLSGUI \
- -I$(srcdir)/../PyInterp -I$(srcdir)/../Session -I$(top_builddir)/idl \
- -I$(srcdir)/../Event \
- -I$(srcdir)/../CASCatch \
+libSalomeApp_la_CPPFLAGS = $(PYTHON_INCLUDES) $(QT_INCLUDES) $(QWT_INCLUDES) \
+ $(CAS_CPPFLAGS) $(VTK_INCLUDES) $(BOOST_CPPFLAGS) @KERNEL_CXXFLAGS@ \
+ -I$(srcdir)/../LightApp -I$(srcdir)/../CAM -I$(srcdir)/../Qtx \
+ -I$(srcdir)/../SUIT -I$(srcdir)/../OBJECT -I$(srcdir)/../SVTK \
+ -I$(srcdir)/../STD -I$(srcdir)/../VTKViewer -I$(srcdir)/../ObjBrowser \
+ -I$(srcdir)/../PyConsole -I$(srcdir)/../TOOLSGUI \
+ -I$(srcdir)/../PyInterp -I$(srcdir)/../Session -I$(top_builddir)/idl \
+ -I$(srcdir)/../Event -I$(srcdir)/../CASCatch \
-I$(top_builddir)/salome_adm/unix @CORBA_CXXFLAGS@ @CORBA_INCLUDES@ @LIBXML_INCLUDES@
-libSalomeApp_la_LDFLAGS=$(PYTHON_LIBS) $(QT_MT_LIBS)
-libSalomeApp_la_LIBADD= $(KERNEL_LDFLAGS) -lOpUtil -lSALOMELocalTrace -lSalomeDSClient \
- ../SUIT/libsuit.la ../STD/libstd.la ../CAM/libCAM.la ../ObjBrowser/libObjBrowser.la \
- ../Prs/libSalomePrs.la ../SPlot2d/libSPlot2d.la ../GLViewer/libGLViewer.la \
- ../OCCViewer/libOCCViewer.la ../VTKViewer/libVTKViewer.la ../OBJECT/libSalomeObject.la \
- ../SVTK/libSVTK.la ../SOCC/libSOCC.la ../PyInterp/libPyInterp.la \
- ../PyConsole/libPyConsole.la ../LogWindow/libLogWindow.la \
- ../LightApp/libLightApp.la ../TOOLSGUI/libToolsGUI.la ../Session/libSalomeSession.la \
+libSalomeApp_la_LDFLAGS = $(PYTHON_LIBS) $(QT_MT_LIBS)
+libSalomeApp_la_LIBADD = $(KERNEL_LDFLAGS) -lOpUtil -lSALOMELocalTrace -lSalomeDSClient \
+ ../SUIT/libsuit.la ../STD/libstd.la ../CAM/libCAM.la ../ObjBrowser/libObjBrowser.la \
+ ../Prs/libSalomePrs.la ../SPlot2d/libSPlot2d.la ../GLViewer/libGLViewer.la \
+ ../OCCViewer/libOCCViewer.la ../VTKViewer/libVTKViewer.la ../OBJECT/libSalomeObject.la \
+ ../SVTK/libSVTK.la ../SOCC/libSOCC.la ../PyInterp/libPyInterp.la \
+ ../PyConsole/libPyConsole.la ../LogWindow/libLogWindow.la \
+ ../LightApp/libLightApp.la ../TOOLSGUI/libToolsGUI.la ../Session/libSalomeSession.la \
../CASCatch/libCASCatch.la $(CAS_KERNEL)
-
-EXTRA_DIST+=SalomeApp_PyInterp.h
include $(top_srcdir)/adm_local/unix/make_common_starter.am
-lib_LTLIBRARIES= libSalomeAppTest.la
+lib_LTLIBRARIES = libSalomeAppTest.la
-salomeinclude_HEADERS= SalomeAppTest.hxx
+salomeinclude_HEADERS = SalomeAppTest.hxx
-dist_libSalomeAppTest_la_SOURCES= SalomeAppTest.cxx
+dist_libSalomeAppTest_la_SOURCES = SalomeAppTest.cxx
-libSalomeAppTest_la_CXXFLAGS= @CPPUNIT_INCLUDES@ $(KERNEL_CXXFLAGS)
-libSalomeAppTest_la_LIBADD= @CPPUNIT_LIBS@
+libSalomeAppTest_la_CXXFLAGS = @CPPUNIT_INCLUDES@ $(KERNEL_CXXFLAGS)
+libSalomeAppTest_la_LIBADD = @CPPUNIT_LIBS@
-bin_PROGRAMS= TestSalomeApp
+bin_PROGRAMS = TestSalomeApp
-TestSalomeApp_SOURCES= TestSalomeApp.cxx
+TestSalomeApp_SOURCES = TestSalomeApp.cxx
-TestSalomeApp_CXXFLAGS= $(libSalomeAppTest_la_CXXFLAGS)
-TestSalomeApp_LDADD= $(libSalomeAppTest_la_LIBADD) libSalomeAppTest.la
+TestSalomeApp_CXXFLAGS = $(libSalomeAppTest_la_CXXFLAGS)
+TestSalomeApp_LDADD = $(libSalomeAppTest_la_LIBADD) libSalomeAppTest.la
dist_salomescript_PYTHON = TestSalomeApp.py
UNIT_TEST_PROG = TestSalomeApp
lib_LTLIBRARIES = libSalomeSession.la
-salomeinclude_HEADERS= \
- Session_Session_i.hxx \
- Session_ServerLauncher.hxx \
- Session_ServerThread.hxx \
- Session_ServerCheck.hxx \
+salomeinclude_HEADERS = \
+ Session_Session_i.hxx \
+ SALOME_Session.hxx \
+ Session_ServerLauncher.hxx \
+ Session_ServerThread.hxx \
+ Session_ServerCheck.hxx \
SalomeApp_Engine_i.hxx
# Libraries targets
-dist_libSalomeSession_la_SOURCES= \
- Session_Session_i.cxx \
- Session_ServerThread.cxx \
- Session_ServerLauncher.cxx \
- Session_ServerCheck.cxx \
+dist_libSalomeSession_la_SOURCES = \
+ Session_Session_i.cxx \
+ Session_ServerThread.cxx \
+ Session_ServerLauncher.cxx \
+ Session_ServerCheck.cxx \
SalomeApp_Engine_i.cxx
-libSalomeSession_la_CPPFLAGS= $(QT_MT_INCLUDES) $(PYTHON_INCLUDES) \
- $(HDF5_INCLUDES) $(BOOST_CPPFLAGS) @KERNEL_CXXFLAGS@ $(CAS_CPPFLAGS) \
- @CORBA_CXXFLAGS@ @CORBA_INCLUDES@ \
- -I$(top_builddir)/salome_adm/unix -I$(top_builddir)/idl \
- -I$(srcdir)/../Qtx -I$(srcdir)/../SUIT -I$(srcdir)/../Event \
+libSalomeSession_la_CPPFLAGS = $(QT_MT_INCLUDES) $(PYTHON_INCLUDES) \
+ $(HDF5_INCLUDES) $(BOOST_CPPFLAGS) @KERNEL_CXXFLAGS@ $(CAS_CPPFLAGS) \
+ @CORBA_CXXFLAGS@ @CORBA_INCLUDES@ \
+ -I$(top_builddir)/salome_adm/unix -I$(top_builddir)/idl \
+ -I$(srcdir)/../Qtx -I$(srcdir)/../SUIT -I$(srcdir)/../Event \
-I$(srcdir)/../Style @LIBXML_INCLUDES@
-libSalomeSession_la_LDFLAGS= $(QT_MT_LIBS) $(KERNEL_LDFLAGS) -lSalomeNS \
- -lSalomeLifeCycleCORBA -lOpUtil -lSALOMELocalTrace -lSalomeCatalog \
- -lSalomeDSClient $(CAS_KERNEL) -lwith_loggerTraceCollector \
- ../SUIT/libsuit.la ../Event/libEvent.la ../../idl/libSalomeIDLGUI.la \
+libSalomeSession_la_LDFLAGS = $(QT_MT_LIBS) $(KERNEL_LDFLAGS) -lSalomeNS \
+ -lSalomeLifeCycleCORBA -lOpUtil -lSALOMELocalTrace -lSalomeCatalog \
+ -lSalomeDSClient $(CAS_KERNEL) -lwith_loggerTraceCollector \
+ ../SUIT/libsuit.la ../Event/libEvent.la ../../idl/libSalomeIDLGUI.la \
../Style/libSalomeStyle.la
# Executable
-bin_PROGRAMS= SALOME_Session_Server
+bin_PROGRAMS = SALOME_Session_Server
-dist_SALOME_Session_Server_SOURCES= SALOME_Session_Server.cxx
+dist_SALOME_Session_Server_SOURCES = SALOME_Session_Server.cxx
-SALOME_Session_Server_CPPFLAGS= $(libSalomeSession_la_CPPFLAGS)
-SALOME_Session_Server_LDADD= $(libSalomeSession_la_LDFLAGS) $(OMNIORB_LIBS) \
- $(HDF5_LIBS) -lSalomeContainer -lSalomeResourcesManager -lTOOLSDS \
- -lSalomeHDFPersist -lSalomeDSImpl -lSalomeGenericObj -lRegistry \
- -lSalomeNotification -lSALOMEBasics -lSalomeLauncher ../Qtx/libqtx.la \
- $(top_builddir)/idl/libSalomeIDLGUI.la \
+SALOME_Session_Server_CPPFLAGS = $(libSalomeSession_la_CPPFLAGS)
+SALOME_Session_Server_LDADD = $(libSalomeSession_la_LDFLAGS) $(OMNIORB_LIBS) \
+ $(HDF5_LIBS) -lSalomeContainer -lSalomeResourcesManager -lTOOLSDS \
+ -lSalomeHDFPersist -lSalomeDSImpl -lSalomeGenericObj -lRegistry \
+ -lSalomeNotification -lSALOMEBasics -lSalomeLauncher ../Qtx/libqtx.la \
+ $(top_builddir)/idl/libSalomeIDLGUI.la \
libSalomeSession.la
-
-lib-hook:
- ln -sf $(top_builddir)/bin/salome/styles styles
-
-# ../SalomeApp/libSalomeApp.la
include $(top_srcdir)/adm_local/unix/make_common_starter.am
+EXTRA_DIST += images
+
# Libraries targets
lib_LTLIBRARIES = libSalomeStyle.la
-salomeinclude_HEADERS= \
- Style.h \
- Style_Tools.h \
- Style_Model.h \
+salomeinclude_HEADERS = \
+ Style.h \
+ Style_Tools.h \
+ Style_Model.h \
Style_Salome.h
-dist_libSalomeStyle_la_SOURCES= \
- Style_Tools.cxx \
- Style_Model.cxx \
+dist_libSalomeStyle_la_SOURCES = \
+ Style_Tools.cxx \
+ Style_Model.cxx \
Style_Salome.cxx
-MOC_FILES= \
+MOC_FILES = \
Style_Salome_moc.cxx
-QRC_FILES= \
+QRC_FILES = \
qrc_Style.cxx
-nodist_libSalomeStyle_la_SOURCES= $(MOC_FILES) $(QRC_FILES)
+nodist_libSalomeStyle_la_SOURCES = $(MOC_FILES) $(QRC_FILES)
-libSalomeStyle_la_CPPFLAGS=$(QT_INCLUDES) \
+libSalomeStyle_la_CPPFLAGS = $(QT_INCLUDES) \
-I$(srcdir)/../Qtx
-libSalomeStyle_la_LDFLAGS=$(QT_MT_LIBS) \
+libSalomeStyle_la_LDFLAGS = $(QT_MT_LIBS) \
../Qtx/libqtx.la
lib_LTLIBRARIES = libToolsGUI.la
-salomeinclude_HEADERS= \
- ToolsGUI.h \
- ToolsGUI_RegWidget.h \
+salomeinclude_HEADERS = \
+ ToolsGUI.h \
+ ToolsGUI_RegWidget.h \
ToolsGUI_CatalogGeneratorDlg.h
-dist_libToolsGUI_la_SOURCES= \
- ToolsGUI_CatalogGeneratorDlg.cxx \
- ToolsGUI_RegWidget.cxx \
+dist_libToolsGUI_la_SOURCES = \
+ ToolsGUI_CatalogGeneratorDlg.cxx \
+ ToolsGUI_RegWidget.cxx \
ToolsGUI.cxx
-EXTRA_DIST+=
-
-MOC_FILES= \
- ToolsGUI_CatalogGeneratorDlg_moc.cxx \
+MOC_FILES = \
+ ToolsGUI_CatalogGeneratorDlg_moc.cxx \
ToolsGUI_RegWidget_moc.cxx
-nodist_libToolsGUI_la_SOURCES= $(MOC_FILES)
+nodist_libToolsGUI_la_SOURCES = $(MOC_FILES)
# .po files to transform in .qm
-nodist_salomeres_DATA= \
+nodist_salomeres_DATA = \
ToolsGUI_msg_en.qm
-libToolsGUI_la_CPPFLAGS = $(QT_INCLUDES) $(CAS_CPPFLAGS) $(BOOST_CPPFLAGS) \
- @KERNEL_CXXFLAGS@ @CORBA_CXXFLAGS@ @CORBA_INCLUDES@ \
- -I$(top_builddir)/salome_adm/unix -I$(top_builddir)/idl \
+libToolsGUI_la_CPPFLAGS = $(QT_INCLUDES) $(CAS_CPPFLAGS) $(BOOST_CPPFLAGS) \
+ @KERNEL_CXXFLAGS@ @CORBA_CXXFLAGS@ @CORBA_INCLUDES@ \
+ -I$(top_builddir)/salome_adm/unix -I$(top_builddir)/idl \
-I$(srcdir)/../Qtx -I$(srcdir)/../SUIT
-libToolsGUI_la_LDFLAGS = $(QT_MT_LIBS) ../SUIT/libsuit.la $(CAS_KERNEL) $(KERNEL_LDFLAGS) \
+libToolsGUI_la_LDFLAGS = $(QT_MT_LIBS) ../SUIT/libsuit.la $(CAS_KERNEL) $(KERNEL_LDFLAGS) \
-lSalomeNS -lOpUtil $(top_builddir)/idl/libSalomeIDLGUI.so
lib_LTLIBRARIES = libVTKViewer.la
-salomeinclude_HEADERS= \
- VTKViewer.h \
- VTKViewer_CellLocationsArray.h \
- VTKViewer_Actor.h \
- VTKViewer_ExtractUnstructuredGrid.h \
- VTKViewer_ConvexTool.h \
- VTKViewer_Filter.h \
- VTKViewer_GeometryFilter.h \
- VTKViewer_AppendFilter.h \
- VTKViewer_Algorithm.h \
- VTKViewer_InteractorStyle.h \
- VTKViewer_RenderWindow.h \
- VTKViewer_RenderWindowInteractor.h \
- VTKViewer_ShrinkFilter.h \
- VTKViewer_TransformFilter.h \
- VTKViewer_Transform.h \
- VTKViewer_Trihedron.h \
- VTKViewer_Utilities.h \
- VTKViewer_ViewManager.h \
- VTKViewer_ViewModel.h \
- VTKViewer_ViewWindow.h \
+salomeinclude_HEADERS = \
+ VTKViewer.h \
+ VTKViewer_CellLocationsArray.h \
+ VTKViewer_Actor.h \
+ VTKViewer_ExtractUnstructuredGrid.h \
+ VTKViewer_ConvexTool.h \
+ VTKViewer_Filter.h \
+ VTKViewer_GeometryFilter.h \
+ VTKViewer_AppendFilter.h \
+ VTKViewer_Algorithm.h \
+ VTKViewer_InteractorStyle.h \
+ VTKViewer_RenderWindow.h \
+ VTKViewer_RenderWindowInteractor.h \
+ VTKViewer_ShrinkFilter.h \
+ VTKViewer_TransformFilter.h \
+ VTKViewer_Transform.h \
+ VTKViewer_Trihedron.h \
+ VTKViewer_Utilities.h \
+ VTKViewer_ViewManager.h \
+ VTKViewer_ViewModel.h \
+ VTKViewer_ViewWindow.h \
VTKViewer_Functor.h
-dist_libVTKViewer_la_SOURCES= \
- VTKViewer_CellLocationsArray.cxx \
- VTKViewer_Actor.cxx \
- VTKViewer_ExtractUnstructuredGrid.cxx \
- VTKViewer_Filter.cxx \
- VTKViewer_GeometryFilter.cxx \
- VTKViewer_AppendFilter.cxx \
- VTKViewer_InteractorStyle.cxx \
- VTKViewer_RenderWindow.cxx \
- VTKViewer_RenderWindowInteractor.cxx \
- VTKViewer_ShrinkFilter.cxx \
- VTKViewer_Transform.cxx \
- VTKViewer_TransformFilter.cxx \
- VTKViewer_Trihedron.cxx \
- VTKViewer_Utilities.cxx \
- VTKViewer_ViewManager.cxx \
- VTKViewer_ViewModel.cxx \
- VTKViewer_ConvexTool.cxx \
+dist_libVTKViewer_la_SOURCES = \
+ VTKViewer_CellLocationsArray.cxx \
+ VTKViewer_Actor.cxx \
+ VTKViewer_ExtractUnstructuredGrid.cxx \
+ VTKViewer_Filter.cxx \
+ VTKViewer_GeometryFilter.cxx \
+ VTKViewer_AppendFilter.cxx \
+ VTKViewer_InteractorStyle.cxx \
+ VTKViewer_RenderWindow.cxx \
+ VTKViewer_RenderWindowInteractor.cxx \
+ VTKViewer_ShrinkFilter.cxx \
+ VTKViewer_Transform.cxx \
+ VTKViewer_TransformFilter.cxx \
+ VTKViewer_Trihedron.cxx \
+ VTKViewer_Utilities.cxx \
+ VTKViewer_ViewManager.cxx \
+ VTKViewer_ViewModel.cxx \
+ VTKViewer_ConvexTool.cxx \
VTKViewer_ViewWindow.cxx
-MOC_FILES= \
- VTKViewer_RenderWindow_moc.cxx \
- VTKViewer_RenderWindowInteractor_moc.cxx \
- VTKViewer_ViewManager_moc.cxx \
- VTKViewer_ViewModel_moc.cxx \
+MOC_FILES = \
+ VTKViewer_RenderWindow_moc.cxx \
+ VTKViewer_RenderWindowInteractor_moc.cxx \
+ VTKViewer_ViewManager_moc.cxx \
+ VTKViewer_ViewModel_moc.cxx \
VTKViewer_ViewWindow_moc.cxx
-nodist_libVTKViewer_la_SOURCES= $(MOC_FILES)
+nodist_libVTKViewer_la_SOURCES = $(MOC_FILES)
-dist_salomeres_DATA=\
- resources/vtk_view_back.png \
- resources/vtk_view_bottom.png \
- resources/vtk_view_camera_dump.png \
- resources/vtk_view_fitall.png \
- resources/vtk_view_fitarea.png \
- resources/vtk_view_front.png \
- resources/vtk_view_glpan.png \
- resources/vtk_view_left.png \
- resources/vtk_view_pan.png \
- resources/vtk_view_reset.png \
- resources/vtk_view_right.png \
- resources/vtk_view_rotate.png \
- resources/vtk_view_top.png \
- resources/vtk_view_triedre.png \
+dist_salomeres_DATA = \
+ resources/vtk_view_back.png \
+ resources/vtk_view_bottom.png \
+ resources/vtk_view_camera_dump.png \
+ resources/vtk_view_fitall.png \
+ resources/vtk_view_fitarea.png \
+ resources/vtk_view_front.png \
+ resources/vtk_view_glpan.png \
+ resources/vtk_view_left.png \
+ resources/vtk_view_pan.png \
+ resources/vtk_view_reset.png \
+ resources/vtk_view_right.png \
+ resources/vtk_view_rotate.png \
+ resources/vtk_view_top.png \
+ resources/vtk_view_triedre.png \
resources/vtk_view_zoom.png
-nodist_salomeres_DATA= \
- VTKViewer_images.qm \
+nodist_salomeres_DATA = \
+ VTKViewer_images.qm \
VTKViewer_msg_en.qm
-libVTKViewer_la_CPPFLAGS=$(QT_INCLUDES) $(VTK_INCLUDES) $(CAS_CPPFLAGS) \
+libVTKViewer_la_CPPFLAGS = $(QT_INCLUDES) $(VTK_INCLUDES) $(CAS_CPPFLAGS) \
-I$(srcdir)/../Qtx -I$(srcdir)/../SUIT
-libVTKViewer_la_LDFLAGS=$(QT_MT_LIBS) $(CAS_KERNEL) $(VTK_LIBS) $(OGL_LIBS) \
+libVTKViewer_la_LDFLAGS = $(QT_MT_LIBS) $(CAS_KERNEL) $(VTK_LIBS) $(OGL_LIBS) \
../Qtx/libqtx.la ../SUIT/libsuit.la
# Executable
bin_PROGRAMS = VTKViewer
-dist_VTKViewer_SOURCES=VTKViewer.cxx
+dist_VTKViewer_SOURCES = VTKViewer.cxx
-VTKViewer_CPPFLAGS=$(libVTKViewer_la_CPPFLAGS)
-VTKViewer_LDADD=libVTKViewer.la $(libVTKViewer_la_LDFLAGS)
+VTKViewer_CPPFLAGS = $(libVTKViewer_la_CPPFLAGS)
+VTKViewer_LDADD = libVTKViewer.la $(libVTKViewer_la_LDFLAGS)
