4
Using template inheritance, two or more templates can organize themselves into an **inheritance chain**, where content and functions from all involved templates can be intermixed. The general paradigm of template inheritance is this: if a template `A` inherits from template `B`, then template `A` agrees to send the executional control to template `B` at runtime (`A` is called the **inheriting** template). Template `B`, the **inherited** template, then makes decisions as to what resources from `A` shall be executed.
6
In practice, it looks like this. Heres a hypothetical inheriting template, `index.html`:
9
<%inherit file="base.html"/>
11
<%def name="header()">
12
this is some header content
15
this is the body content.
17
And `base.html`, the inherited template:
34
<%def name="footer()">
38
Here is a breakdown of the execution:
40
* When `index.html` is rendered, control immediately passes to `base.html`.
41
* `base.html` then renders the top part of an HTML document, then calls the method `header()` off of a built in namespace called `self` (this namespace was first introduced in the Namespaces chapter in [namespaces_builtin_self](rel:namespaces_builtin_self)). Since `index.html` is the topmost template and also defines a def called `header()`, its this `header()` def that gets executed.
42
* Control comes back to `base.html`. Some more HTML is rendered.
43
* `base.html` executes `self.body()`. The `body()` function on all template-based namespaces refers to the main body of the template, therefore the main body of `index.html` is rendered.
44
* Control comes back to `base.html`. More HTML is rendered, then the `self.footer()` expression is invoked.
45
* The `footer` def is only defined in `base.html`, so being the topmost definition of `footer`, its the one that executes. If `index.html` also specified `footer`, then its version would **override** that of the base.
46
* `base.html` finishes up rendering its HTML and the template is complete, producing:
51
this is some header content
54
this is the body content.
62
...and that is template inheritance in a nutshell. The main idea is that the methods that you call upon `self` always correspond to the topmost definition of that method. Very much the way `self` works in a Python class, even though Mako is not actually using Python class inheritance to implement this functionality. (Mako doesn't take the "inheritance" metaphor too seriously; while useful to setup some commonly recognized semantics, a textual template is not very much like an object-oriented class construct in practice).
64
### Using the "next" namespace to produce content wrapping {@name=next}
66
Sometimes you have an inheritance chain that spans more than two templates. Or maybe you don't, but youd like to build your system such that extra inherited templates can be inserted in the middle of a chain where they would be smoothly integrated. If each template wants to define its layout just within its main body, you can't just call `self.body()` to get at the inheriting template's body, since that is only the topmost body. To get at the body of the *next* template, you call upon the namespace `next`, which is the namespace of the template **immediately following** the current template.
68
Lets change the line in `base.html` which calls upon `self.body()` to instead call upon `next.body()`:
85
<%def name="footer()">
89
Lets also add an intermediate template called `layout.html`, which inherits from `base.html`:
92
<%inherit file="base.html"/>
96
<div class="mainlayout">
100
<%def name="toolbar">
106
And finally change `index.html` to inherit from `layout.html` instead:
109
<%inherit file="layout.html"/>
111
## .. rest of template
113
In this setup, each call to `next.body()` will render the body of the next template in the inheritance chain (which can be written as `base.html -> layout.html -> index.html`). Control is still first passed to the bottommost template `base.html`, and `self` still references the topmost definition of any particular def.
115
The output we get would be:
120
this is some header content
129
<div class="mainlayout">
130
this is the body content.
139
So above, we have the `<html>`, `<body>` and `header`/`footer` layout of `base.html`, we have the `<ul>` and `mainlayout` section of `layout.html`, and the main body of `index.html` as well as its overridden `header` def. The `layout.html` template is inserted into the middle of the chain without `base.html` having to change anything. Without the `next` namespace, only the main body of `index.html` could be used; there would be no way to call `layout.html`'s body content.
141
### Using the "parent" namespace to augment defs {@name=parent}
143
Lets now look at the other inheritance-specific namespace, the opposite of `next` called `parent`. `parent` is the namespace of the template **immediately preceding** the current template. What is most useful about this namespace is the methods within it which can be accessed within overridden versions of those methods. This is not as hard as it sounds and is very much like using the `super` keyword in Python. Lets modify `index.html` to augment the list of selections provided by the `toolbar` function in `layout.html`:
146
<%inherit file="layout.html"/>
148
<%def name="header()">
149
this is some header content
152
<%def name="toolbar()">
153
## call the parent's toolbar first
159
this is the body content.
161
Above, we implemented a `toolbar()` function, which is meant to override the definition of `toolbar` within the inherited template `layout.html`. However, since we want the content from that of `layout.html` as well, we call it via the `parent` namespace whenever we want it's content, in this case before we add our own selections. So the output for the whole thing is now:
166
this is some header content
177
<div class="mainlayout">
178
this is the body content.
187
and you're now a template inheritance ninja !
added
removed
src/Mako-0.1.9/doc/build/content/inheritance.txt
