Mark Ramm wrote: > We're thinking about dropping the buffet plugin from TG2. Pylons > is definitely in process of depricating it in 0.9.7. > > The reason behind this is mainly that buffet restricts the ability > of users to use the more advanced features of Mako and Genshi, and > requires a huge amount of code to do something really simple.
After talking with Ben about this a few weeks ago, I am definitely +1 on the idea. > So, my proposal is that we create a default render method that > takes an engine as an optional parameter. > > [snip, snip] > > The main benifit of this theory is that it would allow us to keep > the current expose style, and allow users to create non-default > renderers just by creating a new render function and setting it > up in the config. It would also allow users to have several > renderers installed -- but not imported or used in a particular > project. This seems simple, and sane. I heavily depend on the stacked expose style of TurboGears 2.0, and have found it to be a largely great way to get things done, and would be even happier if it supported extensions as a way to determine the requested content type and thus engine (GET /people/200.json vs GET /people/200.html). I am also very excited by the prospect of creatin simple callables that define custom render functions. -- Jonathan LaCour http://cleverdevil.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 -~----------~----~----~----~------~----~------~--~---
