Al,
I had built Dojo into the Widget Engine already, in one of my own private implementations. (Beyond
that, I had also done several nifty AJAX stuff in Widget Engine, like making the next/prev buttons
AJAXed).
The exercise has told me that integrating any other javascript toolkit into the Widget Engine will
follow similar lines. I have the distinct feeling that the Widget Engine can be built to support
more than 1 toolkit!
Let me know which toolkit wins your votes, and I'll see if I can kick start the
integration exercise.
Jonathon
Al Byers wrote:
Where did we leave the javascript toolkit debate? Googling does not show any
clear cut direction.
I have a question about Prototype. Does it have layout widgets like Dojo
(eg. TabContainer, SplitContainer, AccordianContainer)? I don't see them in
the API for Prototype.
I think we need to make a choice primarily because it will be possible to
integrate a toolkit with the screen widget technology and it won't be
practical to do more than one. Right now I feel comfortable with Dojo as the
primary js toolkit, but that could be because I am not familiar with others.
I like the strong layout widgets that Dojo has and it seems to have
everything else, too, and I don't think that is a bad thing. I am able to do
a file upload within Dojo and get a JSON response and I think that is an
important consideration. I have read that Dojo is more Java, workman like
and Prototype is more Ruby and elegant. If that is the case, I would opt for
Dojo.
If nothing else, it might be useful to use this thread to measure where the
community's interest lies. So respond with nothing more than a vote if you
care to.
-Al
------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.485 / Virus Database: 269.13.14/999 - Release Date: 9/10/2007 5:43 PM
