Welcome, Registration, and other StartingPoints; TWiki history & Wiki style; All the docs...
View   r7  >  r6  >  r5  >  r4  >  r3  >  r2  ...
TWikiTemplates 7 - 15 Sep 2001 - Main.MikeMannix
Line: 1 to 1
 
META TOPICPARENT name="WebHome"
Line: 63 to 63
 
  1. twiki/templates/$webName/$scriptName.tmpl
  2. twiki/templates/$scriptName.tmpl
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).
 Note: TWikiSkins can be defined to overload the standard templates.
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.
 

Template Topics


TWikiTemplates 6 - 15 Sep 2001 - Main.MikeMannix
Line: 1 to 1
 
META TOPICPARENT name="WebHome"
Line: 36 to 36
 
  • 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.
  • Note: The template directives work only for templates, they do not get processed in topic text.
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:
%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

Types of Template

There are two types of templates:

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

HTML Page Templates

TWiki 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

 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: 44 to 119
 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"}%
Changed:
<
<
>
>
 
%TMPL:DEF{"sep"}% | %TMPL:END%

Line: 95 to 169
 Each oops template basically just defines some variables and includes the base template that does the layout work.
Changed:
<
<
>
>
 
%TMPL:DEF{"titleaction"}% (test =titleaction=) %TMPL:END%

Line: 126 to 200
 With URL: .../bin/oops/Test/TestTopic2?template=oopstest&param1=WebHome&param2=WebNotify
Changed:
<
<
>
>
 
testscreen.gif
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"}%
 

Known Issues

  • 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.
Changed:
<
<
-- PeterThoeny - 23 Jul 2001
-- MikeMannix? - 30 Aug 2001
>
>
-- PeterThoeny - 23 Jul 2001
-- MikeMannix? - 14 Sep 2001
 
META FILEATTACHMENT attr="h" comment="Example of oopstest.tmpl rendered" date="999598142" name="testscreen.gif" path="C:\02_TWikiDocs\testscreen.gif" size="9460" user="MikeMannix" version="1.1"
META TOPICMOVED by="MikeMannix" date="1000277381" from="TWiki.TWikiTemplateSystem" to="TWiki.TWikiTemplates"

TWikiTemplates 5 - 14 Sep 2001 - Main.PeterThoeny
Line: 1 to 1
 
META TOPICPARENT name="WebHome"
Line: 8 to 8
 

Overview

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.
 

Major changes from the previous template system

Line: 26 to 26
 
  • 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 the form %TMPL:<key>% and %TMPL:<key>{"attr"}%.
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).
 
    • %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.
Deleted:
<
<
  • 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.
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.
 
  • Note: The template directives work only for templates, they do not get processed in topic text.

New Template System by Example

Line: 45 to 44
 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"}%
Deleted:
<
<
NOTE: Added a dot to escape rendering of variables, i.e. read %.WEB% as %WEB%.
 
Added:
>
>
 

Changed:
<
<
<table border="1" cellspacing="0" cellpadding="1"> <tr><td> <verbatim> %.TMPL:DEF{"sep"}% | %.TMPL:END%
>
>
%TMPL:DEF{"sep"}% | %TMPL:END%
 <html> <head>
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%">
  <meta name="robots" content="noindex"> </head> <body bgcolor="#FFFFFF"> <table width="100%" border="0" cellpadding="3" cellspacing="0"> <tr>
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>
  </td> <td>
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>
  </td> </tr>
Changed:
<
<
<tr bgcolor="%.WEBBGCOLOR%">
>
>
<tr bgcolor="%WEBBGCOLOR%">
  <td colspan="2">
Changed:
<
<
%.TMPL:P{"webaction"}%
>
>
%TMPL:P{"webaction"}%
  </td> </tr> </table>
Changed:
<
<

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

++ %TMPL:P{"heading"}% %TMPL:P{"message"}%
 <table width="100%" border="0" cellpadding="3" cellspacing="0">
Changed:
<
<
<tr bgcolor="%.WEBBGCOLOR%">
>
>
<tr bgcolor="%WEBBGCOLOR%">
  <td valign="top">
Changed:
<
<
Topic <b>TWikiTemplates</b> . { %.TMPL:P{"topicaction"}%
>
>
Topic <b>%TOPIC%</b> . { %TMPL:P{"topicaction"}%
  } </td> </tr> </table> </body>
Deleted:
<
<
</verbatim> </td></tr> </table >
 
Added:
>
>
 
Line: 103 to 98
 
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"}%

 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...
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"}%
 Test topicaction:
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"}%
  </table >
Line: 135 to 130
 
testscreen.gif
Added:
>
>

TWiki master template

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

Template variable: Defines:
Line: 146 to 143
 
%TMPL:DEF{"oops"}% Skeleton of oops dialog

Changed:
<
<
Example: preview.tmpl template
>
>
Example: oopspreview.tmpl template
 
%TMPL:INCLUDE{"twiki"}%
%TMPL:DEF{"titleaction"}% (oops) %TMPL:END%

Line: 163 to 160
 
  • 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.
Changed:
<
<
-- PeterThoeny? - 23 Jul 2001
>
>
-- PeterThoeny - 23 Jul 2001
 -- MikeMannix? - 30 Aug 2001
META FILEATTACHMENT attr="h" comment="Example of oopstest.tmpl rendered" date="999598142" name="testscreen.gif" path="C:\02_TWikiDocs\testscreen.gif" size="9460" user="MikeMannix" version="1.1"
META TOPICMOVED by="MikeMannix" date="1000277381" from="TWiki.TWikiTemplateSystem" to="TWiki.TWikiTemplates"

TWikiTemplates 4 - 12 Sep 2001 - Main.MikeMannix
Line: 1 to 1
 
META TOPICPARENT name="WebHome"
Line: 166 to 166
 -- PeterThoeny? - 23 Jul 2001
-- MikeMannix? - 30 Aug 2001
META FILEATTACHMENT attr="h" comment="Example of oopstest.tmpl rendered" date="999598142" name="testscreen.gif" path="C:\02_TWikiDocs\testscreen.gif" size="9460" user="MikeMannix" version="1.1"
Added:
>
>
META TOPICMOVED by="MikeMannix" date="1000277381" from="TWiki.TWikiTemplateSystem" to="TWiki.TWikiTemplates"

TWikiTemplates 3 - 08 Sep 2001 - Main.MikeMannix
Line: 1 to 1
 
META TOPICPARENT name="WebHome"
Deleted:
<
<

new topic for the final doc

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

see also for ref: orig TWikiTemplatingSystem?

 
Deleted:
<
<
 

TWiki Template System

Line: 10 to 4
 

TWiki Template System

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
 
Changed:
<
<

Overview

>
>

Overview

 
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.
 
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

 
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:
 
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;
 
Changed:
<
<

Functional Spec

>
>
  • defines common variables, like a standard separator (ex: "|"), in the base template;
 
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

 
  • Special template directives (or preprocessor commands) are embedded in normal templates.
  • Use of template directives is optional, templates work without them.
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"}%.
 
  • 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.
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.
 
Changed:
<
<

Examples

>
>

New Template System by Example

 
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.
 
Changed:
<
<

Base template oopsbase.tmpl

>
>

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"}%
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%.
 
Added:
>
>
 
<table border="1" cellspacing="0" cellpadding="1">
<tr><td>

Line: 99 to 93
 </td></tr> </table >
Added:
>
>
 
Changed:
<
<

Test template oopstest.tmpl

>
>

Test template oopstest.tmpl

 Each oops template basically just defines some variables and includes the base template that does the layout work.
Added:
>
>
 
Line: 129 to 125
  </table >
Added:
>
>
 
Changed:
<
<

Sample screen shot of oopstest.tmpl

>
>

Sample screen shot of oopstest.tmpl

 With URL: .../bin/oops/Test/TestTopic2?template=oopstest&param1=WebHome&param2=WebNotify
Added:
>
>
 
testscreen.gif
Added:
>
>
 
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.
 
Template variable: Defines:
Changed:
<
<
%TMPL:DEF{"sep"}% %TMPL:END% "|" separator
>
>
%TMPL:DEF{"sep"}% "|" separator
 
%TMPL:DEF{"htmldoctype"}% Start of all HTML pages
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
 
%TMPL:DEF{"oops"}% Skeleton of oops dialog
Changed:
<
<
I.e. the preview.tmpl template is now simply:
>
>
Example: preview.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%

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%
 %TMPL:P{"oops"}%
Added:
>
>

Known Issues

 
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.
 -- PeterThoeny? - 23 Jul 2001
-- MikeMannix? - 30 Aug 2001

Revision 7r7 - 15 Sep 2001 - 09:32:57 - MikeMannix?
Revision 6r6 - 15 Sep 2001 - 06:07:56 - MikeMannix?
Revision 5r5 - 14 Sep 2001 - 08:41:49 - PeterThoeny?
Revision 4r4 - 12 Sep 2001 - 06:49:41 - MikeMannix?
Revision 3r3 - 08 Sep 2001 - 14:52:33 - MikeMannix?
Revision 2r2 - 07 Sep 2001 - 10:07:14 - MikeMannix?
This site is powered by the TWiki collaboration platform.
All material on this collaboration platform is the property of the contributing authors.
All material marked as authored by Eben Moglen is available under the license terms CC-BY-SA version 4.
Syndicate this site RSSATOM