Randal L. Schwartz wrote:
> >>>>> "Harald" == Harald Joerg <[EMAIL PROTECTED]> writes:
>
> Harald> main.tt basically contains
>
> Harald> [% content = PROCESS $template.name %]
> Harald> [% PROCESS wrapper %]
>
> Harald> This solution can't be all bad because it brought me
> a "brilliant"
> Harald> by Randal L. Schwartz at that time :-)
>
> Yup, and I switched to that as my idiomatic top level. Works very
> nicely... the content can nudge its wrapper.
Now that there's a WRAPPER config option (as of v2.09a) , couldn't you
just do:
my $tt = Template->new({ WRAPPER => 'wrapper.tt' ...
It's my understanding that in this scenario the specified WRAPPERs are
PROCESSed after the requested template (i.e. from the inside out), so
any variables you create/modify are still in the stash and visible to
your wrapper (e.g. navigation). I'm using this model successfully in my
project (I think...)
Jason
_______________________________________________
templates mailing list
[email protected]
http://lists.template-toolkit.org/mailman/listinfo/templates
