13.07.2015 Views

Bouml reference manual - Fedora Project Packages GIT repositories

Bouml reference manual - Fedora Project Packages GIT repositories

Bouml reference manual - Fedora Project Packages GIT repositories

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

file:///C:/uml/BOUML/bouml_3.0/doc/TOUT.html205 of 378 07/10/2007 15:55When you do not want to generate the C++ source file (for instance the artifact is only associated to an enum), empties the declaration<strong>manual</strong>ly or using the button not generated in C++.${comment} is replaced by the artifact description${description} is replaced by the artifact description without adding //${includes} if ${all_includes} is not used in the header definition, it is replaced by the automatically generated #include and using forms(done by the C++ code generator, not made by the dialog which produce a fixed form). If ${all_includes} is used in the header definition,it is replaced by the #include of the header. It is also a good place to add your #include and using forms, the code generator does not lookinside the bodies to compute the needed ones.${namespace_start} is replaced by the namespace xx { forms, dependent on the namespace specifications associated to the packagecontaining the deployment view where the artifact is defined.${members} is replaced by the non inline members of the classes associated to the artifact.${namespace_end} is replaced by the } forms, dependent on the namespace specifications associated to the package containing thedeployment view where the artifact is defined.The forms @{property}are replaced by the value of the corresponding user property if it is defined for the class or at an upper level, else it is not substituted.Artifact dialog, tab Java sourceThis tab is only available for the source artifacts and allows to give the definition of the Java source file generated for the artifact, it isvisible only if Java is set through the menu LanguagesWhen you push the button default declaration, the form specified through the generation settings is proposed, this last may be modifiedas you want, even to produce illegal source code.When you do not want to generate the Java source file, empties the declaration <strong>manual</strong>ly or using the button not generated in Java.${comment} is replaced by the artifact description adding /* */${description} is replaced by the artifact description without adding /* */${package} is replaced by the package xx forms, dependent on the package specifications associated to the BOUML package containingthe deployment view where the artifact is defined.${definition} is replaced by the definition of the classes associated to the artifact.The forms @{property}are replaced by the value of the corresponding user property if it is defined for the class or at an upper level, else it is not substituted.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!