| ... | ... | @@ -70,5 +70,5 @@ The macro defines an expression using two templating variables,i.e. **${Criterio |
|
|
|
[Templates](bootstrapping/templates) will be discussed in detail in a dedicated [templating](bootstrapping/templates) section, so we won't go into much detail here. Suffice it to say that templates are the actual workhorse of most scenarios implemented with TULIP. Templates are essential for dynamic scenarios, relying on data provided from external systems to populate individual objects.
|
|
|
|
|
|
|
|
## Object Tag
|
|
|
|
The **`<objects>`** tag groups all *explicit* tangible object definitions. By explicit object definitions we understand objects which are completely and unequivocally defined and can be instantiated as is. The opposite form of object definitions are those objects requiring data from external systems, which should be defined in the previously introduced [templates](/nui/tulip/-/wikis/bootstrapping/templates) section. It is important to note though, that independently from whether an object is declared in the **`templates`** or **`objects`** section, they always share the same properties. The difference resides in what you're allowed to use to get the respective values from. If defined inside the **`templates`** sections, you're allowed the use variables to provided property values, which you're not allowed to do inside **`objects`** sections. Apart from that, declaring objects in both sections is identical. Each object definition is encapsulated in its own `<object>` tag. Tangible objects are the functional software representation of the physical object manipulated by the user and will be called hereafter **Widgets**. TULIP comes with a number of predefined widgets implementing different behaviors, however, all widgets have a set of basic properties which we'd like to introduce in the [following section](/bootstrapping/objects).
|
|
|
|
<div align="right">[Objects](/bootstrapping/objects)</div> |
|
|
|
The **`<objects>`** tag groups all *explicit* tangible object definitions. By explicit object definitions we understand objects which are completely and unequivocally defined and can be instantiated as is. The opposite form of object definitions are those objects requiring data from external systems, which should be defined in the previously introduced [templates](/nui/tulip/-/wikis/bootstrapping/templates) section. It is important to note though, that independently from whether an object is declared in the **`templates`** or **`objects`** section, they always share the same properties. The difference resides in what you're allowed to use to get the respective values from. If defined inside the **`templates`** sections, you're allowed the use variables to provided property values, which you're not allowed to do inside **`objects`** sections. Apart from that, declaring objects in both sections is identical. Each object definition is encapsulated in its own `<object>` tag. Tangible objects are the functional software representation of the physical object manipulated by the user and will be called hereafter **Widgets**. TULIP comes with a number of predefined widgets implementing different behaviors, however, all widgets have a set of basic properties which we'd like to introduce in the [following section](/authoring/objects).
|
|
|
|
<div align="right">[Objects](/authoring/objects)</div> |
