Changeset 522 for branches/Release04x02/data/TWiki

Timestamp:

11/10/08 13:52:10 (4 years ago)

Author:

CrawfordCurrie

Message:

Item109: outvoted on the templates terminilogy. Skin templates it is.

Location:

branches/Release04x02/data/TWiki

Files:

• . (modified) (1 prop)
• DefaultPreferences.txt (modified) (1 prop)
• InstantEnhancements.txt (modified) (2 diffs)
• MainFeatures.txt (modified) (1 diff)
• MetaData.txt (modified) (1 prop)
• PresentationTemplates.txt (deleted)
• ShortcutMacros.txt (modified) (1 prop)
• SkinTemplates.txt (copied) (copied from trunk/core/data/TWiki/SkinTemplates.txt)
• TWikiDocumentation.txt (modified) (1 diff)
• TWikiGlossary.txt (modified) (1 diff)
• TWikiJavascripts.txt (modified) (1 diff)
• TWikiReferenceManual.txt (modified) (1 diff)
• TWikiSkins.txt (modified) (4 diffs)
• UserAuthentication.txt (modified) (1 prop)

branches/Release04x02/data/TWiki/InstantEnhancements.txt

@@ -36 +36 @@
 ---+++ Set Page Background Color 
 
-Without getting into the [[presentation templates]] system yet, you can easily edit the ==view.tmpl== (in the =templates= directory). In the HTML at the top, the body tag has the page background hardcoded to white ==bgcolor="#ffffff"==. You can change that color value to new variable. First, define a new preferences variable in the site-level [[%LOCALSITEPREFS%]], e.g. =* Set =PAGEBGCOLOR = #d0d0d0=, then edit the ==view.tmpl== template file and change ==bgcolor="#ffffff"== to ==bgcolor="%<nop>PAGEBGCOLOR%"==. If you want, you can set the page background color individually per web, simple add a =* Set =PAGEBGCOLOR = #d0d0d0= bullet to the WebPreferences to overload the site-level preferences. (Without font color control, you'll have to stick to light colors.)
+Without getting into the [[skin templates]] system yet, you can easily edit the ==view.tmpl== (in the =templates= directory). In the HTML at the top, the body tag has the page background hardcoded to white ==bgcolor="#ffffff"==. You can change that color value to new variable. First, define a new preferences variable in the site-level [[%LOCALSITEPREFS%]], e.g. =* Set =PAGEBGCOLOR = #d0d0d0=, then edit the ==view.tmpl== template file and change ==bgcolor="#ffffff"== to ==bgcolor="%<nop>PAGEBGCOLOR%"==. If you want, you can set the page background color individually per web, simple add a =* Set =PAGEBGCOLOR = #d0d0d0= bullet to the WebPreferences to overload the site-level preferences. (Without font color control, you'll have to stick to light colors.)
 
 ---+++ Titles-Only Topic List - !WebTopicList
@@ -174 +174 @@
 ---++ Add Your Favorite <nop>JavaScript Features
 
-You're no doubt familiar or better with HTML, JS, and "webmastering". Without getting into the [[presentation templates]] system yet, you can easily edit the ==view.pattern.tmpl== (if you are using default pattern skin) (in the =templates= directory) for some dramatic effects. The top of the template is mostly regular HTML with some variables. Open up some space in the ==&lt;head&gt;== area, and you can drop in reliable <nop>JavaScripts - a pop-up window script, for example - or tag it as an external script.
+You're no doubt familiar or better with HTML, JS, and "webmastering". Without getting into the [[skin templates]] system yet, you can easily edit the ==view.pattern.tmpl== (if you are using default pattern skin) (in the =templates= directory) for some dramatic effects. The top of the template is mostly regular HTML with some variables. Open up some space in the ==&lt;head&gt;== area, and you can drop in reliable <nop>JavaScripts - a pop-up window script, for example - or tag it as an external script.
 
    * %T% Obviously, you can do the same - place a link to an external stylesheet as well. If you set values for standard HTML tags, you can control a good deal of the type size, style and color with out adding CSS tags. __example__

branches/Release04x02/data/TWiki/MainFeatures.txt

@@ -15 +15 @@
    * *Variables:* Use [[TWikiVariables][variables]] to dynamically compose your pages. This allows you for example to dynamically build a table of contents, include other pages, or show a search result embedded in a page.
    * *TWiki plugins:* Easily install program enhancements using external [[TWikiPlugins][plug-in modules]]. Developers can create plug-ins in Perl using the TWiki Plugin API.
-   * *Templates and skins:* A flexible [[PresentationTemplates][templating system]] separates program logic and presentation. [[Skins]] overwrite template headers and footers; page content is unaffected.
+   * *Templates and skins:* A flexible [[SkinTemplates][templating system]] separates program logic and presentation. [[Skins]] overwrite template headers and footers; page content is unaffected.
    * *Managing pages:* Individual pages can be renamed, moved and deleted through the browser.
    * *Managing users:* Web-based [[TWikiRegistration][user registration]] and [[ChangePassword][change of password]].

branches/Release04x02/data/TWiki/TWikiDocumentation.txt

@@ -63 +63 @@
 [[#PageTop][Back to top]]
 ------
-%INCLUDE{"PresentationTemplates"}%
+%INCLUDE{"SkinTemplates"}%
 
 [[#PageTop][Back to top]]

branches/Release04x02/data/TWiki/TWikiGlossary.txt

@@ -15 +15 @@
 | Site: | A TWiki installation consisting of one or more _webs_. [[TWikiSite][Details...]] |
 | Skin: | Skins overlay regular _templates_ with alternate header/footer layout of _pages_; topic text is not affected. Skins are typically enabled site-wide or per _web_. [[TWikiSkins][Details...]] |
-| Templates: | (1) Regular templates define header/footer layout of _pages_; topic text is not affected. (2) Template topics set the default content for new _topics_. [[PresentationTemplates][Details...]] |
+| Templates: | (1) Regular templates define header/footer layout of _pages_; topic text is not affected. (2) Template topics set the default content for new _topics_. [[SkinTemplates][Details...]] |
 | Topic: | The content of a TWiki _page_, consisting of text, an optional _form_ and optional _attachments_. It has a WikiName that's unique within its _web_. [[TopicsAndWebs][Details...]] |
 | TWiki: | A web-based collaboration platform targeting the corporate world. Contraction of "TakeFive Wiki". By chance, also happens to be the name of the AI robot star of the Buck Rogers 1979 movie and TV series. Features include browser based editing, automatic linking of text (based on ideas of the original <nop>WikiWikiWeb), revision control, file _attachments_, _form_ handling, _preferences_ settings, access control and more. [[http://TWiki.org/][Details...]] |

branches/Release04x02/data/TWiki/TWikiJavascripts.txt

@@ -1 +1 @@
 ---+ Javascripts
 
-This topic contains javascript files that are included by presentation templates, and may be used by skin templates and in topics.
+This topic contains javascript files that are included by skin templates, and may be used by skin templates and in topics.
 
-__Related Topics:__ PresentationTemplates, [[Skins]]
+__Related Topics:__ SkinTemplates, [[Skins]]
 
         * Set ALLOWTOPICCHANGE = %USERSWEB%.AdminGroup

branches/Release04x02/data/TWiki/TWikiReferenceManual.txt

@@ -20 +20 @@
    1. [[FileAttachment][File Attachment]]
    1. [[TWikiForms][TWiki Forms]]
-   1. [[Presentation Templates]]
+   1. [[Skin Templates]]
    1. [[TWikiSkins][TWiki Skins (visual layout)]]
    1. [[MetaData]]

branches/Release04x02/data/TWiki/TWikiSkins.txt

@@ -9 +9 @@
 ---++ Overview
 
-TWiki uses [[presentation templates]] as the basis of all the screens it uses to interact with users. Each screen has an associated template file that contains the basic layout of the screen. This is then filled in by the code to generate what you see in the browser.
+TWiki uses [[skin templates]] as the basis of all the screens it uses to interact with users. Each screen has an associated template file that contains the basic layout of the screen. This is then filled in by the code to generate what you see in the browser.
 
 TWiki ships with a default set of template files that give a very basic, CSS-themable, look-and-feel. TWiki also includes support for _skins_ that can be selected to give different, more sophisticated, look and feels. A default TWiki installation will usually start up with the PatternSkin already selected. Skins may also be defined by third parties and loaded into a TWiki installation to give more options. To see how TWiki looks when *no* skin is selected, [[%SCRIPTURL{"view"}%/%WEB%/%TOPIC%?skin=not_a_skin][view this topic with a non-existant skin]].
@@ -32 +32 @@
 You may want to define your own skin, for example to comply with corporate web guidelines, or because you have a aesthetic vision that you want to share. There are a couple of places you an start doing this.
 
-The [[presentation templates]] used for skins are located in the =twiki/templates= directory and are named according to the skin: ==<scriptname>.<skin>.tmpl==. Skin files may also be defined in TWiki topics - see PresentationTemplates for details.
-
-To start creating a new skin, copy the default presentation templates (like =view.tmpl=), or copy an existing skin to use as a base for your own skin. You should only need to copy the files you intend to customise, as TWiki can be configured to fall back to another skin if a template is not defined in your skin. Name the files as described above (for example =view.myskin.tmpl=.
+The [[skin templates]] used for skins are located in the =twiki/templates= directory and are named according to the skin: ==<scriptname>.<skin>.tmpl==. Skin files may also be defined in TWiki topics - see SkinTemplates for details.
+
+To start creating a new skin, copy the default skin templates (like =view.tmpl=), or copy an existing skin to use as a base for your own skin. You should only need to copy the files you intend to customise, as TWiki can be configured to fall back to another skin if a template is not defined in your skin. Name the files as described above (for example =view.myskin.tmpl=.
 
 If you use PatternSkin as your starting point, and you want to modify the layout, colors or even the templates to suit your own needs, have a look first at the topics PatternSkinCustomization and PatternSkinCssCookbook.
@@ -182 +182 @@
 Controlling the look and feel of attachment tables is a little bit more complex than for the rest of a skin. By default, the attachment table is a standard TWiki table, and the look is controlled in the same way as other tables. In a very few cases you may want to change the _content_ of the table as well.
 
-The format of standard attachment tables is defined through the use of special _TWiki template macros_ which by default, are defined in the =attachtables.tmpl= template using the =%TMPL:DEF= macro syntax described in PresentationTemplates. These macros are:
+The format of standard attachment tables is defined through the use of special _TWiki template macros_ which by default, are defined in the =attachtables.tmpl= template using the =%TMPL:DEF= macro syntax described in SkinTemplates. These macros are:
 | *Macro* | *Description* |
 | =ATTACH:files:header= | Standard title bar |
@@ -221 +221 @@
 TWiki uses a _skin search path_, which lets you combine skins additively. The skin path is defined using a combination of TWikiVariables and URL parameters.
 
-TWiki works by asking for a template for a particular function - for example, 'view'. The detail of how templates are searched for is described in PresentationTemplates, but in summary, the templates directory is searched for a file called <code>view.</code><i>skin</i><code>.tmpl</code>, where _skin_ is the name of the skin e.g. =pattern=. If no template is found, then the fallback is to use =view.tmpl=. Each skin on the path is searched for in turn. For example, if you have set the skin path to =local,pattern= then =view.local.tmpl= will be searched for first, then =view.pattern.tmpl= and finally =view.tmpl=.
+TWiki works by asking for a template for a particular function - for example, 'view'. The detail of how templates are searched for is described in SkinTemplates, but in summary, the templates directory is searched for a file called <code>view.</code><i>skin</i><code>.tmpl</code>, where _skin_ is the name of the skin e.g. =pattern=. If no template is found, then the fallback is to use =view.tmpl=. Each skin on the path is searched for in turn. For example, if you have set the skin path to =local,pattern= then =view.local.tmpl= will be searched for first, then =view.pattern.tmpl= and finally =view.tmpl=.
 
 The basic skin is defined by a =SKIN= setting: