netfrag.org > TWiki > TWikiTemplates (r1.1 vs. r1.11)
TWiki . { Home? | Welcome | Register | Changes | Index | Search | Go }

 <<O>>  Difference Topic TWikiTemplates (r1.11 - 04 Dec 2001 - PeterThoeny?)
Line: 1 208 to 1 208
Changed:
<
<
testscreen.gif
>
>
testscreen.gif

 <<O>>  Difference Topic TWikiTemplates (r1.10 - 18 Sep 2001 - MikeMannix?)
Line: 1 11 to 1 11
Changed:
<
<
The new modular template system offers flexible, easy control over the layout of all TWiki pages. The master template approach groups parts that are shared by several templates - like headers and footers - in a common file. Special variables allow individual layouts to include parts from a master template - variables are mixed with regular HTML mark-up for template-specific content.
>
>
The new modular template system offers flexible, easy control over the layout of all TWiki pages. The master template approach groups parts that are shared by several templates - like headers and footers - in a common file. Special variables allow individual layouts to include parts from a master template - variables are mixed with regular HTML mark-up for template-specific content. Templates are used to define page layout, and also to supplydefault content for new pages.
Line: 56 to 57
Added:
>
>
Line: 71 to 73
Added:
>
>

 <<O>>  Difference Topic TWikiTemplates (r1.9 - 16 Sep 2001 - MikeMannix?)
Line: 1 5 to 1 5
Changed:
<
<

TWiki Template System

>
>

TWiki Templates

Line: 11 to 11
Changed:
<
<
The new modular template system is more flexible, efficient, and easily updated than the old set-up, where each template is a complete HTML file. The new master template approach places common templates parts, like headers and footers, in one shared file. This simplifies the conversion of templates into XHTML format, and provides a more versatile solution for templates and for TWikiSkins.
>
>
The new modular template system offers flexible, easy control over the layout of all TWiki pages. The master template approach groups parts that are shared by several templates - like headers and footers - in a common file. Special variables allow individual layouts to include parts from a master template - variables are mixed with regular HTML mark-up for template-specific content.
Line: 15 to 15
Changed:
<
<
The main difference is that templates are now defined using variables to include template parts. You change one stored instance of a common element to update all occurrences. The new system:
>
>
Where the old templates were each complete HTML documents, the new templates are defined using variables to include template parts from a master file. You can now change one instance of a common element to update all occurrences; previously, every affected template had to be updated. This simplifies the conversion of templates into XHTML format, and provides a more versatile solution for templates and for TWikiSkins. The new system:
Line: 37 to 35
Changed:
<
<
  • Note: The template directives work only for templates, they do not get processed in topic text.
>
>
  • NOTE: The template directives work only for templates, they do not get processed in topic text.

 <<O>>  Difference Topic TWikiTemplates (r1.8 - 15 Sep 2001 - PeterThoeny?)
Line: 1 83 to 1 85
Changed:
<
<
  1. The topic name specified by the templatetopic parameter.
>
>
  1. The topic name specified by the templatetopic CGI parameter.
Line: 93 to 95
Changed:
<
<
(date format is YYYYMMDD)
>
>
(date format is YYYYxMMxDD)
Line: 103 to 106
Changed:
<
<
<input type="text" name="topic" value="ExampleTopic%SERVERTIME{$year$mo$day}%" size="22"> <input type="hidden" name="templatetopic" value="ExampleTopicTemplate"> <input type="hidden" name="onlywikiname" value="on"> <input type="submit" value="Create"> (date format is YYYYMMDD)
>
>
<input type="text" name="topic" value="ExampleTopic%SERVERTIME{$yearx$mox$day}%" size="23" /> <input type="hidden" name="templatetopic" value="ExampleTopicTemplate" /> <input type="hidden" name="onlywikiname" value="on" /> <input type="submit" value="Create" /> (date format is <nop>YYYYxMMxDD)

 <<O>>  Difference Topic TWikiTemplates (r1.7 - 15 Sep 2001 - MikeMannix?)
Line: 1 66 to 1 66
Changed:
<
<
Note: $webName is the name of the web ( i.e. Main ), and $scriptName is the script ( i.e. view ).
>
>
Note: $webName is the name of the web (ex: Main), and $scriptName is the script (ex: view).
Line: 70 to 70
Changed:
<
<
Some special variables are used in templates ( especially view ) to show meta data - see Meta Data Rendering
>
>
Special variables are used in templates, especially in view, to display meta data.

 <<O>>  Difference Topic TWikiTemplates (r1.6 - 15 Sep 2001 - MikeMannix?)
Line: 1 39 to 1 39
Changed:
<
<

New Template System by Example

>
>

TWiki Master Template

All common parts are defined in a master template, twiki.tmpl, that all other templates use.

Template variable: Defines: down
%TMPL:DEF{"sep"}% "|" separator
%TMPL:DEF{"standardfooter"}% Footer, excluding revision and copyright parts
%TMPL:DEF{"simpleheader"}% Simple header with reduced links (ex: edit, attach, oops)
%TMPL:DEF{"oops"}% Skeleton of oops dialog
%TMPL:DEF{"standardheader"}% Standard header (ex: view, index, seach)
%TMPL:DEF{"htmldoctype"}% Start of all HTML pages

Types of Template

There are two types of templates:

  • HTML Page Templates: Defines layout of netfrag.org pages
  • Template Topics: Defines default text when you create a new topic

HTML Page Templates

netfrag.org uses HTML template files for all actions like topic view, edit, preview and so on. This allows you to change the look and feel of all pages by editing just some template files.

The template files are in the twiki/templates directory. As an example, twiki/templates/view.tmpl is the template file for the twiki/bin/view script. Templates can be overloaded per web. The following search order applies:

  1. twiki/templates/$webName/$scriptName.tmpl
  2. twiki/templates/$scriptName.tmpl

Note: $webName is the name of the web ( i.e. Main ), and $scriptName is the script ( i.e. view ).

Note: TWikiSkins can be defined to overload the standard templates.

Some special variables are used in templates ( especially view ) to show meta data - see Meta Data Rendering

Template Topics

Template topics define the default text for new topics. There are three types of template topics:

Topic Name: What it is:
WebTopicViewTemplate Help text shown when you view a non existing topic.
WebTopicNonWikiTemplate Help text shown when you view a non existing topic that has not a WikiName.
WebTopicEditTemplate Default text shown when you create a new topic.
All template topics are located in the TWiki web. The WebTopicEditTemplate can be overloaded. The following search order applies when you create a new topic:

  1. The topic name specified by the templatetopic parameter.
  2. WebTopicEditTemplate in the current web.
  3. WebTopicEditTemplate in the TWiki web.

Template Topics in Action

Here is an example for creating new topics based on a specific template topic:

  • New example topic: (date format is YYYYMMDD)

Above form asks for a topic name. A hidden input tag of name "templatetopic" specifies the ExampleTopicTemplate as the template topic. Here is the HTML source of the form:

<form name="new" action="%SCRIPTURLPATH%/edit%SCRIPTSUFFIX%/%WEB%/">
   * New example topic: 
     <input type="text" name="topic" value="ExampleTopic%SERVERTIME{$year$mo$day}%" size="22">
     <input type="hidden" name="templatetopic" value="ExampleTopicTemplate">
     <input type="hidden" name="onlywikiname" value="on">
     <input type="submit" value="Create"> (date format is YYYYMMDD)
</form>

The "onlywikiname" parameter enforces WikiWords for topic names.

Note: Use can use the %WIKIUSERNAME% and %DATE% variables in your topic templates as the signature; those variables are expanded when a new topic is created. The standard topic signature is:
-- %WIKIUSERNAME% - %DATE%

Templates by Example

Line: 47 to 122
Changed:
<
<
>
>
Line: 98 to 172
Changed:
<
<
>
>
Line: 129 to 203
Changed:
<
<
>
>
Line: 133 to 206
Deleted:
<
<

TWiki master template

All common template parts are defined in one master template, twiki.tmpl, that all other templates include.

Template variable: Defines:
%TMPL:DEF{"sep"}% "|" separator
%TMPL:DEF{"htmldoctype"}% Start of all HTML pages
%TMPL:DEF{"standardheader"}% Standard header (ex: view, index, seach)
%TMPL:DEF{"simpleheader"}% Simple header with reduced links (ex: edit, attach, oops)
%TMPL:DEF{"standardfooter"}% Footer, excluding revision and copyright parts
%TMPL:DEF{"oops"}% Skeleton of oops dialog

Example: oopspreview.tmpl template
%TMPL:INCLUDE{"twiki"}%
%TMPL:DEF{"titleaction"}% (oops) %TMPL:END%
%TMPL:DEF{"webaction"}% *Attention* %TMPL:END%
%TMPL:DEF{"heading"}% Topic is not saved yet %TMPL:END%
%TMPL:DEF{"message"}% Please go back in your browser and save the topic. %TMPL:END%
%TMPL:DEF{"topicaction"}%
%TMPL:END%
%TMPL:P{"oops"}%
Line: 163 to 211
Changed:
<
<
-- PeterThoeny - 23 Jul 2001
-- MikeMannix - 30 Aug 2001
>
>
-- PeterThoeny - 23 Jul 2001
-- MikeMannix - 14 Sep 2001

 <<O>>  Difference Topic TWikiTemplates (r1.5 - 14 Sep 2001 - PeterThoeny?)
Line: 1 11 to 1 11
Changed:
<
<
The new modular template system is more flexible, efficient, and easily updated than the old set-up, where each template is a complete HTML file. The new master template approach places common templates parts, like headers and footers, in one shared file. This simplifies the conversion of templates into XHTML format, and provides a more versatile solution for templates and for skins.
>
>
The new modular template system is more flexible, efficient, and easily updated than the old set-up, where each template is a complete HTML file. The new master template approach places common templates parts, like headers and footers, in one shared file. This simplifies the conversion of templates into XHTML format, and provides a more versatile solution for templates and for TWikiSkins.
Line: 29 to 29
Changed:
<
<
  • Initial set of directives:
    • %TMPL:INCLUDE{"file"}%: Includes a template file. The usual search path is applied.
>
>
  • Directives:
    • %TMPL:INCLUDE{"file"}%: Includes a template file. The template directory of the current web is searched first, then the templates root (twiki/templates).
Line: 34 to 33
Deleted:
<
<
  • New directives can be added over time when needed, ex: IF-THEN-ELSE.
Line: 37 to 36
Changed:
<
<
  • Templates and skins work transparently and interchangeably. For example, you can create a skin that overloads just the twiki.tmpl, like twiki.print.tmpl, that redefines the header and footer.
>
>
  • Templates and TWikiSkins work transparently and interchangeably. For example, you can create a skin that overloads just the twiki.tmpl, like twiki.print.tmpl, that redefines the header and footer.
Line: 48 to 46
Deleted:
<
<
NOTE: Added a dot to escape rendering of variables, i.e. read %.WEB% as %WEB%.
Line: 50 to 48
Added:
>
>
Line: 52 to 51
Changed:
<
<
<table border="1" cellspacing="0" cellpadding="1"> <tr><td> <verbatim> %.TMPL:DEF{"sep"}% | %.TMPL:END%
>
>
%TMPL:DEF{"sep"}% | %TMPL:END%
Line: 58 to 54
Changed:
<
<
<title> %.WIKITOOLNAME% . %.WEB% . %.TOPIC% %.TMPL:P{"titleaction"}%</title> <base href="%.SCRIPTURL%/view%.SCRIPTSUFFIX%/%.WEB%/%.TOPIC%">
>
>
<title> %WIKITOOLNAME% . %WEB% . %TOPIC% %.TMPL:P{"titleaction"}%</title> <base href="%SCRIPTURL%/view%SCRIPTSUFFIX%/%WEB%/%TOPIC%">
Line: 65 to 61
Changed:
<
<
<td bgcolor="%.WEBBGCOLOR%" rowspan="2" valign="top" width="1%"> <a href="%.WIKIHOMEURL%"> <img src="%.PUBURLPATH%/wikiHome.gif" border="0"></a>
>
>
<td bgcolor="%WEBBGCOLOR%" rowspan="2" valign="top" width="1%"> <a href="%WIKIHOMEURL%"> <img src="%PUBURLPATH%/wikiHome.gif" border="0"></a>
Line: 70 to 66
Changed:
<
<
<b>%.WIKITOOLNAME% . %.WEB% . </b><font size="+2"> <B>%.TOPIC%</b> %.TMPL:P{"titleaction"}%</font>
>
>
<b>%WIKITOOLNAME% . %WEB% . </b><font size="+2"> <B>%TOPIC%</b> %TMPL:P{"titleaction"}%</font>
Line: 74 to 70
Changed:
<
<
<tr bgcolor="%.WEBBGCOLOR%">
>
>
<tr bgcolor="%WEBBGCOLOR%">
Line: 76 to 72
Changed:
<
<
%.TMPL:P{"webaction"}%
>
>
%TMPL:P{"webaction"}%
Line: 80 to 76
Changed:
<
<

++ %.TMPL:P{"heading"}% %.TMPL:P{"message"}%
>
>

++ %TMPL:P{"heading"}% %TMPL:P{"message"}%
Line: 83 to 79
Changed:
<
<
<tr bgcolor="%.WEBBGCOLOR%">
>
>
<tr bgcolor="%WEBBGCOLOR%">
Line: 85 to 81
Changed:
<
<
Topic <b>TWikiTemplates</b> . { %.TMPL:P{"topicaction"}%
>
>
Topic <b>%TOPIC%</b> . { %TMPL:P{"topicaction"}%
Line: 92 to 87
Deleted:
<
<
</verbatim> </td></tr> </table >
Line: 95 to 89
Added:
>
>
Line: 106 to 101
Changed:
<
<
%.TMPL:DEF{"titleaction"}% (test =titleaction=) %.TMPL:END%
%.TMPL:DEF{"webaction"}% test =webaction= %.TMPL:END%
%.TMPL:DEF{"heading"}%
Test heading %.TMPL:END%
%.TMPL:DEF{"message"}%
>
>
%TMPL:DEF{"titleaction"}% (test =titleaction=) %TMPL:END%
%TMPL:DEF{"webaction"}% test =webaction= %TMPL:END%
%TMPL:DEF{"heading"}%
Test heading %TMPL:END%
%TMPL:DEF{"message"}%
Line: 115 to 110
Changed:
<
<
  • Param1: %PARAM1%
  • Param2: %PARAM2%
  • Param3: %PARAM3%
  • Param4: %PARAM4%
%.TMPL:END% %.TMPL:DEF{"topicaction"}%
>
>
  • Param1: %PARAM1%
  • Param2: %PARAM2%
  • Param3: %PARAM3%
  • Param4: %PARAM4%
%TMPL:END% %TMPL:DEF{"topicaction"}%
Line: 122 to 117
Changed:
<
<
OK? %.TMPL:P{"sep"}% Register? %.TMPL:END% %.TMPL:INCLUDE{"oopsbase"}%
>
>
[[%WEB%.%TOPIC%][OK]] %TMPL:P{"sep"}% [[%TWIKIWEB%.TWikiRegistration][Register]] %TMPL:END% %TMPL:INCLUDE{"oopsbase"}%
Line: 137 to 133
Added:
>
>

TWiki master template

Line: 149 to 146
Changed:
<
<
Example: preview.tmpl template
>
>
Example: oopspreview.tmpl template
Line: 166 to 163
Changed:
<
<
-- PeterThoeny? - 23 Jul 2001
>
>
-- PeterThoeny - 23 Jul 2001

 <<O>>  Difference Topic TWikiTemplates (r1.4 - 12 Sep 2001 - MikeMannix?)
Line: 1 168 to 1 169
Added:
>
>
META TOPICMOVED MikeMannix date="1000277381" from="TWiki.TWikiTemplateSystem" to="TWiki.TWikiTemplates"

 <<O>>  Difference Topic TWikiTemplates (r1.3 - 08 Sep 2001 - MikeMannix?)
Line: 1 3 to 1 2
Deleted:
<
<

new topic for the final doc

Slightly edited down, but waiting for new docs, hopefully.

see also for ref: orig TWikiTemplatingSystem?

Line: 13 to 7
Changed:
<
<
Define the templates used to render all HTML pages displayed in TWiki
>
>
Definition of the templates used to render all HTML pages displayed in TWiki
Line: 15 to 9
Changed:
<
<

Overview

>
>

Overview

Line: 17 to 11
Changed:
<
<
We have a need for more advanced template handling. As JohnTalintyre? pointed out in CommonHeaderFooterTemplate? it makes sense to separate the header and footer into one file so that it can be easily altered (or even overloaded by a skin). Also the oops dialog messages are all identical except for a few variables like heading, and so on.
>
>
The new modular template system is more flexible, efficient, and easily updated than the old set-up, where each template is a complete HTML file. The new master template approach places common templates parts, like headers and footers, in one shared file. This simplifies the conversion of templates into XHTML format, and provides a more versatile solution for templates and for skins.
Line: 19 to 13
Changed:
<
<
Using external modules like the TemplateToolkit? would be one way to go, but this will add a lot of baggage to TWiki.
>
>

Major changes from the previous template system

Line: 21 to 15
Changed:
<
<

Needs of the TWiki templating system

>
>
The main difference is that templates are now defined using variables to include template parts. You change one stored instance of a common element to update all occurrences. The new system:
Line: 23 to 17
Changed:
<
<
  • Separate common parts into one (or more) base template file(s) and include that from other template files like view.tmpl.
  • Define common variables like a "|" separator in the base template and use them in other template files
  • Define variable text in templates (i.e. view.tmpl) and pass them to the base template
>
>
  • separates a set of common template parts into a base template that is included by all of the related templates;
Line: 27 to 19
Changed:
<
<

Functional Spec

>
>
  • defines common variables, like a standard separator (ex: "|"), in the base template;
Line: 29 to 21
Changed:
<
<
I tried to define a simple but powerful solution that can be extended over time. Here we go:
>
>
  • defines variable text in the individual templates and passes it back to the base template.

Functional Specifications

Line: 33 to 27
Changed:
<
<
  • All template preprocessing is done in &TWiki::Store::readTemplate() so that the caller simply gets an expanded template file (the same as before)
  • Directives are of form %TMPL:<key>% and %TMPL:<key>{"attr"}%.
>
>
  • All template preprocessing is done in &TWiki::Store::readTemplate() so that the caller simply gets an expanded template file (the same as before).
  • Directives are of the form %TMPL:<key>% and %TMPL:<key>{"attr"}%.
Line: 40 to 34
Changed:
<
<
  • New directives can be added over time when needed, i.e. IF-THEN-ELSE.
  • Variables live in a global name space, there is no parameter passing.
  • Two pass processing, so that you can use a variable before declaring it or after.
  • Templates and skins work transparently and interchangeably. You could for example define a new skin just for the header & footer and keep the other template files unchanged.
  • Note: The template directive work only for templates, they do not get processed in topic text.
>
>
  • New directives can be added over time when needed, ex: IF-THEN-ELSE.
  • Variables are live in a global name space, there is no parameter passing.
  • Two-pass processing, so that you can use a variable before declaring it or after.
  • Templates and skins work transparently and interchangeably. For example, you can create a skin that overloads just the twiki.tmpl, like twiki.print.tmpl, that redefines the header and footer.
  • Note: The template directives work only for templates, they do not get processed in topic text.
Line: 47 to 40
Changed:
<
<

Examples

>
>

New Template System by Example

Line: 49 to 42
Changed:
<
<
Attached is an example of an oops base template oopsbase.tmpl and a example oops dialog oopstest.tmpl which is based on the base template. This is not the version that will go into the release, it is just a quick hack.
>
>
Attached is an example of an oops base template oopsbase.tmpl and a example oops dialog oopstest.tmpl which is based on the base template. NOTE: This isn't the release version, just a quick, simple demo.
Line: 51 to 44
Changed:
<
<

Base template oopsbase.tmpl

>
>

Base template oopsbase.tmpl

Line: 55 to 48
Changed:
<
<
Note: Added a dot to escape rendering of variables, i.e. read %.WEB% as %WEB%.
>
>
NOTE: Added a dot to escape rendering of variables, i.e. read %.WEB% as %WEB%.
Line: 56 to 50
Added:
>
>
Line: 101 to 96
Added:
>
>
Line: 104 to 99
Changed:
<
<

Test template oopstest.tmpl

>
>

Test template oopstest.tmpl

Line: 107 to 103
Added:
>
>
Line: 131 to 128
Added:
>
>
Line: 133 to 130
Changed:
<
<

Sample screen shot of oopstest.tmpl

>
>

Sample screen shot of oopstest.tmpl

Line: 136 to 134
Added:
>
>
Line: 137 to 136
Added:
>
>
Line: 139 to 138
Changed:
<
<

Comments and feedback

  • The itching factor to put this into the upcoming release is to easy the pending converstion of the templates into XHTML format and to have a more flexible solution for templates and skins.
  • Is the terminology OK?
  • Is the spec OK?
  • Are there any other directives that are needed urgently?
  • One drawback by using the directives is that you can only test a template from within TWiki. This is because you don't have a text that has a linear flow when you use TMPL:DEF, TMPL:P and TMPL:INCLUDE.

-- PeterThoeny? - 21 Jul 2001

  • It's probably more readable to enforce variables being defined before use, which would avoid need for slower two-pass processing.
    • [ PeterThoeny? ] You need two-pass processing because you need to define the "|" separator in the included template onone side, and on the other side define variables for the included template. The processing happens as regex in memory, so there is no mesurable speed penalty.
  • It would be nice to simplify the syntax a bit, e.g. not using "" around variable names (they don't really need it, unlike filenames), and not using braces - however, this is not a big deal and there is some merit in keeping consistent with the current TWiki syntax.
    • [ PeterThoeny? ] The templating system uses the standard internal TWiki function to parse variable attributes. The "" can be skipped (is possible but is not documented).

Please have a look at the latest templates in the TWikiAlphaRelease?. There is now one master template called twiki.tmpl that all other templates include (well, will include when all done). The idea is to define all common parts of the templates in twiki.tmpl and simply use that from all other templates.

>
>
All common template parts are defined in one master template, twiki.tmpl, that all other templates include.
Line: 158 to 141
Changed:
<
<
%TMPL:DEF{"sep"}% %TMPL:END% "|" separator
>
>
%TMPL:DEF{"sep"}% "|" separator
Line: 160 to 143
Changed:
<
<
%TMPL:DEF{"standardheader"}% Standard header (for view, rdiff, ...
%TMPL:DEF{"simpleheader"}% Simple header with reduced links (for edit, attach, oops,...)
%TMPL:DEF{"standardfooter"}% Footer, excluding revision part and copyright part
>
>
%TMPL:DEF{"standardheader"}% Standard header (ex: view, index, seach)
%TMPL:DEF{"simpleheader"}% Simple header with reduced links (ex: edit, attach, oops)
%TMPL:DEF{"standardfooter"}% Footer, excluding revision and copyright parts
Line: 165 to 148
Changed:
<
<
I.e. the preview.tmpl template is now simply:
>
>
Example: preview.tmpl template
Line: 171 to 155
Changed:
<
<
%TMPL:DEF{"message"}% Please go back in your browser and save the topic. %TMPL:END% %TMPL:DEF{"topicaction"}% %TMPL:END%
>
>
%TMPL:DEF{"message"}% Please go back in your browser and save the topic. %TMPL:END% %TMPL:DEF{"topicaction"}% %TMPL:END%
Line: 175 to 160
Added:
>
>

Known Issues

Line: 177 to 164
Changed:
<
<
With this it should be possible to create a skin that overloads just the twiki.tmpl, i.e. a twiki.print.tmpl that redefines the header and footer.
>
>
  • A drawback of referring to a master template is that you can only test a template from within TWiki, where the include variables are resolved. In the previous system, each template is a structurally complete HTML document with a .tmpl filename extension - it contains unresolved %VARIABLES%, but can still be previewed directly in a browser.

 <<O>>  Difference Topic TWikiTemplates (r1.2 - 07 Sep 2001 - MikeMannix?)
Line: 1 11 to 1 11
Changed:
<
<

TWiki Template System

>
>

TWiki Template System

Line: 15 to 15
Changed:
<
<

Overview

>
>

Overview

Line: 21 to 21
Changed:
<
<

Needs of the TWiki templating system

>
>

Needs of the TWiki templating system

Line: 27 to 27
Changed:
<
<

Functional Spec

>
>

Functional Spec

Line: 47 to 47
Changed:
<
<

Examples

>
>

Examples

Line: 51 to 51
Changed:
<
<
Base template oopsbase.tmpl
>
>

Base template oopsbase.tmpl

Line: 104 to 104
Changed:
<
<
Test template oopstest.tmpl
>
>

Test template oopstest.tmpl

Line: 133 to 133
Changed:
<
<
Sample screen shot of oopstest.tmpl
>
>

Sample screen shot of oopstest.tmpl

Line: 139 to 139
Changed:
<
<

Comments and feedback

>
>

Comments and feedback


 <<O>>  Difference Topic TWikiTemplates (r1.1 - 04 Sep 2001 - MikeMannix?)
Line: 1 to 1
Added:
>
>
META TOPICPARENT WebHome

new topic for the final doc

Slightly edited down, but waiting for new docs, hopefully.

see also for ref: orig TWikiTemplatingSystem?

TWiki Template System

Define the templates used to render all HTML pages displayed in TWiki

Overview

We have a need for more advanced template handling. As JohnTalintyre? pointed out in CommonHeaderFooterTemplate? it makes sense to separate the header and footer into one file so that it can be easily altered (or even overloaded by a skin). Also the oops dialog messages are all identical except for a few variables like heading, and so on.

Using external modules like the TemplateToolkit? would be one way to go, but this will add a lot of baggage to TWiki.

Needs of the TWiki templating system

  • Separate common parts into one (or more) base template file(s) and include that from other template files like view.tmpl.
  • Define common variables like a "|" separator in the base template and use them in other template files
  • Define variable text in templates (i.e. view.tmpl) and pass them to the base template

Functional Spec

I tried to define a simple but powerful solution that can be extended over time. Here we go:

  • Special template directives (or preprocessor commands) are embedded in normal templates.
  • Use of template directives is optional, templates work without them.
  • All template preprocessing is done in &TWiki::Store::readTemplate() so that the caller simply gets an expanded template file (the same as before)
  • Directives are of form %TMPL:<key>% and %TMPL:<key>{"attr"}%.
  • Initial set of directives:
    • %TMPL:INCLUDE{"file"}%: Includes a template file. The usual search path is applied.
    • %TMPL:DEF{"var"}%: Define a variable. Text between this and the END directive is not returned, but put into a hash for later use.
    • %TMPL:END%: Ends variable definition.
    • %TMPL:P{"var"}%: Prints a previously defined variable.
  • New directives can be added over time when needed, i.e. IF-THEN-ELSE.
  • Variables live in a global name space, there is no parameter passing.
  • Two pass processing, so that you can use a variable before declaring it or after.
  • Templates and skins work transparently and interchangeably. You could for example define a new skin just for the header & footer and keep the other template files unchanged.
  • Note: The template directive work only for templates, they do not get processed in topic text.

Examples

Attached is an example of an oops base template oopsbase.tmpl and a example oops dialog oopstest.tmpl which is based on the base template. This is not the version that will go into the release, it is just a quick hack.

Base template oopsbase.tmpl

The first line declares the delimiter variable called "sep", used to separate multiple link items. The variable can be called anywhere by writing %TMPL:P{"sep"}%

Note: Added a dot to escape rendering of variables, i.e. read %.WEB% as %WEB%.

<table border="1" cellspacing="0" cellpadding="1">
<tr><td>
<verbatim>
%.TMPL:DEF{"sep"}% | %.TMPL:END%
<html>
<head>
  <title> %.WIKITOOLNAME% . %.WEB% . %.TOPIC% %.TMPL:P{"titleaction"}%</title>
  <base href="%.SCRIPTURL%/view%.SCRIPTSUFFIX%/%.WEB%/%.TOPIC%">
  <meta name="robots" content="noindex">
</head>
<body bgcolor="#FFFFFF">
<table width="100%" border="0" cellpadding="3" cellspacing="0">
  <tr>
    <td bgcolor="%.WEBBGCOLOR%" rowspan="2" valign="top" width="1%">
      <a href="%.WIKIHOMEURL%">
      <img src="%.PUBURLPATH%/wikiHome.gif" border="0"></a>
    </td>
    <td>
      <b>%.WIKITOOLNAME% . %.WEB% . </b><font size="+2">
      <B>%.TOPIC%</b> %.TMPL:P{"titleaction"}%</font>
    </td>
  </tr>
  <tr bgcolor="%.WEBBGCOLOR%">
    <td colspan="2">
      %.TMPL:P{"webaction"}%
    </td>
  </tr>
</table>
--- ++ %.TMPL:P{"heading"}%
%.TMPL:P{"message"}%
<table width="100%" border="0" cellpadding="3" cellspacing="0">
  <tr bgcolor="%.WEBBGCOLOR%">
    <td valign="top">
      Topic <b>TWikiTemplates</b> . {
        %.TMPL:P{"topicaction"}%
      }
    </td>
  </tr>
</table>
</body>
</verbatim>
</td></tr>
</table >

Test template oopstest.tmpl

Each oops template basically just defines some variables and includes the base template that does the layout work.

%.TMPL:DEF{"titleaction"}% (test =titleaction=) %.TMPL:END%
%.TMPL:DEF{"webaction"}% test =webaction= %.TMPL:END%
%.TMPL:DEF{"heading"}%
Test heading %.TMPL:END%
%.TMPL:DEF{"message"}%
Test =message=. Blah blah blah blah blah blah blah blah blah blah blah...

   * Some more blah blah blah blah blah blah blah blah blah blah...
   * Param1: %PARAM1%
   * Param2: %PARAM2%
   * Param3: %PARAM3%
   * Param4: %PARAM4%
%.TMPL:END%
%.TMPL:DEF{"topicaction"}%
Test =topicaction=:
[[%.WEB%.%TOPIC%][OK]] %.TMPL:P{"sep"}%
[[%.TWIKIWEB%.TWikiRegistration][Register]] %.TMPL:END%
%.TMPL:INCLUDE{"oopsbase"}%

Sample screen shot of oopstest.tmpl

With URL: .../bin/oops/Test/TestTopic2?template=oopstest&param1=WebHome&param2=WebNotify

testscreen.gif

Comments and feedback

  • The itching factor to put this into the upcoming release is to easy the pending converstion of the templates into XHTML format and to have a more flexible solution for templates and skins.
  • Is the terminology OK?
  • Is the spec OK?
  • Are there any other directives that are needed urgently?
  • One drawback by using the directives is that you can only test a template from within TWiki. This is because you don't have a text that has a linear flow when you use TMPL:DEF, TMPL:P and TMPL:INCLUDE.

-- PeterThoeny? - 21 Jul 2001

  • It's probably more readable to enforce variables being defined before use, which would avoid need for slower two-pass processing.
    • [ PeterThoeny? ] You need two-pass processing because you need to define the "|" separator in the included template onone side, and on the other side define variables for the included template. The processing happens as regex in memory, so there is no mesurable speed penalty.
  • It would be nice to simplify the syntax a bit, e.g. not using "" around variable names (they don't really need it, unlike filenames), and not using braces - however, this is not a big deal and there is some merit in keeping consistent with the current TWiki syntax.
    • [ PeterThoeny? ] The templating system uses the standard internal TWiki function to parse variable attributes. The "" can be skipped (is possible but is not documented).

Please have a look at the latest templates in the TWikiAlphaRelease?. There is now one master template called twiki.tmpl that all other templates include (well, will include when all done). The idea is to define all common parts of the templates in twiki.tmpl and simply use that from all other templates.

Template variable: Defines:
%TMPL:DEF{"sep"}% %TMPL:END% "|" separator
%TMPL:DEF{"htmldoctype"}% Start of all HTML pages
%TMPL:DEF{"standardheader"}% Standard header (for view, rdiff, ...
%TMPL:DEF{"simpleheader"}% Simple header with reduced links (for edit, attach, oops,...)
%TMPL:DEF{"standardfooter"}% Footer, excluding revision part and copyright part
%TMPL:DEF{"oops"}% Skeleton of oops dialog

I.e. the preview.tmpl template is now simply:

%TMPL:INCLUDE{"twiki"}%
%TMPL:DEF{"titleaction"}% (oops) %TMPL:END%
%TMPL:DEF{"webaction"}% *Attention* %TMPL:END%
%TMPL:DEF{"heading"}% Topic is not saved yet %TMPL:END%
%TMPL:DEF{"message"}%
  Please go back in your browser and save the topic. %TMPL:END%
%TMPL:DEF{"topicaction"}% %TMPL:END%
%TMPL:P{"oops"}%

With this it should be possible to create a skin that overloads just the twiki.tmpl, i.e. a twiki.print.tmpl that redefines the header and footer.

-- PeterThoeny? - 23 Jul 2001
-- MikeMannix - 30 Aug 2001

META FILEATTACHMENT testscreen.gif attr="h" comment="Example of oopstest.tmpl rendered" date="999598142" path="C:\02_TWikiDocs\testscreen.gif" size="9460" user="MikeMannix" version="1.1"

Topic TWikiTemplates . { View | Diffs | r1.11 | > | r1.10 | > | r1.9 | More }    output as: { }
Revision r1.1 - 04 Sep 2001 - 10:07 - MikeMannix?
Revision r1.11 - 04 Dec 2001 - 10:21 - PeterThoeny?