An object-oriented approach for supporting both X and terminal interfaces

While the X Window System is clearly becoming the dominant user interface between display system, there is still a continuing need to support character cell terminal devices. For a user interface application which must support both, it is desirable to be able to use them to their fullest extent, as opposed to simply providing a character-based display within an X window. An object-oriented application framework is presented here which allows the full capabilities of each system to be used while minimizing and isolating the amount of device-dependent code. Every user interface application consists of two parts: the various components used to display information and accept user input, and the processing of the interaction between these components. Many user interfaces are built around a core set of components such as menus, text entry fields, and forms. For a given application, the interaction between these components is the same regardless of the display system in use. Our approach is to implement each component as an object, accessible via a single public interface. All of the code necesary to implement the component for the desired display system is completely encapsulated within the object. The application is then written as a collection of objects interacting in a device-independent manner with one another. If a display system provides additional capabilities, the application can be extended by adding objects (e.g. for image display in X). We are currently implementing StarView, the user interface to the HST science archive (STDADS) using this approach. StarView will be written in C++ and will use Vermont Views for the terminal interface and OSF/Motif for the X Window interface.