Friday, August 4th, 2006

Ajax Design Methodology: A Guide

Category: Design, Prototype

Adam Howitt has put together an 8-page PDF on Ajax design.

In the guide which you can download from the link below I’ll cover the process I have developed in the course of implementing two AJAX applications as a developer for Duo Consulting in Chicago. This approach has made it easier for me to work with the design team, produce estimates for this type of project and communicate what is involved each step of the way to the project managers for scheduling purposes.

He begins by taking a UI sketch and marks all “discreet sections”. Each section becomes its own JS file. From there, you decide on each interaction in each section, and create a Javascript function for it, later consolidating repeated functions into reusable objects.

You also need to consider the nature of remoting, and the guide distinguishes between four styles – essentially a 2×2 quadrant. One dimension is Uniqueness, i.e. whether the call is cacheable. The other dimension concerns the destination of the call – will it be some HTML rendered directly on a UI element, or some metadata that’s interpreted by the Javascript event handler. The document shows how to use the Prototype library to achieve all these combinations.

Duo is hiring right now, looking for ColdFusion developers to work in Chicago.

Posted by Michael Mahemoff at 3:51 am
5 Comments

+++--
3.6 rating from 22 votes

5 Comments »

Comments feed TrackBack URI

What…? Is it in fashion to talk about Ajax without showing samples?
What the hell is Ajax anyway? Every click, results in complete loads/reloads, as regular old-style web-programming…

Self apointed expert…huh?

Comment by Ned B — August 4, 2006

Interesting Finds: August 4, 2006

Trackback by Jason Haley — August 4, 2006

Ned B,

He provides several live examples of his work; while he doesn’t appear to be an ajax visionary, it is apparent that he has sufficient experience to provide some “words of wisdom.”

My only problem with his methodology is the example app has a very linear use case (ie user clicks a, load results in b, user clicks b, load results in c…). While many (if not most) complex ajax applications don’t work in this fashion, his technique of identifying disparate components can be applied for use in an object oriented environment when developing for nonlinear use case. A decent read!

Comment by Ed McManus — August 5, 2006

[…] Adam Howitt has put together an 8-page PDF on Ajax design. In the guide which you can download from the link below Ill cover the process I have developed in the course of implementing two AJAX applications as a developer for Duo Consulting in Chicago. This approach has made it easier for me to work with the design team, produce estimates for this type of project and communicate what is involved each step of the way to the project managers for scheduling purposes. He begins by taking a UI sketch and marks all discreet sections. Each section becomes its own JS file. From there, you decide on each interaction in each section, and create a Javascript function for it, later consolidating repeated functions into reusable objects. You also need to consider the nature of remoting,…. link: Ajax Design Methodology: A Guide posted: http://www.litefeeds.com […]

Pingback by varun krish on the web » Blog Archive » Ajax design methodology ((litefeeds)) — August 6, 2006

I think it is very fashionable

Comment by Kyle — July 27, 2007

Leave a comment

You must be logged in to post a comment.