W3TPL/tags: Difference between revisions

From Woozle Writes Code
Jump to navigation Jump to search
(alphabetical listing)
(the <trace> tag was apparently retired some time ago)
Line 26: Line 26:
* {{w3tpl/tag|load}}
* {{w3tpl/tag|load}}
* {{w3tpl/tag|save}}
* {{w3tpl/tag|save}}
* {{w3tpl/tag|trace}}
* {{w3tpl/tag|w3tpl}}
* {{w3tpl/tag|w3tpl}}
* {{w3tpl/tag|xploop}}
* {{w3tpl/tag|xploop}}
Line 45: Line 44:
* '''Debugging''':
* '''Debugging''':
** '''{{w3tpl/tag|dump}}''': show list of all variables (with values) and functions (with code)
** '''{{w3tpl/tag|dump}}''': show list of all variables (with values) and functions (with code)
** '''{{w3tpl/tag|trace}}
* '''In development''':
* '''In development''':
** '''{{w3tpl/tag|class}}'''
** '''{{w3tpl/tag|class}}'''

Revision as of 02:15, 8 June 2012

About

Although the main "meat" of W3TPL is the (as-yet-unfinished) parser for text within Template:XmltagTemplate:Xmltag tags, there are a number of other tags which replicate much of the same functionality and may be suitable for simpler tasks.

In order to get around the parser, most of these tags have ways of using internal data for their values rather than depending on the parser to get things in the right order. to be documented

One of the weaknesses of the MediaWiki parser is that it cannot deal with nested tags properly; the ending-tag of a tag-pair nested inside another tag-pair results in closure of the outer tag-pair as well, and any text past the internal closing-tag is displayed rather than being passed to the tag handler. W3TPL allows you to get around this limitation by defining functions which are parsed separately from the code-block in which they are executing.

Tags

alphabetical by function

Common Attributes