Join modifications from branch OCC_debug_for_3_2_0b1

[modules/gui.git] / doc / salome / gui / KERNEL / kernel / about_salome_pro_architecture.htm

diff --git a/doc/salome/gui/KERNEL/kernel/about_salome_pro_architecture.htm b/doc/salome/gui/KERNEL/kernel/about_salome_pro_architecture.htm
index 477c3de19efa3bc0daebf21cb89fb891d244931b..689f79e303a42cf75fea584076f0873532c73181 100755 (executable)
--- a/doc/salome/gui/KERNEL/kernel/about_salome_pro_architecture.htm
+++ b/doc/salome/gui/KERNEL/kernel/about_salome_pro_architecture.htm
@@ -104,7 +104,7 @@ else
  dramatically without affecting other components. </span></p>\r
 \r
 <p class="whs3"><span style="font-weight: normal;">All \r
- software components (VISU, GEOM, SMESH...) integrated into </span>SALOME \r
+ software components (Post-Pro, Geometry, Mesh...) integrated into </span>SALOME \r
  <span style="font-weight: normal;">platform &nbsp;implement \r
  predefined interfaces. Each component provides data for the </span>SALOME<span \r
  style="font-weight: normal;"> study in a form of links (stored in the \r
@@ -118,16 +118,15 @@ else
 \r
 <p class="whs2">&nbsp;</p>\r
 \r
-<p class="whs5">Actually, starting with SALOME 3.0.0 \r
- version, it is possible to create engine-independent modules. These modules \r
- may not use CORBA at all, and can have internal data structure which can \r
- be written in pure C++ (or python). Such modules are located inside SALOME \r
- GUI process and from the point of view of the end user have no difference \r
- with standard components. Such modules not using the standard tools of \r
- SALOME platform are defined on a special separated level named CAM. CAM \r
- component is the basis for new SALOME GUI and contains all basic functionality \r
- for working with modules (loading; saving, closing, customization of toolbar \r
- and menu).</p>\r
+<p class="whs5">It is equally possible to create engine-independent \r
+ modules. These modules may not use CORBA at all, and can have internal \r
+ data structure which can be written in pure C++ (or python). Such modules \r
+ are located inside SALOME GUI process and from the point of view of the \r
+ end user have no difference with standard components. Such modules not \r
+ using the standard tools of SALOME platform are defined on a special separated \r
+ level named CAM. CAM component is the basis for new SALOME GUI and contains \r
+ all basic functionality for working with modules (loading; saving, closing, \r
+ customization of toolbar and menu).</p>\r
 \r
 <p class="whs5">Another fundamental piece of the <span \r
  style="font-weight: bold;"><B>SALOME</B></span> architecture is the use of the \r
@@ -147,7 +146,7 @@ else
 <p class="whs6"><span \r
  style="font-weight: normal;">&nbsp;<img src="../note1.gif" x-maintain-ratio="TRUE" width="35px" height="37px" border="0" class="img_whs7">In </span>SALOME<span style="font-weight: normal;"> there \r
  is a possibility to run definite components in the so-called </span><a href="running_salome_pro.htm#batchmode">batch mode</a><span style="font-weight: normal;"> \r
- without GUI provided by IAPP component. In this case you can work with \r
+ without GUI provided by GUI component. In this case you can work with \r
  these components with the help of Python commands and scripts. </span>&nbsp;</p>\r
 \r
 <p class="whs8">&nbsp;</p>\r