Template Attribute Language

The following attributes are used, normally prefixed by "tal:":

; define

: creates local variables, valid in the element bearing the attribute (including contained elements)

; condition

: decides whether or not to render the tag (and all contained text)

; repeat

: creates a loop variable and repeats the tag iterating a sequence, e.g. for creating a selection list or a table

; content

: replaces the content of the tag

; replace

: replaces the tag (and therefore is not usable together with content or attributes)

; attributes

: replaces the given attributes (e. g. by using tal:attributes="name name; id name" the name and id attributes of an input field could be set to the value of the variable "name")

; omit-tag

: allows to omit the start and end tag and only render the content if the given expression is true.

; on-error

: if an error occurs, this attribute works like the content tag.

If a tag has more than one TAL attributes, they are evaluated in the above (fairly logical) order.

In cases when no tag is present which lends itself to take the attributes, special TAL tags can be used, making the "tal:" prefix optional. e.g.:

...

would cause the code inside the tal:if tags to be used whenever the context (whatever the application server defines the context to be, e.g. an object) contains variable "itemlist" with a true value, e.g. a list containing at least one element. The identifier following the colon is arbitrary; it simply needs to be there, and to be the same for the opening and closing tag.

The Macro Expansion Template Attribute Language (METAL) complements TAL, providing macros which allow the reuse of code across template files. Both were created for Zope but are used in other Python projects as well.

METAL complements TAL with the ability to reuse code. It allows the developer to define and use macros, which in turn may have slots; when using a macro, variational content can be specified for a slot.

When generating XML documents, the XML namespace must be specified

(xmlns:metal="http://xml.zope.org/namespaces/metal").

The following attributes are recognised, normally requiring a „metal:“ prefix:

; define-macro

: creates a macro

; define-slot

: creates a slot inside a macro

; use-macro

: uses a macro (normally given via a TALES path expression)

; fill-slot

: when using a macro, replaces the default content of the given slot

; extend-macro

: since Zope v3: extends a macro, comparable to subclassing, by redefining of slots

Normally, just one of those is used at a time.

In cases when no tag is present which lends itself to take the attributes, and in special cases when more than one METAL attribute is needed, special METAL tags can be used, making the „metal:“ prefix optional. E. g. (sketched with Roundup in mind):

...

...

TAL/TALES/METAL are used by the following projects:

• Zope (web application server)
• Roundup (issue tracker)

Besides the original Zope implementation, there are (not exhaustive):

• SimpleTAL
• OpenTAL
• ZPT, a standalone version of Zope Page Templates
• Chameleon, a fast reimplementation of Zope Page Templates

• SharpTAL

• tal, a native Go implementation of TAL, TALES and METAL

• [https://github.com/jhiver/template-tal template-tal], TAL Implementation for NodeJs
• jstal
• Distal
• DomTal
• ZPT-JS

• JPT: Java Page Templates
• JavaZPT
• ZPT-Java

• PETAL, the Perl Template Attribute Language
• Template-TAL

• Flower, a Raku implementation of TAL, with some Petal and PHPTAL extensions.

• PHPTAL
• Twital
• Biscuit
• zTAL

• XSLTal, transforming TAL via XSLT to XSLT

• TALCL: A library that implements the TAL template language for common lisp

• ATal – Not really a TAL implementation, but inspired on TAL concepts
• Thymeleaf - Not a TAL implementation, but a similar "natural template" language

{{Reflist}}

• [https://zope.readthedocs.io/en/latest/zopebook/AppendixC.html Zope Page Templates Reference] (Zope Book)

Category:Zope

Category:Template engines