Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
TWiki Skins | ||||||||
Line: 13 to 13 | ||||||||
Topic text is not affected by the choice of skin, though a skin can be defined to use a CSS (Cascading Style Sheet), which can sometimes give a radically different appearance to the text. | ||||||||
Changed: | ||||||||
< < | Tip: TWiki:TWiki.TWikiSkinsSupplement on TWiki.org has supplemental documentation on TWiki Skins. | |||||||
> > | Relevant links on TWiki.org:
| |||||||
Changing the default TWiki skin | ||||||||
Line: 23 to 30 | ||||||||
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. | ||||||||
Changed: | ||||||||
< < | The TWikiTemplates files used for skins are located in the twiki/templates directory and are named according to the skin: <scriptname>.<skin>.tmpl . For example, the template used for pages generated by the view script with the print skin selected is view.print.tmpl (this is how the Printable control is implemented). Skin files may also be defined in TWiki topics - see TWikiTemplates for details. | |||||||
> > | The TWikiTemplates files 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 TWikiTemplates for details. | |||||||
To start creating a new skin, copy the default TWikiTemplates (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 . | ||||||||
Added: | ||||||||
> > | For your own TWiki skin you are encouraged to show a small 80x31 pixel logo at the bottom of your skin:
<a href="http://twiki.org/"><img src="%PUBURL%/%TWIKIWEB%/TWikiLogos/T-logo-80x15.gif" alt="This site is powered by the TWiki collaboration platform" width="80" height="15" title="This site is powered by the TWiki collaboration platform" border="0" /></a>
The standard TWiki skins show the logo in the %WEBCOPYRIGHT% variable. | |||||||
Note: Two skin names have reserved meanings; text skin, and skin names starting with rss have hard-coded meanings.
The following template files are used for TWiki screens, and are referenced in the TWiki core code. If a skin doesn't define its own version of a template file, then TWiki will fall back to the next skin in the skin path, or finally, to the default version of the template file. | ||||||||
Line: 51 to 64 | ||||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Line: 69 to 83 | ||||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
twiki.tmpl is a master template conventionally used by other templates, but not used directly by code. | ||||||||
Changed: | ||||||||
< < | Note: You are strongly recommended not to TMPL:INCLUDE the default templates, or templates from other skins, when you are defining your own skin. If you do, you run the risk that the included file might change and break your skin. | |||||||
> > |
Note: It is best to create these templates for your skin. If you TMPL:INCLUDE the default templates, or templates from other skins, when you are defining your own skin, you run the risk that the included file might change and break your skin.
Partial customisation, or adding in new features to an existing skinYou can use recusion in the TMPL:INCLUDE chain (eg twiki.classic.tmpl contains%TMPL:INCLUDE{"twiki"}% , the templating system will include the next twiki.SKIN in the skin path.
For example, to create a customisation of pattern skin, where you only want to remove the edit & WYSIWYG buttons from view page, you create only a view.yourlocal.tmpl :
%TMPL:INCLUDE{"view"}% %TMPL:DEF{"edit_topic_link"}%%TMPL:END% %TMPL:DEF{"edit_wysiwyg_link"}%%TMPL:END%and then set SKIN=yourlocal,pattern .
Because ClassicSkin and the default templates use the same Template definition names, you can over-ride the edit links in them (or any skin derived from them) using the same view.yourlocal.tmpl (just set SKIN=yourlocal,classic either in TWikiPreferences for globally, or a Web's Webname.WebPreferences for a particular web) | |||||||
Variables in Skins | ||||||||
Line: 104 to 134 | ||||||||
| ||||||||
Changed: | ||||||||
< < | The "Go" Box and Navigation Box | |||||||
> > | The "Go" Box and Navigation BoxThe default skins include a "Go" box, also called "Jump" box, to jump to a topic. | |||||||
Changed: | ||||||||
< < | The default %WEBTOPICLIST% includes a "Go" box, also called "Jump" box, to jump to a topic. The box also understands URLs, e.g. you can type http://www.google.com/ to jump to an external web site. The feature is handy if you build a skin that has a select box of frequently used links, like Intranet home, employee database, sales database and such. A little JavaScript gets into action on the onSelect method of the select tag to fill the selected URL into the "Go" box field, then submits the form. | |||||||
> > | The box also understands URLs, e.g. you can type http://www.google.com/ to jump to an external web site. The feature is handy if you build a skin that has a select box of frequently used links, like Intranet home, employee database, sales database and such. A little JavaScript gets into action on the onchange method of the select tag to fill the selected URL into the "Go" box field, then submits the form. | |||||||
Here is an example form that has a select box and the "Go" box for illustration purposes. You need to have JavaScript enabled for this to work: | ||||||||
Changed: | ||||||||
< < | ||||||||
> > |
| |||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
Deleted: | ||||||||
< < | Bare bones header for demo only | |||||||
Changed: | ||||||||
< < | Welcome | Register | Changes | Topics | Index | Search | Go | |||||||
> > | ||||||||
Changed: | ||||||||
< < | Using Cascading Style Sheets | |||||||
> > | Note: Redirect to a URL only works if it is enabled in configure (Miscellaneous, {AllowRedirectUrl} ). | |||||||
Changed: | ||||||||
< < | CSS is used by PatternSkin, the TWiki skin that is selected in new installations. See that skin topic for information how CSS is used. | |||||||
> > | Using Cascading Style Sheets | |||||||
Changed: | ||||||||
< < | CSS files are gererally attachments to the skin topic that are included in the the skin templates - in the case of PatternSkin in the template css.pattern.tmpl . | |||||||
> > | CSS files are gererally attachments to the skin topic that are included in the the skin templates - in the case of PatternSkin in the template styles.pattern.tmpl . | |||||||
Changed: | ||||||||
< < | Write in your main template: | |||||||
> > |
| |||||||
<style type='text/css' media='all'>@import url('%PUBURLPATH%/%TWIKIWEB%/MySkin/mystyle.css');</style> | ||||||||
Line: 186 to 224 | ||||||||
| ||||||||
Changed: | ||||||||
< < | You can also add a parameter to the URL, such as ?skin=catskin, bearskin . Example activation of PrintSkin that generates a printable page: | |||||||
> > | You can also add a parameter to the URL, such as ?skin=catskin,bearskin : | |||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
Changed: | ||||||||
< < | Setting SKIN (or the ?skin parameter in the URL) replaces the existing skin path setting. You can also extend the existing skin path as well, using covers. | |||||||
> > | Setting SKIN (or the ?skin parameter in the URL) replaces the existing skin path setting, for the current page only. You can also extend the existing skin path as well, using covers. | |||||||
| ||||||||
Changed: | ||||||||
< < | This pushes a different skin to the front of the skin search path (so for our example above, that final skin path will be ruskin, catskin, bearskin ). There is also an equivalent cover URL parameter. | |||||||
> > | This pushes a different skin to the front of the skin search path (so for our example above, that final skin path will be ruskin, catskin, bearskin ). There is also an equivalent cover URL parameter. The difference between setting SKIN vs. COVER is that if the chosen template is not found (e.g., for included templates), SKIN will fall back onto the next skin in line, or the default skin, if only one skin was present, while COVER will always fall back onto the current skin.
An example would be invoking the printable mode, which is achieved by applying ?cover=print . The view.print.tmpl simply invokes the viewprint template for the current skin which then can appropriately include all other used templates for the current skin. Where the printable mode be applied by using SKIN , all skins would have the same printable appearance. | |||||||
The full skin path is built up as follows: SKIN setting (or ?skin if it is set), then COVER setting is added, then ?cover . |