> On Aug 22, 2006, at 2:15 PM, Alberto Valverde wrote: > Since TurboKid is under our control, we can certainly add things to > it as needed... But, we should also try to keep the big picture in > mind because TurboKid is just one of several template plugins > available. I'm not saying you should do anything differently at this > particular juncture. There has been some discussion on the python > templating list about having template loaders, which may be an > alternative route to doing load_template_string.
I've implemented this using "load_template_string" after getting inspiration from TurboCheetah which defines but doesn't implement it. I thought it was part of the intended protocol... however, I'm open to study this in more detail but I can't seem to find the python templating list you're talking about (any pointer appreciated). BTW, I've updated the ticket with new patches and it now fully supports markup and kid/markup combinations :) (Tests included). I've noticed that this ticket would probably close 1.0's #830 and, after considering the changes made, I feel it wouldn't be too risky to merge this functionality into 1.0 (after we settle on the template_string loading protocol and someone else tests those patches (hint, hint ;) )) I'm personally not using markup yet but I feel that leveraging the template engine plugin architecture in widgets is the way to go, not only from an asthetical viewpoint but from a consistency and flexibility viewpoint too (#830). Opinions welcomed :) Alberto --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
