On 8/15/06, Sam Sutch <[EMAIL PROTECTED]> wrote: > Oh, really? Sortable lists, drag-drop facilities, DOM utilities, ajax > utilities (some of which rode in with prototype, albeit), autocomplete > etc... By calling it simply an effects library would almost be calling > Rico the same thing.
I think the idea is that there's a design difference between dojo, yui, google toolkit, mochikit, prototype, zimbra and scriptaculous, moofx (hrmph...library), PlotKit, etc. The former are used primarily to build behavior while the latter are used primarily to add flash or 'ajaxy goodness' to otherwise complete apps. Or at least that's how I associate them. I think that scriptaculous is starting to push the boundary with some of the new features but it retains most of its roots as the frosting layer on the webapp cake. I personally use MochiKit with the scriptaculous port (in the SVN repo) and dip into dojo when I know I'm going to have a use for the IO, history control, or events utilities it provides. And dojo is mucho javathonic but that only mildly diminishes its awesomeness. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
