[wp-hackers] AJAX and responsiveness

Tom Armitage tom.armitage at gmail.com
Thu Aug 17 15:21:10 GMT 2006

Or, you could do what's more obvious, and have a the animation
indicate that something's going on, and THEN update the UI to act as
confirmation. Which is the obvious way around.

On 17/08/06, Dave W <dabbaking at gmail.com> wrote:
> You can always Update the UI and have a little * Proccessing Requests Sign.
> Then it disappears when it's done. This way, it doesn't take forever to load
> and the user knows that something is still going on.
> On 8/17/06, Tom Armitage <tom.armitage at gmail.com> wrote:
> >
> > Updating UI immediately is, imho, not optimal - users in a hurry are
> > likely to click away, assuming things are complete. And it's not
> > enough to say "even though the visuals may have updated, the action
> > might not have happened, so wait a bit". If you want users to wait
> > until an action completes, wait for the visual element to update.
> >
> > This is a downside to Ajax, but imho it's a necessary one - you can't
> > have the complete desktop metaphor. At some point, you have to give in
> > to basic HTTP.
> >
> >
> --
> Dave W
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers

More information about the wp-hackers mailing list