Changes between Version 1 and Version 2 of Dev/Technical/UsingMako

Timestamp:

03/24/11 17:46:51 (2 years ago)

Author:

mdamarac

Comment:

--

Dev/Technical/UsingMako

@@ -27 +27 @@
 }}}
 Here {{{None}}} defines the default value for {{{dark}}}.
+
+Another important thing is that only the arguments that were passed to the {{{render()}}} method get passed along to the included templates. Local variables or {{{pageargs}}} from some template {{{A.tpl}}} will not be available in all the templates that {{{A.tpl}}} includes.
 
 = 3. Whitespace between two expressions matters =
@@ -84 +86 @@
 = 7. Continuous Python blocks should be merged into one =
 Indico template [[https://espace.cern.ch/indico-soft/developers/wiki%20for%20Indico%20developers/Templating%20engine%20guide.aspx|documentation]] recommends to surround each Python code line with {{{<% %>}}}. Mako generates faster code when continuous {{{<% %>}}} blocks are merged into one. This is because after {{{<% %>}}} Python code execution Mako updates a dictionary where it keeps some information about the variables.
+
+= 8. Search path in inclusion mechanism =
+If the template {{{A.tpl}}} includes another template using {{{<%include file="B.tpl"/>}}}, then Mako searches for {{{B.tpl}}} in the same directory where {{{A.tpl}}} is stored. This becomes a problem, for example, when a template in the plugins folder tries to do,
+{{{
+<%include file="ConfModifCollaborationDefaultAdvancedTab.tpl"/>
+}}}
+and the file to be included is in the main templates directory. The problem can be solved by using full path:
+{{{
+<%include file="${TPLS}/ConfModifCollaborationDefaultAdvancedTab.tpl"/>
+}}}
+The variable {{{TPLS}}} is defined to be {{{Config.getInstance().getTPLDir()}}}.