Web UI design vs 5250 UI design

John P wrote:

>I am thinking of a simple Order Entry type scenario 
>where (in 5250 land) I might create the Order
>Header, then from subsequent screens write the details, 
>then ask for order confirmation and either commit or 
>rollback the transactions.  Since my mental model 
>works that way for 5250, I had seen no reason to use a
>different model for CGI.  

We're looking to "webify" our Synon applications, and are finding that all
the options that leave the 5250 data entry sequence as-is leave something to
be desired.  In other words, having to walk through 7 "screens" is just not
"GUI-ish."  It looks screen scraped, even though it might be RPG-CGI,
WebFaced or e-deployed.  The tech-savvy people we show this to all groan
when they see it.

More fashionable (word chosen with care) is the shopping cart, a la
amazon.com, or a single panel, with everything on it, a la innumerable web
registration pages.  Please remember that *I* do not think there's anything
wrong with the traditional multi-screen data entry.  The problem is that our
prospective customers now want sizzle with their steak; they want what's
fashionable.  And right now, stateless panels are The Thing.

Buck