Difference between revisions of "Templates"
| Line 1: | Line 1: | ||
| − | + | {{context|Basic Concepts and Terminology|Visual Building Blocks}} | |
| − | + | ||
Templates contain one or more portals and represent a rectangular region within the containing layout. The template is responsible for coordinating the position of its own portals within its boundaries. | Templates contain one or more portals and represent a rectangular region within the containing layout. The template is responsible for coordinating the position of its own portals within its boundaries. | ||
Latest revision as of 01:21, 22 November 2008
Context: HL Kit … Basic Concepts and Terminology … Visual Building Blocks
Templates contain one or more portals and represent a rectangular region within the containing layout. The template is responsible for coordinating the position of its own portals within its boundaries.
Every template is associated with a specific thing or pick. All of the portals within the template are associated with that thing or pick. Therefore, all fields associated with portals reference that field with the thing/pick associated with the template. For example, if a template is associated with the "pistol" pick and the template contained a portal associated with the "range" field, that portal would display the contents of the "range" field of the "pistol" pick.
IMPORTANT! Since templates are associated with a thing or pick, templates may not contain portals that are precluded from having field associations. This means that table and chooser portals may not be used within templates.
