On Jan 25, 2007, at 10:17 PM, iain duncan wrote: > > On Thu, 2007-25-01 at 21:54 -0500, Kevin Dangoor wrote: >> On Jan 25, 2007, at 6:55 AM, Jorge Godoy wrote: >> >>> My main concern is with the stability of what we called stable >>> code :-) And >>> the introduction of toscawidgets, genshi by default, sqlalchemy, >>> etc. are not >>> a minor change IMVHO. >> >> The move to Genshi is actually pretty easy, typically. (It may even >> be somewhat automatable, thanks to XML). >> >> Genshi's error handling, speed, text templates, extra tags, etc. make >> it a win that's worth pushing to sooner than later. SQLAlchemy's a >> big win as well, but it's a much more involved transition. > > Actually I don't think this is quite that cut and dry. For me, the > ability to use arbitrary python within kid is *extremely useful*. I > don't always use my templates within a full TG app, and for > prototyping > or splitting up labour and testing in a small operation, it's a real > time saver. > > I realize Genshi plans to implement that feature, but they aren't > there > yet.
True. Keep in mind that I wasn't talking about eliminating Kid support in TG 1.1. I was talking about making Genshi the preferred template choice... those who need to stick with Kid could indeed do so. By the way, for app composition to work really nicely, Genshi's variable includes and more powerful matching are a big win. Kevin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
