[EMAIL PROTECTED] wrote: > Recently, I have removed almost all of my usage of Kid templates. > All of the interesting things my controller does are exported over > JSON and then inserted with just a few MochiKit calls. The web > pages are basically just hard-to-maintain HTML files (XHTML plus the > painful Expat errors from Kid). > > Does anybody else see this in your own projects? I wonder if this > is a good thing or not. I like kid templates (except debugging > them), but it just can't compete with a static structure, data over > JSON, and updates with MochiKit.DOM. I'm starting to feel like Kid > is redundant for AJAX projects.
I had exactly the opposite experience, personally. I was finding myself duplicating a ton of my templates in MochiKit.DOM, which is much more difficult to use and maintain than kid templates. You basically standardized on MochiKit's DOM layer and JSON for all of your display. I standardized on using TurboGears widgets with kid templates and sending XHTML fragments over MochiKit.Async, rather than sending JSON. Personally, I find this solution a ton more elegant and way easier to maintain than having my markup generated client-side. Instead of having markup generated all over the place, every bit of markup in my applications is generated by a kid template. -- Jonathan LaCour http://cleverdevil.org --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
