Changes between Version 1 and Version 2 of MolgenisLanguageReference
- Timestamp:
- 2009-08-23T22:49:00+02:00 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MolgenisLanguageReference
v1 v2 2 2 = MOLGENIS Database definition language ('*_db.xml' files) = 3 3 4 == <molgenis> application defintion element == 5 The <molgenis> element is the root of each MOLGENIS application definition file and can contain data definition and/or user interface definition elements. The model can be split, i.e. there can be multiple MOLGENIS XML files for one application (see section on molgenis.properties file). 6 Example usage of the <molgenis> element: 7 {{{ 8 #!xml 9 <molgenis name="myfirstdb" label="My First Database"> 10 <menu name="mainmenu"> ... 11 <entity name="firstentity"/> 12 <module name="mymodule"/> 13 ... 14 </molgenis> 15 }}} 4 The MOLGENIS database language knows the following elemengs 5 * MolgenisElement -- usage of the <molgenis> element 6 * EntityElement -- usage of the <entity> element 7 * FieldElement -- usage of the <field> element 8 * UniqueElement -- usage of the <unique> element 9 * ModuleElement -- usage of the <module> element 16 10 17 === Required attributes of the <molgenis> element ===18 * name="name": name of your MOLGENIS blueprint. This will be used by the generator to name the java packages that are generated..19 11 20 === Optional attributes of the <molgenis> element ===21 * label="your label": Label of your MOLGENIS system. This will be shown on the screen as well as heading in the generated documentation.22 * Version=”1.2.3”: Version of your MOLGENIS system. It is recommended to use this to manage the versions of your application.23 12 24 The <molgenis> element can contain other elements:25 * Exactly one <menu> or one <form> as main screen.26 * Zero or one <description> elements describing the application27 * Many <entity> elements describing the data structure.28 * Many <module> elements describing the data structure. These are containers to group <entity>.29