how can I pass variable from child to the parent template?

[kenic...@gmail.com]

Hi all,
Is there a way to pass variable from child to the parent template?
I have a base.mako file that displays the site's navigation tree. I
also have a profile.mako file that inherits from base.mako. I want to
pass a "current_page" variable from profile.mako to base.mako so that
the current page can be highlighted in the navigation tree. Is this
possible?

[Michael Bayer]

using inheritance, the best way to pass variables is to send arguments
to the body() function as follows:

# inheriting template
<%inherit file="foo.html"/>
<%page args="x, y, z"/>

x y z are ${x} ${y} ${z}

# inherited template
<%
x = 1
y = 2
z = 3
%>
${next.body(x=x, y=y, z=z)}

this is another thing that I have failed to place a specific example
for in the docs.

hope this helps.

- mike

On Aug 9, 9:17 pm, "keniche...@gmail.com" <keniche...@gmail.com>
wrote:

[kenic...@gmail.com]

Michael,
this will pass x, y, z from the inherited template to the inheriting
template right? what about vice versa? I want the inheriting file to
tell the inherited template what x, y and z is.

- Kenny

[Michael Bayer]

the best way to do vice versa right now is to define defs in your
inheriting template:

# inheriting template
<%inherit file="foo.html"/>

<%def name="stuff()"><%
return (3, 4, 5)
%></%def>

# inherited tempalte
<%
(x, y, z) = self.stuff()
%>

*or*

# inherited tempalte
<%
(x, y, z) = next.stuff()
%>

[kenic...@gmail.com]

Thanks Michael, that works.

On Aug 10, 11:39 am, Michael Bayer <mike...@zzzcomputing.com> wrote:
> the best way to do vice versa right now is to define defs in your
> inheriting template:
>
> # inheriting template
> <%inherit file="foo.html"/>
>
> <%def name="stuff()"><%
> return (3, 4, 5)
> %></%def>
>
> # inherited tempalte
> <%
> (x, y, z) = self.stuff()
> %>
>
> *or*
>
> # inherited tempalte
> <%
> (x, y, z) = next.stuff()
> %>
>

[Anton V. Belyaev]

So simple! I invented much more tricky scheme :)

On 10 авг, 22:39, Michael Bayer <mike...@zzzcomputing.com> wrote:
> the best way to do vice versa right now is to define defs in your
> inheriting template:
>
> # inheriting template
> <%inherit file="foo.html"/>
>
> <%def name="stuff()"><%
> return (3, 4, 5)
> %></%def>
>
> # inherited tempalte
> <%
> (x, y, z) = self.stuff()
> %>
>
> *or*
>
> # inherited tempalte
> <%
> (x, y, z) = next.stuff()
> %>
>

[Pascal Schaedeli]

Excerpt: the best way to do vice versa right now [i.e. in 2007] is [...]: is there a better way today?

I can see how the def could be replaced by a block if appropriate in a given situation, but the only different is the "look". Is there a fundamentally newer/better concept that I could use (my objective is the same as in the question that initially started this thread)?

Thx. Pascal

[Jinghui Niu]

Hi Mike. It works as long as that variable is not used as a filename for an imported namespace. What if the variable you are passing from the child to the parent is the namespace file name? Then the namespace name definition will be hoisted to the beginning of that def and unaware of the returned value of next.stuff().