Prototype, DOJO, self made - what Ajax framework should we use?
So far I have always recommended to write a simple self-made routine for the -driven sites if I think that the developers don’t have the time or skills to learn the . If, on the other hand, the developers are skilled and there’s time scheduled to learn a complete framework I have recommended prototype.js. The recommendation is based both on the usefulness prototype provides, but also on the very beautiful way it’s coded. (despite that extending standard classes must not necessarily be a good idea).
Today Per Henrik Lausten made comment regarding my “Using Ajax to manipulate Lotus Notes documents” post. In his post I found out that is working close with the DOJO toolkit. This is very interesting and I will certainly try out once again, it was some months ago last time.
I believe that a heavy, feature rich framework is only of use if all architects and developers knows what features there is and how to use them. I have seen many projects that are including several overlapping frameworks. In addition to this the developers have included there own tools.js, utils.js code with old, proved functions for opening windows, populating selection boxes etc. Such applications will be extremely hard to maintain in the future. Better to find one , learn it very well and stay with it.
UPDATE: Is Yahoo UI the way to go. It’s atleast what Interakt choosed and the post has some arguments aswell.
Stumble It!
I was looking at the Dojo vs Prototype issue just last night and am still not convinced which one I should lean towards. With IBM’s involvement with Dojo becomng official this week, the decision seems to be even more crititcal. Since you already seem to be very familiar with Prototype, it would be great to see a write up of the differences and similarities between the 2, especially from a Domino Developer’s point of view.
Sean—
Yes, I certainly intend to do some kind of comparison between these frameworks in the near future. Not next week though.
Joachim, thanks for “taking action” on my comments on using dojo as framework.
[...] I wrote an article on developerWorks regarding how Ajax can be used on a Lotus Domino platform that was published very close to the IBM/DOJO announcement last week. Per Henrik Lausten made a comment, which I replied to some days ago. {link}. He suggested more examples and information on how the DOJO can be used in conjunction with the domino server. [...]
Have you seen the “The JavaScript Library World Cup” article that compares dojo, Prototype, Mochikit, and Yahoo UI Library?
http://www.sitepoint.com/article/javascript-library
Oh yeah, maybe the best walk through I’ve seen on the libraries around. Thanks alot for that link!
[...] I have written about it before (here and here). The question about which javascript framework to use. In lack of defacto standards both inside and outside of my professional area I have used prototype.js and script.aculo.us heavily and starts to like them both, especially the prototype.js. [...]
Hello, how is the situation right now?
We have now the Prototype v. 1.5.1 and is very well documented , DOJO is unfortunately not. Is still Domino working more with DOJO?
Yes, they really are. DOJO will come in a ’sharp’ release this summer and rumours says it will be better documented.
Is there any information whch differentiates DOJO and PROTOTYPE?
I would like to know the major differences.