RE: The Perpetual Myth of iSeries Obsolescence

I key with two hands, I should never have to touch the mouse, but to send
this e-mail now I have to hit alt, down, down look and see that outlook has
highlighted the send menu option and hit enter, or use the mouse to press
the button. 

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Trevor Perry
Sent: Thursday, May 04, 2006 1:00 PM
To: Midrange Systems Technical Discussion
Subject: Re: The Perpetual Myth of iSeries Obsolescence


You guys are all so funny! You are griping about BAD GUI designs. While they

are prevalent, they are not how it SHOULD be done.. All of you must be using

a POORly designed GUI. Or maybe a 'browser'UI - remember, the T in HTML 
stands for TEXT. There is no G in BROWSER.

A GUI should have RICH controls, and should be able to be navigated by the 
keyboard as WELL as the mouse - not either/or.

In the end, if a user's dominant function is mousing, then the mouse should 
be in the dominant hand, and the keyboard in the non-dominant hand. If the 
keyboard is the dominant function, then the mouse should be in the 
non-dominant hand. In this case, if you key with your right hand and mouse 
with your left, you don't have to switch. How amazing is it that thinking a 
little differently might stop the whining?? :-)

And then there are the companies who think Solitaire should be removed. Like

Evan said, that is a management issue. Solitaire is the best mouse training 
tool...



----- Original Message ----- 
From: <GKern@xxxxxxxxxxxxxxxx>
Subject: Re: The Perpetual Myth of iSeries Obsolescence


>> My main gripe about GUI designs is that they have you move from
>> keyboard... to mouse... to keyboard... to mouse...  wasted motion!
>
> "That's a peeve of mine too."
>
> Exactly - especially when I begin typing, and then look at the field (on a
> browser) and see nothing was input. Then I (again) have to reach for the
> mouse, move it to the field and click inside the field to enable the field
> as input capable. You'd think tabbing to the field would make it input
> capable. Clearly not head's down friendly. That's a 'feature' that's not
> modern by my definition.
>
>
> Regards, Jerry