ONYX - 9.0 - Utilisation - Les bonnes pratiques ONYX Designer/en

Différence entre versions

De MappingDoc
(Page créée avec « * '''TEXT memory zones''': if no calculations are required, "Memory" type zones must always have the subtype '''"Text Memory"''' and never "Integer Memory" nor "Floating M... »)
 
(Une révision intermédiaire par le même utilisateur non affichée)
Ligne 1 : Ligne 1 :
 
<languages/>
 
<languages/>
We recommend that you follow the good practices described below.
+
We recommend that you follow the best practices described below.
  
 
* '''Name of the projets''' : FORMAT_SEQUENCE (example: INVOICES_00010.mpp).<br/>
 
* '''Name of the projets''' : FORMAT_SEQUENCE (example: INVOICES_00010.mpp).<br/>
Ligne 10 : Ligne 10 :
 
* '''TEXT memory zones''': if no calculations are required, "Memory" type zones must always have the subtype '''"Text Memory"''' and never "Integer Memory" nor "Floating Memory" (even if the fields handled are numerical)
 
* '''TEXT memory zones''': if no calculations are required, "Memory" type zones must always have the subtype '''"Text Memory"''' and never "Integer Memory" nor "Floating Memory" (even if the fields handled are numerical)
  
* '''Espacement AVANT''' : Lors de la création de groupes, gérer les sauts de lignes avec les '''espacements AVANT'''. Les espacements APRES ne doivent être utilisés que pour ajouter un espace libre avant l'impression de la ligne suivante. Ne jamais écrire dans un espace réservé par une autre ligne (c-a-d par la ligne précédente ou par la ligne suivante), chaque ligne ayant son propre espace défini par <u><i>"Espacement AVANT + Espacement APRES"</i></u>.
+
* '''Space BEFORE''': when creating groups, manage line breaks with '''space BEFORE'''. Spaces AFTER should only be used to add a blank space before the following line is printed. Do not write in a space which is destined to another line (that is to say the previous or following line), because each line has its own space, defined by <u><i>"Space BEFORE + Space AFTER"</i></u>.

Version actuelle datée du 29 juillet 2019 à 07:30

Autres langues :
English • ‎français

We recommend that you follow the best practices described below.

  • Name of the projets : FORMAT_SEQUENCE (example: INVOICES_00010.mpp).
An additional comment can be added afterwards (example: INVOICES_00010_Invoices-Clients.mpp). In all cases, it is essential that the first 20 characters in the name of the project be discriminant.
Creating a subfolder for each project where source files of Designer and Connect, components, variable elements and txt or xml example files are placed, is recommended.
  • No calculations: Avoid making calculations in Designer. It is best that you favour making calculations beforehand (ERP, Connect...)
  • TEXT memory zones: if no calculations are required, "Memory" type zones must always have the subtype "Text Memory" and never "Integer Memory" nor "Floating Memory" (even if the fields handled are numerical)
  • Space BEFORE: when creating groups, manage line breaks with space BEFORE. Spaces AFTER should only be used to add a blank space before the following line is printed. Do not write in a space which is destined to another line (that is to say the previous or following line), because each line has its own space, defined by "Space BEFORE + Space AFTER".