--- /dev/null
+
+.. include:: ../../rst_prolog.rst
+
+Command template
+****************
+
+Description
+===========
+The **template** command generates the sources of a SALOME module out of a template.
+SAT provides two templates for SALOME 9 :
+
+* PythonComponent : a complete template for a SALOME module implemented in python (with data model and GUI)
+* CppComponent : a template for a SALOME component implemented in C++, with a code coupling API
+
+Usage
+=====
+* Create a python SALOME module: ::
+
+ sat template --name <product_name> --template PythonComponent --target <my_directory>
+
+ Create in *my_directory* a ready to use SALOME module implemented in python. The generated module can then be adapted to the needs, and pushed in a git repository.
+
# built documents.
#
# The short X.Y version.
-version = '5.4'
+version = '5.5'
# The full version, including alpha/beta/rc tags.
-release = '5.4.0'
+release = '5.5.0'
# The language for content autogenerated by Sphinx. Refer to documentation
# for a list of supported languages.
# The name of an image file (relative to this directory) to place at the top
# of the sidebar.
-html_logo = "images/sat_v5.0.png"
+html_logo = "images/sat_v5.png"
# The name of an image file (within the static path) to use as favicon of the
# docs. This file should be a Windows icon file (.ico) being 16x16 or 32x32
# Grouping the document tree into LaTeX files. List of tuples
# (source start file, target name, title, author, documentclass [howto/manual]).
latex_documents = [
- ('index', 'salomeTools.tex', u'salomeTools Documentation',
+ ('index', 'salomeTools.tex', u'SAT Documentation',
u'CEA DEN/DANS/DM2S/STMF/LGLS', 'manual'),
]
# One entry per manual page. List of tuples
# (source start file, name, description, authors, manual section).
man_pages = [
- ('index', 'salometools', u'salomeTools Documentation',
+ ('index', 'salometools', u'SAT Documentation',
[u'CEA DEN/DANS/DM2S/STMF/LGLS'], 1)
]
.. toctree::
:maxdepth: 2
-************
-Salome Tools
-************
+.. **********
+.. SalomeTool
+.. **********
Welcome
Using SAT <usage_of_sat>
Configuration <configuration>
-For SAT developers...
----------------------
-
-.. toctree::
- :maxdepth: 1
-
- Extending SAT with additional commands <write_command>
List of Commands
================
prepare <commands/prepare>
compile <commands/compile>
launcher <commands/launcher>
- application <commands/application>
log <commands/log>
environ <commands/environ>
clean <commands/clean>
generate <commands/generate>
init <commands/init>
environ <commands/environ>
+ template <commands/template>
Release Notes
.. toctree::
:maxdepth: 1
- Release Notes 5.5.0 (in construction) <release_notes/release_notes_5.5.0>
+ Release Notes 5.5.0 <release_notes/release_notes_5.5.0>
Release Notes 5.4.0 <release_notes/release_notes_5.4.0>
Release Notes 5.3.0 <release_notes/release_notes_5.3.0>
Release Notes 5.2.0 <release_notes/release_notes_5.2.0>
After several tests anf iterations, the following management was adopted:
- sat prepare <application> does nothing for pip products (because at prepare time we don't have python compiled, and the use of native pip may not be compatible).
- - sat compile <application> use the pip module installed in python to get pip archives (wheels), store them in local archive directory, and install then either in python
-directory, or in the product directory (in accordance to pip_install_dir property).
+ - sat compile <application> use the pip module installed in python to get pip archives (wheels), store them in local archive directory, and install then either in python directory, or in the product directory (in accordance to pip_install_dir property).
**single directory mode**