Application control module for common user access interface

• US 5,819,090 A
• Filed: 03/12/1997
• Issued: 10/06/1998
• Est. Priority Date: 03/04/1994
• Status: Expired due to Term

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: AST Research, Inc. (Samsung Electronics Co. Ltd.)
• Inventors: Lanier, Charles D., Wolf, Julie M., Helm, Bryan L.
• Primary Examiner(s): Oberley, Alvin
• Assistant Examiner(s): COURTENAY III, ST JOHN
• Application Number:
  US08/815,802
• Time in Patent Office: 573 Days
• Field of Search: 395/335, 395/682
• US Class Current: 719/320
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface

Abstract

An application management system for achieving a common user access (CUA) interface throughout multiple applications of a computer system is described. The system includes an operating environment having an application control module (ACM) that is run-time bound and executable by the applications. The ACM furnishes generalized procedural codes for each application. The application uses data structures to define the appearance and operation of the application to the ACM. The system also integrates the application program interfaces (API'"'"'s) of an operating environment graphic user interface (GUI) system and a database management system (DBMS) within the ACM. The invention reduces the programming required for applications and improves consistency in programming across multiple applications.

Claims

1. A method for providing an operating environment for multiple applications using a common user access interface in a computer system, said computer system comprising a system memory and mass storage, the method comprising the steps of:

storing graphic user interface (GUI) data structures in an application, wherein said GUI data structures comprise data for use by a control module of said operating environment for defining how data is to be presented and gathered and how user input events are to be gathered, said control module comprising code for handling user interface functions common to said multiple applications;

storing database data structures in said application, wherein said database data structures comprise data for use by said control module for defining how user data is to be read from and written to said mass storage;

storing control module data structures in said application, wherein said control module data structures comprise data for use by said control module for defining an appearance and operation of said application;

said application requesting loading of said control module into said system memory;

dynamically linking said control module to said application;

said control module initializing said control module data structures;

said control module displaying said application on a display screen of said computer system in accordance with said defined application appearance and;

said control module responding to user input events in accordance with said defined application operation.

2. The method of claim 1, said initialization step further comprising the steps of:

initializing said screen;

adding to said operating environment application defined user interface components defined by said control module data structures and said GUI data structures;

initializing user interface components, said components including graphic user interface components and said application defined user interface components;

reading data from a file stored in said mass storage into said database data structures;

copying said stored data from said database data structures to said GUI data structures; and

setting states of said GUI data structures to graphically represent said stored data on said screen.

3. The method of claim 1, said processing step comprising:

(a) indicating current user input location on said screen;

(b) accepting user input through the graphic user interface of said system;

(c) determining commands based on said user input;

(d) processing said commands; and

(e) repeating steps (a) through (d) until an error or a user directed exit occurs.

4. The method of claim 3, said determining step comprising the steps of:

receiving a return code generated by a GUI component in response to said user input; and

determining whether there is a command associated with said component return code.

5. The method of claim 3, said determining step comprising the steps of:

generating an event based on said user input; and

determining whether there is a command associated with said event.

6. The method of claim 5, wherein said generating step comprises defining and event associated with the selection of a graphic user interface component to be a command.