summaryrefslogtreecommitdiff
path: root/docs/narr/templates.rst
blob: 4b74ab652c15fce45174b440917c8f562e5c1cde (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
Templates
=========

A *template* is a file on disk which can be used to render data
provided by a *view* in a form that is meaningful for a particular
*context*.

Default Templating With z3c.pt Page Templates
------------------------------------------------

Like Zope, ``repoze.bfg`` uses Zope Page Templates (ZPT) as its default
templating language. However, ``repoze.bfg`` uses a different
implementation of the ZPT specification: the `z3c.pt
<http://pypi.python.org/pypi/z3c.pt>`_ templating engine. This
templating engine complies with the `Zope Page Template
<http://wiki.zope.org/ZPT/FrontPage>`_ template specification. While
``z3c.pt`` doesn't implement the METAL specification (feature or
drawback, depending on your viewpoint,) it is significantly faster. And
faster, of course, is the zen of ``repoze.bfg``.

Given a template named ``foo.html`` in a directory in your application
named "templates", you can render the template in a view via::

  from repoze.bfg.template import render_template_to_response
  return render_template_to_response('templates/foo.html', foo=1, bar=2)

You can also wire up page templates via ZCML:

.. sourcecode:: xml

  <bfg:view
      for=".models.IMapping"
      view=".views.contents_view"
      name="contents.html"
      />

Both approaches load the template and keep it in memory between
requests. This means that modifications to the ZPT require a restart
before you can see the changes.

Templating with XSLT
------------------------

``repoze.bfg`` also supports XSLT as an optional templating language.
Like ZPT, an XSLT template is loaded once and re-used between requests.

Given a template ``foo.xsl`` in the templates directory, you can render
an XSLT as follows::

  from repoze.bfg.template import render_transform_to_response
  from lxml import etree
  node = etree.Element("root")  
  return render_transform_to_response('templates/foo.xsl', node)

As shown, the second argument to ``render_transform_to_response`` is
the element (and children) that you want as the top of the data for
the XSLT.

You can also pass XSLT parameters in as keyword arguments::

  from repoze.bfg.template import render_transform_to_response
  from lxml import etree
  node = etree.Element("root")
  value1 = "'app1'"
  return render_transform_to_response('templates/foo.xsl', node, param1=value1)

This would then assign 'app1' as the value of an ``<xsl:param
name="param1"/>`` parameter in the XSLT template.