> - Genshi templates > - Tosca widgets > - Sqlalchemy > - Routes
I like the flexibility of Routes, but I'm not 100% sold on it over CherryPy style object dispatch for ease of use in the simple case. I'm pretty sure we'll be able to default to one and make it easy to do the other too. > Where does MochiKit and/or Prototype fit into this picture? I really like MochiKit, but it is getting a bit long in the tooth. I would love to see mochikit push all the visual stuff out of the core, and use namespacing more aggressively, so that I can mix it in with other libraries more easily. We've been using ext.js on a recient project, and I think there's a lot of good design decisions in there. So that might be my personal choice for a prefered one-stop-shopping kind of javascript framework. At the same time I know Alberto is a fan of jquery. And I think that the choice of a "preferred" javascript library may best be left in the hands of ToscaWidgets. This is certianly one area (like template engine choice) where we want to allow for some flexibility because users will have different needs and different opinions abut the various engines out there. But for core widgets, and for the official documentaiton and tutorials, I think we do need to choose one javascript library. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
