Rails 0.10 Released The Office: US Edition Finally Makes It!
Feb 24

Ajax: A New Approach to Web Applications

Ajax, HTML, JavaScript, Tech, UI / UX Add comments

There has been a lot of talk regarding the amazing new UIs that we can build with XmlHttpRequest, and the like ( a la Google Maps, TadaList, etc ).

Jesse James Garrett has given this set of technology a new name, and talks about it in Ajax: A New Approach to Web Applications.

I am extremely excited about the technology, but can’t agree more with Jason Fried when he calls for some caution.

As with all ‘new ways of doint it’, we need to make sure that we don’t confuse the users. One of the sad truths of UI work, is that you often have to keep your UI in a state that users are used too, even if the purist in you thinks they know a better way.

So, its time for us to get creative, but end up with an interface that is as usable, as much as it blows away the customers! :)

10 Responses to “Ajax: A New Approach to Web Applications”

  1. Howard M. Lewis Ship Says:

    I’m looking forward to people wrapping Ajax behavior inside Tapestry components. I was explaining to Ben that Tapestry’s engine service abstraction provides a way for script in the browser to communicate with logic in the server … without having to configure a new servlet (it piggy backs on the existing Tapestry servlet mapping).

  2. Howard M. Lewis Ship Says:

    I’m looking forward to people wrapping Ajax behavior inside Tapestry components. I was explaining to Ben that Tapestry’s engine service abstraction provides a way for script in the browser to communicate with logic in the server … without having to configure a new servlet (it piggy backs on the existing Tapestry servlet mapping).

  3. James Strachan Says:

    Agreed; I’ve wanted to develop for some time an ‘ActiveTable’ component for Tapestry using ActiveMQ’s Streamlets…

    http://activemq.codehaus.org/Streamlets

    to be able to easily provide a real time view of tabular information (such as a customers orders, emails, workflow queues etc).

    BTW Tapestry rocks :)

  4. James Strachan Says:

    Agreed; I’ve wanted to develop for some time an ‘ActiveTable’ component for Tapestry using ActiveMQ’s Streamlets…

    http://activemq.codehaus.org/Streamlets

    to be able to easily provide a real time view of tabular information (such as a customers orders, emails, workflow queues etc).

    BTW Tapestry rocks :)

  5. Michal Says:

    I am just wondering if java applets will be ever rediscovered.

    I’ve been doing things in the way which resembles “Ajax way” using applets years ago.
    With applets such things are easier to do as we can use mutiple threads and do many things in parallel and implement variouous inteligent caching or “read ahead of time” strategies on the client side.
    Saying nothing that component model (swing) for building user interface is light-years ahead comparing to what exists in any of modern web frameworks: it is easier to use, test and complex user friendly guis can be developed order of magnitude faster (this means cheaper!).

    Michal

  6. Michal Says:

    I am just wondering if java applets will be ever rediscovered.

    I’ve been doing things in the way which resembles “Ajax way” using applets years ago.
    With applets such things are easier to do as we can use mutiple threads and do many things in parallel and implement variouous inteligent caching or “read ahead of time” strategies on the client side.
    Saying nothing that component model (swing) for building user interface is light-years ahead comparing to what exists in any of modern web frameworks: it is easier to use, test and complex user friendly guis can be developed order of magnitude faster (this means cheaper!).

    Michal

  7. Michael Slattery Says:

    I had to make my own blog about ajax problems to stop the madness:
    http://jroller.com/comments/MikeSlattery/Weblog/ajax_is_a_mistake

    Btw, I agree with the last poster. If you’ve gone insane and think Ajax will solve your problems, you would probably be better off using an applet.

  8. Michael Slattery Says:

    I had to make my own blog about ajax problems to stop the madness:
    http://jroller.com/comments/MikeSlattery/Weblog/ajax_is_a_mistake

    Btw, I agree with the last poster. If you’ve gone insane and think Ajax will solve your problems, you would probably be better off using an applet.

  9. James Says:

    I agree, writing apps in plain AJAX is madness, its the modern equivalent to writing assembly language. You need different versions for different platforms.
    Of course tools will emerge to compile/generate a real programming language such as Java into executable code, which for AJAX is Javascript & HTML.

  10. James Says:

    I agree, writing apps in plain AJAX is madness, its the modern equivalent to writing assembly language. You need different versions for different platforms.
    Of course tools will emerge to compile/generate a real programming language such as Java into executable code, which for AJAX is Javascript & HTML.

Leave a Reply

Spam is a pain, I am sorry to have to do this to you, but can you answer the question below?

Q: Type in the word 'cricket'