> Anyway, it should be possible to support one (standard) library well > and enable the use of others optionally by providing basic widgets.
In the end I think we *must* support multiple libraries, because people want them, and because they all provide different features. And I think that ultimately the decision about which one we support as "default" will be chosen by those who are putting together lots of new ToscaWidgets for twtools. ;) As Florent has suggested, working code is always the best argument. But I do find the arguments for dojo reasonably compelling. Particularly the dojo.require stuff: * http://redesign.dojotoolkit.org/jsdoc/dojo/HEAD/dojo.require I also like the fact that Dojo has lots of tests, and mochikit users will find dojo.deferred to be useful, since it too is based on Twisted. * http://redesign.dojotoolkit.org/jsdoc/dojo/HEAD/dojo.Deferred And of course Kevin Dangoor (the origonal founder of TurboGears) works for the Dojo people and has been doing screencasts of DoJo +TG2 already. So, we have some built-in marketing support on that front. http://www.sitepen.com/blog/2008/03/31/rich-ui-webapps-with-turbogears-2-and-dojo-screencast/ But none of that means anything without working code ;) --Mark Ramm --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
