Saturday, April 29, 2006

Dojo

I've worked with AJAX a bit now without the use of any framework. It is a very powerful, but sometimes cumbersome solution. I've begun creating my own AJAX-enabled JSF components, as well as integrating AJAX into other web apps (PL/SQL, Python, etc.). I believe that I have finally stumbled upon a Javascript toolkit which will make life easier...it is called Dojo.

I haven't dug too deep into it yet, but I have downloaded the toolkit and read some material. I think that this open source toolkit may be exactly what AJAX needs. I'll keep you posted as I delve into the realm of Dojo...as time permits of course! Thanks to java.net for the excellent Dojo article!

4 comments:

  1. Anonymous6:09 PM

    Do you really believe that simplest AJAX appications must be so complicated?

    ReplyDelete
  2. Simple small apps are one thing, a full blown AJAX application is another. For instance, I can make an auto-complete text field or an AJAX form submission easily enough. However, if I need to duplicate similar code on 10 - 15 different web pages, it is easier to use a consistent pattern. It seems that Dojo would "hide" lots of tedious javascipt and make a large application easier to maintain.

    Let's face it, 6 months down the road do you rally want to traverse 100 lines of javascript to make a small modification? I'm not speaking from experience with Dojo, but it appears that it may make maintenance a bit easier.

    ReplyDelete
  3. Anonymous10:02 PM

    dojo makes the code a little bit shorter and solves the cross-browser capability issue, but it does not change the main point. Using the innerHtml directly to change the dom from the user code is a stone age. I would like to see the example where the half portion of the page with complicated table on it should be replaced as a result of the AJAX request. Let's see how short and easier to maintain the JavaScript code will be.

    ReplyDelete
  4. Anonymous10:05 PM

    dojo makes the code a little bit shorter and solves the cross-browser capability issue, but it does not change the main point. Using the innerHtml directly to change the dom from the user code is a stone age. I would like to see the example where the half portion of the page with complicated table on it should be replaced as a result of the AJAX request. Let's see how short and easier to maintain the JavaScript code will be.

    ReplyDelete

Please leave a comment...