RE: Re: Modify the IE Browser

> From: Eyers, Daniel
> 
> Joe....
> 
> (With all due respect)
> 
> Let's just say that if you failed to provide a robust, customizable
user
> interface in my organization, you would have a
> finding assigned to you in peer review.  You would not be able to
deploy
> your application until you either: 1) corrected
> your deficient design or 2) obtained a waiver.   Peter could get a
waiver
> for his kiosk application.  You probably
> couldn't get passed peer review until you made some changes to respect
the
> browser.

Honestly, Dan, I have no idea what you're talking about.  If I've got an
order entry system that requires them to enter header information
followed by lines of data, ending with some freight information, then
that's what they're going to do.  What is "robust"?  What is
"customizable"?  What do you consider required for this hypothetical
order entry system?

Or let's take an item maintenance application.  There are three panels
of data, one after the other.  The user may be able to switch between
panels, but until they either commit the transaction or end it, they
can't do anything else.  How is this not "robust" or "customizable"?


> Control of a flow of a business application does not equal "need" to
> control over the UI.  Facts not in evidence, your honor.

I don't understand this.  How about a concrete example?


> If the user wants to get out of order entry to go start A/R, let them
make
> the choice.  If it means they throw work
> away, so be it.  At least they had a choice. Choice is what makes a
good
> application great. Whether it's a game or a
> business application, choice sells.

They have that choice!  It's called the "exit" button, just like in any
5250 application.  I'm really confused here.

Joe