SET(CMAKE_MODULE_PATH "${CMAKE_SOURCE_DIR}/CMakeCommon" ${CMAKE_MODULE_PATH})
-IF (NOT OPENPARTS_BUILD_DOC)
+IF (NOT CADBUILDER_BUILD_DOC)
OPTION(SHAPER_BUILD_DOC "Generate SHAPER documentation" ON)
-ENDIF(OPENPARTS_BUILD_DOC)
+ENDIF(NOT CADBUILDER_BUILD_DOC)
INCLUDE(SalomeMacros)
ENDIF(WIN32)
IF(HAVE_SALOME)
- SET(EXCLUDE_DOC_DIR "*/AppElements/* */OpenParts/*")
+ SET(EXCLUDE_DOC_DIR "*/AppElements/* */CADBuilder/*")
ELSE(HAVE_SALOME)
SET(EXCLUDE_DOC_DIR "*/Shaper/*")
ENDIF(HAVE_SALOME)
* \defgroup Salome A Salome connector
*
* \brief A set of classes which provide wrapping of
- * OpenParts application as SALOME module
+ * CAD Builder application as SALOME module
*/
/**
/*!
\page general_architecture General Architecture
-OpenPARTS is made of Workshop (see XGUI_Workshop) which loads a Module (see ModuleBase_IModule), connecting its features with GUI, providing it with services for launching of operations, tools for user inputs and visualisation of results. The Module can consist of one or several plug-ins which provide implementation of Module features. Each plug-in can implement one or several features. These features can be structured by Workbenches within Workshop. Workshop provides introducing of these Workbenches within main window in form of menus or/and tool bars.
+CAD Builder is made of Workshop (see XGUI_Workshop) which loads a Module (see ModuleBase_IModule), connecting its features with GUI, providing it with services for launching of operations, tools for user inputs and visualisation of results. The Module can consist of one or several plug-ins which provide implementation of Module features. Each plug-in can implement one or several features. These features can be structured by Workbenches within Workshop. Workshop provides introducing of these Workbenches within main window in form of menus or/and tool bars.
\n
-Workshop interacts with a Module with help of specific interface defined in ModuleBase package. Each module for OpenPARTS application has to implement ModuleBase_IModile interface.
+Workshop interacts with a Module with help of specific interface defined in ModuleBase package. Each module for CAD Builder application has to implement ModuleBase_IModile interface.
\n
A Module manages a one document (ModelAPI_Document). This document consists of a one root document and several, loaded by request, sub-documents. Each sub-document can be stored in a single file.
\n
-<b>Main features of the general architecture of OpenPARTS:</b>
+<b>Main features of the general architecture of CAD Builder:</b>
<ul>
-<li> OpenPARTS consists of a one Module running within a Workshop.</li>
+<li> CAD Builder consists of a one Module running within a Workshop.</li>
<li> This Module produces one type of Document only.</li>
<li> This Document consists of a main document and several sub-documents which can be stored and loaded as separated files.</li>
<li> A Module is made of one or several Plug-ins implementing Features supported of the Module.</li>
<li> These Features are structured by Workbenches.</li>
<li> The Module communicates with the Workshop through Interfaces.</li>
-<li> The API of OpenPARTS consists of the Interface of the Workshop and of Modules.</li>
+<li> The API of CAD Builder consists of the Interface of the Workshop and of Modules.</li>
<li> A configuration file describes the composition of the Workshop where the Module and Plug-ins are referenced by their unique names.</li>
</ul>
\n\n
\n\n
Feature is a peace of code which performs an operation. The Feature is a main component of a plug-in. It consists of input attributes, operation functionality and result objects (one or several). All features are defined in plug-ins by the specific feature developer (in C++ or python).
\n
-For today there is a one implementation of OpenPARTS application which implements Part Set functionality (PartSet_Module).
-The geometric model (i.e. the whole geometry produce by PartSet) is created through operations, or features (ModelAPI_Feature), which define a meaningful piece of design (see \ref Plugins group). In order to easily create dedicated variants of the modeler, also to gradually develop OpenPARTS, each feature is implemented in a <i>Plug-in</i> (ModelAPI_Plugin, a piece of application including its own GUI, built separately from the application. It is loaded dynamically to the application). In other words, a Module is made of a collection of Plug-ins.
+For today there is a one implementation of CAD Builder application which implements Part Set functionality (PartSet_Module).
+The geometric model (i.e. the whole geometry produce by PartSet) is created through operations, or features (ModelAPI_Feature), which define a meaningful piece of design (see \ref Plugins group). In order to easily create dedicated variants of the modeler, also to gradually develop CAD Builder, each feature is implemented in a <i>Plug-in</i> (ModelAPI_Plugin, a piece of application including its own GUI, built separately from the application. It is loaded dynamically to the application). In other words, a Module is made of a collection of Plug-ins.
Each sub-document contains a data of a one Part. When the user saves its session, all documents are saved: the PartSet and each Part.
\n
aValue = std::string(anEnv) +
FSEP + "share" + FSEP + "salome" + FSEP + "resources" + FSEP + "shaper";
} else {
- anEnv = getenv("OPENPARTS_ROOT_DIR");
+ anEnv = getenv("CADBUILDER_ROOT_DIR");
if (anEnv) {
aValue = std::string(anEnv) + FSEP + "resources";
}
aValue = std::string(anEnv) +
FSEP + "share" + FSEP + "salome" + FSEP + "resources" + FSEP + "shaper";
} else {
- anEnv = getenv("OPENPARTS_ROOT_DIR");
+ anEnv = getenv("CADBUILDER_ROOT_DIR");
if (anEnv) {
aValue = std::string(anEnv) + FSEP + "plugins";
}
if (aSolution == 1)
anEnvName<<"SHAPER_ROOT_DIR";
else if (aSolution == 2)
- anEnvName<<"OPENPARTS_ROOT_DIR";
+ anEnvName<<"CADBUILDER_ROOT_DIR";
else
- anEnvName<<"OPENPARTS_PLUGINS_DIR";
+ anEnvName<<"CADBUILDER_ROOT_DIR";
char* anEnv = getenv(anEnvName.str().c_str());
if (!anEnv)
if (aResultIndex == theFindIndex)
return aFileName;
aResultIndex++;
- if (aSolution == 1) // don't allow SHAPER and OpenParts paths treated simultaneously
+ if (aSolution == 1) // don't allow SHAPER and CADBuilder paths treated simultaneously
aSolution++;
}
}
aFile = std::string(anEnv) +
FSEP + "share" + FSEP + "salome" + FSEP + "resources" + FSEP + "shaper";
} else {
- anEnv = getenv("OPENPARTS_ROOT_DIR");
+ anEnv = getenv("CADBUILDER_ROOT_DIR");
if (anEnv)
aFile = std::string(anEnv) + FSEP + "resources";
}
aFile = std::string(anEnv) +
FSEP + "share" + FSEP + "salome" + FSEP + "resources" + FSEP + "shaper";
} else {
- anEnv = getenv("OPENPARTS_ROOT_DIR");
+ anEnv = getenv("CADBUILDER_ROOT_DIR");
if (anEnv)
aFile = std::string(anEnv) + FSEP + "resources";
}
static QString MyFilter2(QObject::tr("SHAPER files (*.shaper)"));
static QString MyExtension(".shaper");
#else
-static QString MyFilter(QObject::tr("OpenParts files (*.opp);;All files (*.*)"));
-static QString MyFilter2(QObject::tr("OpenParts files (*.opp)"));
+static QString MyFilter(QObject::tr("CAD Builder files (*.opp);;All files (*.*)"));
+static QString MyFilter2(QObject::tr("CAD Builder files (*.opp)"));
static QString MyExtension(".opp");
#endif
"salome" + aSep + "gui" + aSep + "SHAPER";
}
#else
- QString aDir(getenv("OPENPARTS_ROOT_DIR"));
+ QString aDir(getenv("CADBUILDER_ROOT_DIR"));
aDocDir = aDir + aSep + "doc" + aSep + "gui";
#endif
QString aFileName = aDocDir + aSep + aHelpPage;
void createDockWidgets();
/// Extends undo/redo toolbutton's with history menu
- /// \param theObject - in the OpenParts it is a QToolButton by itself,
+ /// \param theObject - in the CADBuilder it is a QToolButton by itself,
/// in salome mode - QAction that creates a button.
/// \param theSignal - void "updateUndoHistory" or "updateRedoHistory" SIGNAL;
/// \param theSlot - onUndo(int) or onRedo(int) SLOT
