Re: [OT] JS/AJAX toolkits evaluation
Re: [OT] JS/AJAX toolkits evaluation
- Subject: Re: [OT] JS/AJAX toolkits evaluation
- From: Q <email@hidden>
- Date: Thu, 24 May 2007 00:02:42 +1000
On 23/05/2007, at 10:37 PM, Andrus Adamchik wrote:
Sorry for an OT question.
Briefly got out of the black hole of backend development, and into
the much-hyped world of dynamic web UI. Need to make a decision on
a JavaScript toolkit to do various dynamic widgets for a set of web
applications.
A short version of the question: which toolkit? why?
Of the toolkits I have looked at, YUI was the most likely candidate I
found to take home the trophy. It's cleanly implemented, very
modular, well documented and very well supported.
Prototype is very popular among the rails crowd, but it makes changes
to the object model that may break code from other sources. jQuery
has a strong rivalry with Prototype, and has some advantages (or at
least it used to) over prototype that makes for some very elegant code.
Dojo I found to be bloated, slow and problematic with some cross
browser support.
Mochikit is small, fast, very well thought out, well documented, and
heavily influenced by python. It isn't as feature rich as some of the
alternatives however.
DWR I looked at, but never actually used.
For structured coding and debugging, GWT takes a completely different
approach, you write and debug your code in Java and it gets cross-
compiled into javascript. It's certainly worth looking at, but it's
more intended for apps like gmail where the entire application runs
in the browser and the application server just serves up the data.
Integration with WO is most easily done by using the Ajax.Framework
included with Project Wonder.
Tapestry integration I don't know about, I have never used it (I'm
waiting for HLS to stop rewriting it every new release)
A more long-winded version:
5-6 years ago there was WO and there was JSP/Struts (or EOF vs.
EJB, for another absurd comparison). For a person coming to the
market with no deep knowledge, it was easy to pick the later over
the former, if only because of marketing (or lack of thereof for
WO). So now I'd like to avoid picking "JSP of AJAX" so to speak.
So ... is there a "WO of AJAX" out there? What are the opinions on
the popular and less popular toolkits among the WO community? Dojo,
Google, YUI, anything else? Are they even as much different as WO
vs. JSP?
I am looking for an ability to do structured coding (as opposed to
traditional JS spaghetti), a set of reusable widgets, and ease of
integration with Java engines like WO or Tapestry (I know Tapestry
4.1 already bundles Dojo, still wanted to look at other options), ...
Appreciate the insights of the WO community.
Thanks
Andrus
---------------------------------------------
Andrus (aka Andrei) Adamchik
Apache Cayenne ORM: http://cayenne.apache.org/
Creator, VP Apache Software Foundation
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40gmail.com
This email sent to email@hidden
--
Seeya...Q
Quinton Dolan - email@hidden
Gold Coast, QLD, Australia
Ph: +61 419 729 806
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden