{{{ #!rst ============================ Markup XML Template Language ============================ Markup provides a simple XML-based template language that is heavily inspired by Kid_, which in turn was inspired by a number of existing template languages, namely XSLT_, TAL_, and PHP_. .. _kid: http://kid-templating.org/ .. _python: http://www.python.org/ .. _xslt: http://www.w3.org/TR/xslt .. _tal: http://www.zope.org/Wikis/DevSite/Projects/ZPT/TAL .. _php: http://www.php.net/ This document describes the template language and will be most useful as reference to those developing Markup templates. Templates are XML files of some kind (such as XHTML) that include processing directives_ (elements or attributes identified by a separate namespace) that affect how the template is rendered, and template expressions_ that are dynamically substituted by variable data. .. contents:: Contents :depth: 3 .. sectnum:: ---------- Python API ---------- The Python code required for templating with Markup is generally based on the following pattern: * Attain a ``Template`` object from a string or file object containing the template XML source. This can either be done directly, or through a ``TemplateLoader`` instance. * Call the ``generate()`` method of the template, passing any data that should be made available to the template as keyword arguments. * Serialize the resulting stream using its ``render()`` method. For example:: from markup.template import Template tmpl = Template('

$title

') stream = tmpl.generate(title='Hello, world!') print stream.render('xhtml') That code would produce the following output::

Hello, world!

However, if you want includes_ to work, you should attain the template instance through a ``TemplateLoader``, and load the template from a file:: from markup.template import TemplateLoader loader = TemplateLoader([templates_dir]) tmpl = loader.load('test.html') stream = tmpl.generate(title='Hello, world!') print stream.render('xhtml') .. _`expressions`: -------------------- Template Expressions -------------------- Python_ expressions can be used in text and attribute values. An expression is substituted with the result of its evaluation against the template data. Expressions need to prefixed with a dollar sign (``$``) and usually enclosed in curly braces (``{…}``). If the expression starts with a letter and contains only letters and digits, the curly braces may be omitted. In all other cases, the braces are required so that the template processors knows where the expression ends:: >>> from markup.template import Context, Template >>> tmpl = Template('${items[0].capitalize()} item') >>> print tmpl.generate(Context(items=['first', 'second'])) First item Expressions support the full power of Python. In addition, it is possible to access items in a dictionary using “dotted notation” (i.e. as if they were attributes), and vice-versa (i.e. access attributes as if they were items in a dictionary):: >>> from markup.template import Context, Template >>> tmpl = Template('${dict.foo}') >>> print tmpl.generate(Context(dict={'foo': 'bar'})) bar .. _`directives`: ------------------- Template Directives ------------------- Directives are elements and/or attributes in the template that are identified by the namespace ``http://markup.edgewall.org/``. They can affect how the template is rendered in a number of ways: Markup provides directives for conditionals and looping, among others. To use directives in a template, the namespace should be declared, which is usually done on the root element:: ... In this example, the default namespace is set to the XHTML namespace, and the namespace for Markup directives is bound to the prefix “py”. All directives can be applied as attributes, and some can also be used as elements. The ``if`` directives for conditionals, for example, can be used in both ways:: ...

Bar

... This is basically equivalent to the following:: ...

Bar

... The rationale behind the second form is that directives do not always map naturally to elements in the template. In such cases, the ``py:strip`` directive can be used to strip off the unwanted element, or the directive can simply be used as an element. Available Directives ==================== .. _`py:attrs`: ``py:attrs`` ------------ This directive adds, modifies or removes attributes from the element:: Given ``foo={'class': 'collapse'}`` in the template context, this would produce:: Attributes with the value ``None`` are omitted, so given ``foo={'class': None}`` in the context for the same template this would produce:: This directive can only be used as an attribute. .. _`py:choose`: .. _`py:when`: .. _`py:otherwise`: ``py:choose`` / ``py:when`` / ``py:otherwise`` ---------------------------------------------- This set of directives provides advanced contional processing for rendering one of several alternatives. The first matching ``py:when`` branch is rendered, or, if no ``py:when`` branch matches, the ``py:otherwise`` branch is be rendered. If the ``py:choose`` directive is empty the nested ``py:when`` directives will be tested for truth::
0 1 2
This would produce the following output::
1
If the ``py:choose`` directive contains an expression the nested ``py:when`` directives will be tested for equality to the parent ``py:choose`` value::
0 1 2
This would produce the following output::
1
.. _`py:content`: ``py:content`` -------------- This directive replaces any nested content with the result of evaluating the expression:: Given ``bar='Bye'`` in the context data, this would produce:: This directive can only be used as an attribute. .. _`py:def`: .. _`macros`: ``py:def`` ---------- The ``py:def`` directive can be used to create macros, i.e. snippets of template code that have a name and optionally some parameters, and that can be inserted in other places::

Hello, ${name}!

${greeting('world')} ${greeting('everyone else')}
The above would be rendered to::

Hello, world!

Hello, everyone else!

If a macro doesn't require parameters, it can be defined as well as called without the parenthesis. For example::

Hello, world!

${greeting}
The above would be rendered to::

Hello, world!

This directive can also be used as an element::

Hello, ${name}!

.. _`py:for`: ``py:for`` ---------- The element is repeated for every item in an iterable:: Given ``items=[1, 2, 3]`` in the context data, this would produce:: This directive can also be used as an element:: .. _`py:if`: ``py:if`` ------------ The element is only rendered if the expression evaluates to a truth value::
${bar}
Given the data ``foo=True`` and ``bar='Hello'`` in the template context, this would produce::
Hello
This directive can also be used as an element::
${bar}
.. _`py:match`: .. _Match Templates: ``py:match`` ------------ This directive defines a *match template*: given an XPath expression, it replaces any element in the template that matches the expression with its own content. For example, the match template defined in the following template matches any element with the tag name “greeting”::
Hello ${select('@name')}
This would result in the following output::
Hello Dude
Inside the body of a ``py:match`` directive, the ``select(path)`` function is made available so that parts or all of the original element can be incorporated in the output of the match template. See [wiki:MarkupStream#UsingXPath] for more information about this function. This directive can also be used as an element::
Hello ${select('@name')}
.. _`py:replace`: ``py:replace`` -------------- This directive replaces the element itself with the result of evaluating the expression::
Hello
Given ``bar='Bye'`` in the context data, this would produce::
Bye
This directive can only be used as an attribute. .. _`py:strip`: ``py:strip`` ------------ This directive conditionally strips the top-level element from the output. When the value of the ``py:strip`` attribute evaluates to ``True``, the element is stripped from the output::
foo
This would be rendered as::
foo
As a shorthand, if the value of the ``py:strip`` attribute is empty, that has the same effect as using a truth value (i.e. the element is stripped). .. _`with`: ``py:with`` ----------- The ``py:with`` directive lets you assign expressions to variables, which can be used to make expressions inside the directive less verbose and more efficient. For example, if you need use the expression ``author.posts`` more than once, and that actually results in a database query, assigning the results to a variable using this directive would probably help. For example::
$x $y $z
Given ``x=42`` in the context data, this would produce::
42 7 52
This directive can also be used as an element::
$x $y $z
Note that if a variable of the same name already existed outside of the scope of the ``py:with`` directive, it will **not** be overwritten. Instead, it will have the same value it had prior to the ``py:with`` assignment. Effectively, this means that variables are immutable in Markup. .. _order: Processing Order ================ It is possible to attach multiple directives to a single element, although not all combinations make sense. When multiple directives are encountered, they are processed in the following order: #. `py:def`_ #. `py:match`_ #. `py:when`_ #. `py:otherwise`_ #. `py:for`_ #. `py:if`_ #. `py:choose`_ #. `py:with`_ #. `py:replace`_ #. `py:content`_ #. `py:attrs`_ #. `py:strip`_ .. _includes: -------- Includes -------- To reuse common snippets of template code, you can include other files using XInclude_. .. _xinclude: http://www.w3.org/TR/xinclude/ For this, you need to declare the XInclude namespace (commonly bound to the prefix “xi”) and use the ```` element where you want the external file to be pulled in:: ... Include paths are relative to the filename of the template currently being processed. So if the example above was in the file "``myapp/index.html``" (relative to the template search path), the XInclude processor would look for the included file at "``myapp/base.html``". You can also use Unix-style relative paths, for example "``../base.html``" to look in the parent directory. Any content included this way is inserted into the generated output instead of the ```` element. The included template sees the same context data. `Match templates`_ and `macros`_ in the included template are also available to the including template after the point it was included. By default, an error will be raised if an included file is not found. If that's not what you want, you can specify fallback content that should be used if the include fails. For example, to to make the include above fail silently, you'd write: See the XInclude_ for more about fallback content. Note though that Markup currently only supports a small subset of XInclude. Incudes in Markup are fully dynamic: Just like normal attributes, the `href` attribute accepts expressions_, and directives_ can be used on the ```` element just as on any other element, meaning you can do things like conditional includes:: .. _comments: -------- Comments -------- Normal XML/HTML comment syntax can be used in templates:: However, such comments get passed through the processing pipeline and are by default included in the final output. If that's not desired, prefix the comment text with an exclamation mark:: Note that it does not matter whether there's whitespace before or after the exclamation mark, so the above could also be written as follows:: }}} ---- See also: MarkupGuide, MarkupRecipes