Thats a good lot of food for thought. Thanks very much! > I do hope that Markup and Kid can become one, since they are syntactically > > quite close
I took a quick look at Markup and liked it too. I particularly like its "make it fit in the xml tool chain" meme (I'm not a particular fan of xml but, hehho when in rome). ISTR something in the kid docs along the lines that support for comment processing prevented Kid from making full use of cElementTree accelerations. (In fact my copy of kid has a patch applied to get comments working at all but thats another story). I did very much like that Markup uses AST generation rather than generating .pyc's. I didn't realy understand why not having a dependency on ElementTree was a good thing. I mean, how hard can it be to patch cElementTree to give line numbers and handle comment processing in c ? I'll have a dig arround the firstclass stuff & trunk this weekend, with a view to seeing how deep the water is ;-) Cheers, Robin On 09/08/06, Kevin Dangoor <[EMAIL PROTECTED]> wrote: > > On Aug 9, 2006, at 1:01 AM, Robin Bryce wrote: > > > > > Thanks for the feedback. Got any thoughts on how you would like an > > implementation to look ? I've got time to work on this atm. > > I was just emailed with Elvelind about this a couple of days ago, > because he was thinking of something else along these lines. I'd love > to see some work done on this (on the trunk). > > One part is template paths (and this is the part that may change how > expose finds templates). Under ideal circumstances, if the user wants > to completely replace a template they should be able to do so, and > template paths would allow this. First Class is the codename for the > first major release after 1.0. It will allow applications to be > configured in PasteDeploy style. (There's an experiment checked in in > the firstclass branch that adds a tg-admin serve command that allows > easy composition of apps through PasteDeploy). > > The second part of this is being able to flexibly swap out the master > *or* to add additional match rules. The new Markup template language > provides a Kid-like syntax but provides this kind of flexibility in > match rule inheritance. I do hope that Markup and Kid can become one, > since they are syntactically quite close, but that's really for > others to decide. It would likely be possible to make a Kid->Markup > converter, given that Kid templates are standard XHTML. There are > some constructs that would be harder to convert automatically though. > > To start with, though, Markup does make it easy to substitute in a > new "master" or to add match rules. So, that increases layout > flexibility tremendously for apps that you are reusing. This > capability just needs to be exposed via Python and config file. (Note > that the current trunk does not include the PasteDeploy goodness... > this will need to be ported from firstclass, which is a bit old right > now.) > > Kevin > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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 -~----------~----~----~----~------~----~------~--~---
