Here's the initial version of my rewrite of Buffet, Pylons' template front end. This is only for those who care about the template internals. It won't actually work with Pylons until I write a pylons.templating patch, but here's a preview of the direction I'm proposing.
---------- Forwarded message ---------- From: Mike Orr <[EMAIL PROTECTED]> Date: Jun 3, 2007 6:38 AM Subject: ANN: Smorgasbord 0.1.0 is released To: [EMAIL PROTECTED] There's an initial implementation of Smorgasbord, my rewrite of the Buffet universal templating front end, at the Python Cheeseshop or http://sluggo.scrapping.cc/python/smorgasbord/ . Documentation is at http://sluggo.scrapping.cc/python/smorgasbord/Smorgasbord-current/README.html Plugins are included for Mako, Cheetah, Genshi, Kid, string.Template. These pass a minimal Nose test (a template with a placeholder) but do not recognize template options yet. There are plugins for Myghty and Breve but they don't work yet. (Expert needed.) A universal loader that recognizes path and URI notation is built-in, and is expandable for dotted notation if somebody twists my arm hard enough. It looks up templates in a directory path and an extension path (a list of extensions to be appended in turn if the template is not found). There is also an optional caching subclass that saves compiled templates in a dict. Feedback is welcome. What options are important for which engines? What does TurboGears need? Shall we go with URI syntax across the board for all engines in both Pylons and TG? Or Path syntax? Do we have to support existing Pylons/TG sites unchanged even if it means doing dotted notation and Python imports and obsolete options? Is it necessary to import Python templates (for Kid/Cheetah), or can we let the dict cache be the alternative speeder-upper? What about those dozens of default options Pylons has for Myghty? -- Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
