>> If so, this would mean that template engines would have to provide >> special code for Pylons/TG2, which defeats the idea of having a >> standardized plugin interface accross frameworks. >> > yes for pylons not yet true for tg2.
Well, it's not much different from buffet, we just provide render_whatever functions which are called to return a rendered string via some template engine or other. And these render functions are gennerally less than a half dozen lines of code, so if TG doesn't provide one it's easy enough to write your own. Ultimately the trouble with buffet is that it requires all template engines to fit the same API. This ends up restricting Mako, genshi and other template engines that provide non-standard features. The other issue is the setup and configuration of various template engines which isn't always well supported via buffet. Another problem that people came across is what if you want to have genshi configured two different ways in the same application (one for returning html, another for returning xml, and a third which just hands back the genshi stream without rendering it down to a string). --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
