>This isn't to say that I'd be against using AJAX to post database
changes and update the
>list, but it's not clear to me how the added complexity would improve
the user interface. 

The additional complexity isn't that hard to deal with. I whipped
together a POC app at
http://w3.techsoftwareinc.com/midrange/ajax/Default.aspx that shows a
simple data entry screen like Wilt was looking for that uses ajax to
post the data back to the server and get additional fields. 

In this app the data is just echoed back to the client with two
additions. First, the description is manufactured from the item number,
and second, if you specify a non-numeric item number the server "hangs"
for 5 seconds to emulate a complex operation. You'll see you can
actually continue to enter items while the server is "busy" with the
non-numeric item. If you're fast you can even get a couple of numeric
items added to the list before the non-numeric one comes back.

As for the complexity, look at the html code. Adding ajax added about 20
lines to the html, not a big price to pay, imho.

Oh, if you leave quantity empty, or non-numeric you'll mess it up.
Sorry, this is a POC app, I'm not spending the time to fix it.

-Walden 


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2021 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.