Nice job.
I do have a couple of comments, however:

When trying to enter Phoenix, AZ in the from box, the autocomplete did
not work (or at least did not bring up anything to do with phoenix).
I happen to already know that sky harbor is PHX, and typing that worked
with the autocomplete, but I would suggest making cities return the
appropriate values.  Perhaps a full-text search would be appropriate?

Also, the performance of the autocomplete is really slow.  Whether it's
by design or just physical limitations, it's too slow, in my opinion,
especially since the autocomplete still pops up even after a value is
entered and then the user tabs out of the field.  For example, I typed
in PHX (which, by itself, should be acceptable), and then tabbed to the
next field.  THEN the autocomplete for the field I just typed PHX in
popped up.  This could be potentially quite confusing for users.

I like the dynamic loading of the results quite a bit.  In fact, that
REALLY gives the illusion of the app working much faster than services
like travelocity which buffer the results and then send them all at
once.
Those sliders on the left are pretty nifty, too.  That's a novel idea I
haven't seen before.  It's a hell of a lot more user-friendly than the
usual multi drop-down interface you normally see.  It's especially
handy with that dual-slider you have for the departure and arrival
times.

Another comment, though, is that the grid of search results needs to be
selectable.  People like to print out summaries of available flights to
show to someone else before making a final decision.  As it is right
now, it's not possible (or at least not very easy) to select the grid
and print it.  In fact, it doesn't appear that selection is possible at
all anywhere on that page.

I am a bit curious as to why the listings are draggable, too.  Is there
a reason for that?

Also, a question for you:
How does this site behave with downlevel browsers?
Does it gracefully scale back to less scripts and whatnot or does it
just not work in downlevel browsers?  If it does not work, is the user
notified of this in some way or redirected appropriately?

Those are just my thoughts after a few minutes of browsing.
I hope it's useful to you.

Brandon


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Ajax.NET Professional" group.

To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]

For more options, visit this group at http://groups.google.com/group/ajaxpro

The latest downloads of Ajax.NET Professional can be found at 
http://www.ajaxpro.info/

Don't forget to read my blog at http://weblogs.asp.net/mschwarz/
-~----------~----~----~----~------~----~------~--~---

Reply via email to