OPALE:10.0:Utilisation:Partie Dynamique (Map)/en - Historique des versions

Alestoquoi le 25 juillet 2019 à 09:10

2019-07-25T09:10:03Z

Alestoquoi le 25 juillet 2019 à 09:07

2019-07-25T09:07:22Z

Alestoquoi le 25 juillet 2019 à 09:06

2019-07-25T09:06:59Z

Alestoquoi le 25 juillet 2019 à 09:06

2019-07-25T09:06:45Z

Alestoquoi le 25 juillet 2019 à 08:20

2019-07-25T08:20:20Z

Alestoquoi le 25 juillet 2019 à 07:46

2019-07-25T07:46:57Z

Alestoquoi le 17 juillet 2019 à 09:56

2019-07-17T09:56:00Z

Alestoquoi le 17 juillet 2019 à 09:54

2019-07-17T09:54:49Z

Alestoquoi le 17 juillet 2019 à 09:54

2019-07-17T09:54:07Z

Alestoquoi : Page créée avec « A group can vary: * in size: beginning and end lines are determined dynamically by conditions * and/or in printing position: variable groups can be linked one to another... »

2019-07-10T13:30:29Z

Page créée avec « A group can vary: * in size: beginning and end lines are determined dynamically by conditions * and/or in printing position: variable groups can be linked one to another... »

← Version précédente		Version du 25 juillet 2019 à 09:10
Ligne 177 :		Ligne 177 :
	Note:		Note:

−	XML data can be placed on the outside of a page as information linked to the overall document and not to the page in particular. However this data will not be accessible to '''Designer''' and thus cannot be processed to design the document. Nonetheless, this data can be used by in the '''Opale Server''' engine.	+	XML data can be placed on the outside of a page as information linked to the overall document and not to the page in particular. However this data will not be accessible to '''Designer''' and thus cannot be processed to design the document. Nonetheless, this data can be used in the '''Opale Server''' engine.

@@ Ligne 122 : / Ligne 122 : @@
 * The tags and attributes names are case-sensitive and need to be written in lowercase letters.
 * For the application to access it, data must be placed in pages in between the <page name="…"> and </page> tags. One document can contain several pages.
-* Inside a page, data is organised per singular fields (<field name="…"> tag), or per information groups (<group name="…"> tag)
+* Inside a page, data is organised per unit-based fields (<field name="…"> tag), or per information groups (<group name="…"> tag)
 * Information groups are composed of lines (<line name="…"> tag)
-* The lines contain singular informations (<field name="…"> tag)
+* The lines contain unit-based informations (<field name="…"> tag)

@@ Ligne 106 : / Ligne 106 : @@
 <field name="...">value1</field> can correspond to two things:
-* If this tag is on the outside of a group, that is to say on the outside of the <group> </group> tags, it can correspond to singular information in the invoice. In which case, value1 corresponds to the invoice number in the header, for instance, or to the client number, the type of invoice, etc.
+* If this tag is on the outside of a group, that is to say on the outside of the <group> </group> tags, it can correspond to unit-based information in the invoice. In which case, value1 corresponds to the invoice number in the header, for instance, or to the client number, the type of invoice, etc.
 * If this tag is inside a group, value1 corresponds to the value of the zone in the line. For instance, the product code, its name, price, etc.

@@ Ligne 92 : / Ligne 92 : @@
 * The <page name="..."> … </page> tags mark out the pages of the document. In the last example, there is only one page.
-* The <field name="...">value1</field> tags correspond to singular information (the equivalent of ‘zones’/'fields' in '''Designer''').
+* The <field name="...">value1</field> tags correspond to unit-based information (the equivalent of ‘zones’/'fields' in '''Designer''').
 * The <group name="..."> … </group> tags refer to a particular number of lines which contain zones, such as a ‘group’ in '''Designer'''.
 * The <line name="…"> … <line> tags correspond to the lines inside of these groups.

@@ Ligne 44 : / Ligne 44 : @@
 In XML mode, the design principles are the same and are put in application using an example file loaded in the application.
 [[File:ModeXML.PNG|300px|center|sans_cadre]]
 Once the document is loaded, do not forget to check that the mode = XML in the project properties.

@@ Ligne 17 : / Ligne 17 : @@
 Text files usually have a ".PAG" extension because they need to be paginated: the DESIGNER application does not manage pagination in SPLF mode.
-Text files can be paginated by running the « MAPPAGIFS » command in OPALE Server where an argument specifying the number of lines per page ("Overflow") will be given.
+Text files can be paginated by running the "MAPPAGIFS" command in OPALE Server where an argument specifying the number of lines per page ("Overflow") will be given.
 XML files need to respect a particular syntax so that the application can properly process them.

@@ Ligne 298 : / Ligne 298 : @@
 When using the "drag and drop" in the spooled file view, the beginning and end lines are automatically filled in. The latter can be adjusted if necessary.
-You can also create a fixed group using the icon that is located in the "Mapping" toolbar. Les beginning and end lines will then have to be filled in manually.
+You can also create a fixed group using the icon that is located in the "Mapping" toolbar. The beginning and end lines will then have to be filled in manually.
 No information will be printed if you ask for a preview, because a group only defines tags in between which information must be retrieved in the spooled file.

← Version précédente		Version du 17 juillet 2019 à 09:54
Ligne 270 :		Ligne 270 :
	To create a fixed group:		To create a fixed group:

−	Select the bloc of lines to retrieve in the spooled file, ~~the~~ use the "drag and drop" method to place the group in the designing space.	+	Select the bloc of lines to retrieve in the spooled file, then use the "drag and drop" method to place the group in the designing space.

@@ Ligne 247 : / Ligne 247 : @@
 * Barcode: encodes and prints out barcodes
 * Tools: inserts a page number, images, …
-* Archive: indexe the document to archive it (non printed zones)
+* Archive: indexes the document to archive it (non printed zones)
 * Memory: memorises (non printed) information to reuse it later
 * Graph: designs graphs

@@ Ligne 312 : / Ligne 312 : @@
 The aim of a variable group is the same as that of a fixed group: retrieve several lines of information in the spooled file. Use the fixed group when the information to retrieve has a fixed position in the spooled file (never changes), use the variable group to retrieve information that does not have a fixed position beforehand.
-Un groupe peut être variable :
+A group can vary:
-* en taille : les lignes de début et de fin sont déterminées dynamiquement par conditions
+* in size: beginning and end lines are determined dynamically by conditions
-* et/ou en position d’impression : les groupes variables peuvent être chainés les uns à la suite des autres, le groupe n+1 commençant à s’imprimer dès que le groupe n est terminé.
+* and/or in printing position: variable groups can be linked one to another, the n+1 group then starts to be printed as soon as the n group is printed entirely.
-Pour créer un groupe variable, cliquer sur l’icône [[File:Iconegroupe.PNG|frameless|120px ]] , puis dessiner le groupe sur l’espace de conception. La vue Propriétés s’affiche, pour renseigner les informations du groupe
+To create a variable group, click on the [[File:Iconegroupe.PNG|frameless|120px ]] icon, then draw the group in the designing space. The Properties view opens, fill in the information about the group.