Em Terça 23 Maio 2006 13:49, [EMAIL PROTECTED] escreveu: > > 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.
That's another approach. You loose some flexibility of using widgets, for example, but you also get your job done. If you don't need to guarantee that your project will work with browsers without JavaScript, then it is OK. If you do, then you are lost... :-) As for problems with Kid, I rarely have them and when I do, I generate the source file and read the generated Python code to see what Kid is understanding from my code (Kevin, here's another good opportunity for that mind-reading code... ;-)). As for redundancy, I believe they are in separate layers. For me it is much better to have custom templates and just use MochiKit to swapDOM or innerHTML some loadJSONDoc results then creating the whole structure in JavaScript (I have coded both things here to try them...). Both are complementary structures to me, one providing (X)HTML and the other doing the dynamic part on my website. If you stop to thing, a lot of things can be labeled "redundant" in TG, but they are intended as complementary instead. :-) Use what you believe is better for you. There are several other templating engines that you can use instead of Kid only, maybe they might suit you better. :-) -- Jorge Godoy <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
