![]() |
|
|
|
Buttons, Lists and Windows |
|
|
|
|
Robust character-based applications
should not be limited to text entry, but should include other
interface elements where appropriate. Consider the traditional
“action” prompt line found in many data entry programs. The same
function might be handled by incorporating an “action bar” – a
row of “command buttons” that perform the desired action when
“pressed”. This ties in with mouse input, and is easily used
from the keyboard either using cursor keys and the Enter key, or by
attaching function key shortcuts to each button. |
|
|
Go GUI |
|
|
|
|
|
The majority of new applications being
developed utilize some kind of Graphical User Interface. This is
typically a Windows interface, but could also be browser-based, or
another GUI environment like Mac or X. There are many advantages to
adopting a Graphical User Interface for a Multi-Value application.
The application will have an interface that is consistent with other
Windows applications, so it will be more familiar to new users. New
users will be able to learn the application more quickly because the
user interface operates in a consistent and expected manner, and
casual users may be able to use the application with little or no
training. And when the first impression is critical to making the
“sale”, the GUI look puts the Multi-Value application on equal
footing with the competition, at least when it comes to that
critical first look. AccuTerm’s GUI Development Environment provides the development tools and runtime environment to create GUIs for Multi-Value applications. AccuTerm GUI consists of a design tool which lets developers design GUI forms for their application using a friendly WYSIWYG designer. AccuTerm acts as the communication link between the host application and the GUI runtime engine (a component of AccuTerm). A library of Multi-Value BASIC subroutines act as the interface between the application and the GUI. Finally, the designer is integrated with a simple code generator, which generates skeleton BASIC code for the application’s user interface, with stub subroutines for all of the events that require handling. Adapting an existing Multi-Value application to use AccuTerm GUI is not as simple as the other modernization techniques discussed above, but the results are much more dramatic. In order to convert from character-based to true GUI, the user interface and business rules must be separated. Then the user interface layer can be replaced by new code which implements the GUI. The GUI environment is inherently event-driven, meaning that the application responds to events, not keystrokes. Typical events are click, validate, activate, etc.) And with a properly designed application, the order of events should not be constrained (the user should be allowed to click on any field and the application should accommodate). Multi-Value applications using AccuTerm GUI look and work exactly like other Windows applications. |
|
|
Summary |
|
|
More than a few Multi-Value applications
suffer from obsolete, ineffective and frustrating user interfaces.
In order to compete in the marketplace with applications developed
on other platforms, a Multi-Value application’s user interface may
need to be modernized. This includes visual enhancements so that the
applications appearance is consistent with typical Windows
applications. This is especially important when a quick glance at a
trade show is the only impression a prospect may get of the
application. Functional improvements in input processing are often
required, to ensure that the application behaves in a logical,
expected manner. Finally, incorporating a true GUI for the
application yields a Multi-Value application that looks and acts
exactly like other Windows applications. Any of these enhancements
can be effectively used to extend the lifetime of the Multi-Value
application. |
|
|
© 2004 AccuSoft Enterprises All rights reserved |
|