Apologies if you get multiple copies; I don't know who's on which list. I wrote up my understanding of how pylons.templating, Buffet, and the major plugins behave, both to document it all in one place, and to describe the de facto interface that is emerging. I've also listed all the template options for all the existing plugins I could find.
http://docs.pythonweb.org/display/pylonscookbook/Template+plugins+%28for+developers%29 This should help those who want to use one of the template plugins, incorporate Buffet in a new project, or write a new plugin. It describes the apparent best practices as far as I understand them, and can be a starting point for discussion on how we want the future spec to evolve. I started out analyzing Buffet and pylons.templating equally, but quickly moved to pylons.templating because that's what I actually use, and I had too many unanswered questions about Buffet/TG/CherryPy behavior to analyze them properly. So I followed the Pylons code, informed by the Buffet plugin interface: http://docs.turbogears.org/1.0/TemplatePlugins and the source to Mako, TurboKid, TurboCheetah, and Genshi. Please let me know of any mistakes in the article. -- Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
