Thanks a lot for the quick reply!

> > Note that in welcome.kid I don't want to have anything like <head>,
> > <body>, etc, etc, only the stuff that should be different on that
> > page, namely the <div id="content> container. This is the thing I
> > couldn't figure out from the docs.
>
> There are good reasons to include head and body sections in your page
> templates. This allows previewing them as standalone pages in a web
> browser. Also the title and meta info usually depend on the page.

Previewing the template as a standalone page is a good point, I
haven't considered that yet. Good to know. Actually, the title is
always the same for me and although the meta info like css and js may
vary but I solved it with turbogears.view.variable_providers. In this
way css and js files or sources are added programmatically from the
controllers.

> If you really always have the same head, then put this fixed head
> section in your master.kid template (i.e. without any py:match etc.)
> and you can leave it out in the page template.
>
> Header and footer section already exist in your master.kid template,
> just modify them according to your needs.
>
> Everything inside the body of your page template will automatically
> appear in a div section inside the body automatically, you don't need to
> put it in a separate div section in your page template.

Thanks, now it works, actually part of my problem was that when I
rewrote some of the templates I think cherrypy didn't restart and I
kept seeing old versions. Now I restart it manually sometimes and such
problems are gone :)

Cheers,
Daniel

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to