Browse Prior Art Database

DATA DRIVER USER INTERFACE

IP.com Disclosure Number: IPCOM000026621D
Original Publication Date: 1992-Dec-31
Included in the Prior Art Database: 2004-Apr-06
Document File: 2 page(s) / 84K

Publishing Venue

Xerox Disclosure Journal

Abstract

One problem in the printing application field is the frequency of upgrades. Whenever printer programs are upgraded with new features or enhancements, requests to upgrade will be received. With evolving printing technology, the application software and user interface must be updated and released on a regular basis, which is an expensive process.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 61% of the total text.

Page 1 of 2

XEROX DISCLOSURE JOURNAL

DATA DRIVER USER INTERFACE Proposed Eddie J. Chen U.S. C1.364/000 Classification

Int. C1. G05b OO/OO

One problem in the printing application field is the frequency of upgrades. Whenever printer programs are upgraded with new features or enhancements, requests to upgrade will be received. With evolving printing technology, the application software and user interface must be updated and released on a regular basis, which is an expensive process.

The alternative is an intelligent but generic interface which describes the flexible and expandable functionalities in a script or data file. The software, which will become generic to different kinds of user interface requirements, reads in functionality from the script file, interprets it, and presents it to the end user. Thus immune from functionality additions or changes, only data files get affected. The advantage of this approach is that instead of releasing new software every time the requirement changes, a data file will be released. Presumably, the overhead will be much lower than that required for releasing new software. This concept is discussed in terms of printing systems here, but can be expanded to cover many generic user interface problems and other software development issues.

Examples of information to be stored are "Button labels", *Number of Choice Items', 'Text for Boolean or Choice Items", "Actions when user selects an item", "Category of and relationship between the objects",...