Jorge Godoy wrote:
Anyway, I'm curious about Deliverance. ;-)
Basically Deliverance works with a "theme" (which is just a file or URL)
and some rules. The rules define how the content (what your app
produces) is injected into the theme. A simple rule set would be:
<rules xmlns:xi="http://www.w3.org/2001/XInclude";
xmlns="http://www.plone.org/deliverance"; >
<xi:include href="standardrules.xml" />
<copy theme="//[EMAIL PROTECTED]'container']"
content="//[EMAIL PROTECTED]'portal-columns']" />
</rules>
The stuff in standardrules.xml just merges the <head>'s properly, and we
might get rid of that (as this is really HTML-oriented, so building in
HTML preconceptions is okay with me).
The <copy> rule says to take the div with id 'container' and put the
content in the element with id 'portal-columns' there. You can also do
things like:
<append theme="//[EMAIL PROTECTED]'sidenav']"
href="/myapp/sidenav.html" />
Which would take the content in sidenav.html and add it to the element.
Or you can take navigation out of the content page itself, for another
style of customization. All the work happens after the content is
rendered, so it's completely neutral of any templating technique. At
it's simplest you can also tell people to install an application, point
Deliverance (or some configuration key, like theme_url) to a page they
want to copy, and that's it. With that minimal technique you lose a
little something, but you also get something workable very fast that way.
--
Ian Bicking | [EMAIL PROTECTED] | http://blog.ianbicking.org
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears Trunk" 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-trunk?hl=en
-~----------~----~----~----~------~----~------~--~---
