|
Then you haven't seen one of my VB apps. (Sorry for interjecting... ) Michael Schutte "Christen, Duane J." <dchristen@mcleod To usa.com> "'Midrange Systems Technical Sent by: Discussion'" midrange-l-bounce <midrange-l@xxxxxxxxxxxx> s@xxxxxxxxxxxx cc Subject 05/04/2006 03:20 RE: The Perpetual Myth of iSeries PM Obsolescence Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.com> I don't disagree with a single word Scott, but I have yet to come across a halfway well written GUI application! I suppose that it could be keyboard-chair interface, but I doubt it. Duane Christen -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Scott Klement Sent: Wednesday, May 03, 2006 9:56 AM To: Midrange Systems Technical Discussion Subject: Re: The Perpetual Myth of iSeries Obsolescence > Without wanting to sound as if I am completely negative, I could not > disagree with you more. I am of course only looking at this from the > perspective of our industry, and more time is wasted playing with the g-d > forsaken mouse and clicking on buttons than anything else I have ever seen. Will all due respect, there's absolutely no reason that a GUI application can't be keyboard controlled. No GUI application that's even halfway well written requires a mouse. GUI can do every single thing that a green screen application can do. And it can do it in exactly the same way, if you want it to. Saying that GUIs are bad because of the mouse is like saying that 5250 is bad because of the need for a field+ and field- key. In both cases, you can design your applications so that they aren't required. But it ALSO adds additional capabilities (by the score!) that green screen cannot do. There are loads of productivity killers in green screen applications. For example, what happens if the cursor is positioned on a spot on the screen where no input fields exist? When the operator types, where do the keystrokes go? A GUI can prevent this type of mistake. When you type data into a field in a GUI you can have the program immediately validate the field and print information on the screen without stopping the operator who is keying. For example, after keying in an insurance group number, it can automatically print the name of that group on the screen, or report an error, without the user having to press enter or stopping their typing. This way, without pause, the typist can verify that he/she typed the correct group number. It ENHANCES productivity for data entry. I'm tired of the "green screen is better for heads down data entry" excuse that people keep using. You may have had some bad experiences with software where the user interface wasn't well-designed for heads down data entry, but that's certainly not because 5250 is "better." The advantage to 5250 applications is that you already know how to write them, and that you can write them extremely quickly. Their very lightweight, and they work very well over a slow network or communications link. But these advantages aren't good enough for your major, important applications. When users sit in front of a computer all day long every day, we should give them the most productive, easiest to use, least error prone system that we can. And there's no question that this will be a GUI interface. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. NOTICE: This electronic mail transmission may contain confidential information and is intended only for the person(s) named. Any use, copying or disclosure by any other person is strictly prohibited. If you have received this transmission in error, please notify the sender via e-mail. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.