A reasonably skilled template author should be able to implement a template without any assistance from the developer, other than @@ -49,8 +49,8 @@ where users may assemble different types of content to their liking.
(graphic)
-See include and -master. See also Building reusable layout components and +
See include and +master. See also Building reusable layout components and Using master templates.
Template authors need a simple mechanism for declaring @@ -60,13 +60,13 @@ include a search box. The data dictionary specifies available properties as well as the set of valid values when appropriate.
(graphic)
-See property.
+See property.
Designers often need to tailor the layout depending on the specific data being presented. For example, when presenting a list of library books that a user has checked out, the designer might want to highlight the overdue ones in red.
-See if..else.
+See if..else.
Dynamic pages often present lists of values or records, each of which typically represents the results of a database query. @@ -87,9 +87,9 @@
To accomodate these type of scenarios, the template parser sets some additional variables that the designer can reference to vary the layout from item to item.
- - + +Template tags are processed by the server each time a page is @@ -102,8 +102,8 @@ However, if a page layout depends on the presence or absence of whitespace between HTML tags for proper display, then special care must be taken with dynamic tags to avoid adding whitespace.
When placed on a line by themselves, tags that are containers -for template sections (grid, if, and -multiple) will cause newlines to be added to the page at +for template sections (grid, if, and +multiple) will cause newlines to be added to the page at the beginning and end of the section. This can be avoided by crowding the start and end tags like so:
<td><if %x% eq 5><img src="five.gif"></if>