Hi There! Kevin Dangoor wrote: > On Jun 26, 2006, at 10:13 PM, Jorge Vargas wrote: > > > I'm developing an app with a friend and he is going to do the front > > end, and has suggested to use dojo, I really don't have any > > arguments agains/pro it so please give me your comments.
I am the gui-guy :) I also want to note that this is the first time I'll use such a toolkit - I've done "normal" websites before, so its also the first time working on a real project in a web framework - and for web *app* you have to go a different direction, thats something I recognized soon.. > > I have done some research and dojo was one of the libs Kevin use > > for the "effective ajax" screencast, although I don't see a widget > > for it. > > I didn't actually use Dojo, I just referred to it. Where is this screencast? I've got to watch it! ;) PS: Kevin, your screencasts are everytime great and informative, thx for that :) > > Anyone has a widget for it? if not this sounds like a great idea > > for me to learn how to do those. > > Nope. Wrapping Dojo would be an interesting task, because it's > different from a typical "do one thing" JavaScript library. In fact, > it's not even typical as far as "just add this script tag", because > it has a whole module/package system. That makes it somewhat again a little bit pythonic, dont you think? :) I like the idea. > > From what I have read Dojo is more featurefull then mochikit, but > > mochikit is more pythonic (whatever that means) > > MochiKit is Pythonic in that it provides a bunch of functions that > we, Python programmers, like and take for granted. Dojo is, without a > doubt, more featureful. > > > Another thing I have read is that mochikit was written so it wont > > colide with other toolkits so it shouldn't be a problem to > > integrate them. > > Correct. In fact, MochiKit has specific support for integrating with > Dojo's packaging system. > > > what dojo has that mochikit can't provide? > > Here's the rub: Dojo has many features that MochiKit does not. It's > worth figuring out if those features are ones that are actually > useful to you. > > 1) animation - Dojo has it currently, MochiKit will have it in 1.4 > 2) dojo.storage - store effectively limitless amounts of data on the > client with little programming effort > 3) more Ajax features - different kinds of transports and whatnot The JSON part of Dojo is from MochiKit as I read in the source code ;) > 4) "comet" - long-lived connections that the server can use to push > data to the client... it's unclear that CherryPy can do the server > side of this right now > 5) widgets - something similar to TG's widgets, but implemented > completely client-side Important for me, are these Layout, Form, and General Widgets, the gui things, who gives you the possibility to do great user interfaces. They help you to put more app in "web app" ;) Because we need as much space on the users screen we can get for this specific project, its nice to use something like the TabContainer for examples or other ways to use the available space more effectively without scrolling. > 6) probably many other things that I haven't read about or that > aren't documented yet > > Dojo is, without a doubt, worthy of investigation and use. > Personally, I find MochiKit to be quite easy and pleasant to work > with... I like how MochiKit doesn't require fully qualified names and > implements $(). But, I wouldn't be surprised if I find use cases > where Dojo is a good fit along the way. Otherwise it makes your life easier with more prebuilt "widgets" than in MochiKit - who are, not to underestimate, are already tested from the dojo guys to work in as much browsers as possible. > Kevin It would be nice to hear some experience reports from people using it - or other suggestions of other toolkits with an "eye on the gui guy".. ;) Greetings Markus. A little trivia: I think I also heard Dojo will be the AJAX weapon of choice for the next Django versions..!? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
