Notes on Moving from a Character Cell to GUI

Usability Techniques
Notes on Moving from a Character Cell to GUI

By Chauncey Wilson, edited by Robi Gunn
Reprinted from Usability Interface, Vol 4, No. 4, April 1998

I have run across cases (somewhat embarrassing) where the mainframe product was actually more efficient than the Windows version of the product (at least in version 1). For things like order-entry or general form input, some of the attributes of windowing applications can get in the way. If you are designing a windowing application for frequent form-based input/modification, you want really good keyboard capabilities, an absence of windows popping around, a minimum of keyboard mouse transitions, etc. The guidelines for Windows design don't really deal well with form design and high-frequency data input and modification. Here are usability guidelines that I’ve found helpful in making the transition from character cell to GUI applications.

1. Avoid mouse-keyboard transitions in the new GUI. A common mistake in moving from character cell to GUI is to use some controls that are "mouse primary" and some that are "keyboard primary" on the same dialog. This forces the user to switch between the keyboard and the mouse and waste time.

2. Optimize the design for keyboard use if you expect users to be typing in a lot of information. (For example, use combo boxes instead of a drop-down list so expert users can type in a code, rather than using the mouse or awkward keyboard procedures for searching through the list.)

3. Provide a clue about what fields are required.

4. Avoid window "flapping". Having multiple windows popping around can be painful for heavy-duty form input.

5. Consider whether the input is from a paper form and then design the input to match the form.

6. Consider whether you should use the Tab key or the Enter key for navigation. The Windows interface makes Tab a navigation key, but "green-screen" users are often used to the Enter key.