>>> To be honest, since mochikit isn't going to be the "blessed" framework >>> anymore I'm not sure if we should pursue finishing this to work with >>> tg2.
This is a hard question. I don't want TG2 to depend on a particularl javascript framework, or to become tied to one like tg1 was to mochikit. But I do think we need to document doing ajaxy things with TG2 in some way. Ideally we'd have documents for all kinds of stuff, but at least we should show something. And since Rum, Catwalk, and other still mythical things like the TortugaCMS are all using Dojo, I am tempted to document that first. It will be a kind of endorsement, but nothing as strong as TG1 was, which wasn't that strong either. Django studiously refrains from any endorsement of a JS framework and while I appreciate that I don't think a best of breed framework should necessarily be afraid to document how to use a particular JS library. Rails does it with Scriptaculous, TG1 did it with mochikit, and I personally think TG2 should consider it at some point, even if it's just so that most of the plugins and standard apps that you can download use the same JS library, rather than forcing confusing choices on people. --Mark Ramm --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
