On Saturday 05 May 2007 23:20, asm wrote:
> > To override the standard template used in a controller (ie,
> > @expose("my.template.name")), pass "tg_template" in the dictionary you
> > return from your controller. So, if the template is stored in a
> > database, then you can just pass the name in the tg_template part of
> > the dictionary you return.
>
> This is cool - and I can see it will works well, say, switching
> between
> layout preferences for a particular key page. However it seems less
> useful for applying a selectable visual theme to the whole site.
>
> In my current project I have used the kid 'extend' mechanism to focus
> the site layout in a 'master.kid' but that would be harder to select,
> say,
> per user.
>
> Not desperate for this yet but it would be handy.I will only need to have a different template for a little part of the web page - the part which will display a page of the photo album. Each page will have its own template, but the rest of the web page will remains the same. I think to give to the widget the name of the template (stored in the db), and it will point to the correct kid file. -- Frédéric http://www.gbiloba.org
pgpllwPzjVE9I.pgp
Description: PGP signature
