Browse Prior Art Database

Run-Time Engine Architecture for Reusable Programmed Components

IP.com Disclosure Number: IPCOM000116250D
Original Publication Date: 1995-Aug-01
Included in the Prior Art Database: 2005-Mar-30
Document File: 2 page(s) / 54K

Publishing Venue

IBM

Related People

Chiu, H: AUTHOR [+2]

Abstract

Reusable Programmed Components are self contained units that have a predefined graphical user interface, and compiled programmer defined logic. These components can be combined to form applications. A run-time engine architecture, that enables these types of applications to operate, is described.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 59% of the total text.

Run-Time Engine Architecture for Reusable Programmed Components

      Reusable Programmed Components are self contained units that
have a predefined graphical user interface, and compiled programmer
defined logic.  These components can be combined to  form
applications.  A run-time engine architecture, that enables these
types of applications to operate, is described.

A run-time engine has been created that is able to:
  o  Initialize and terminate Reusable Programmed Component based
      applications
  o  Attach and detach components to its application
  o  Respond to program requests through a programming interface

The run-time engine consists of two state machines:
  o  A run-time state machine
  o  A component state machine

The run-time state machine is packaged as an executable file.  When
executed, it does the following:
  o  Initializes its state data
  o  Opens a Reusable Programmed Component with the same name as
itself
  o  Creates a message loop and dispatches messages until the message
      loop terminates
  o  Closes the Reusable Programmed Component that was previously
opened
  o  Cleans up its state data
  o  Exits

While inside the message loop, the run-time state machine responds to
requests through its programming interface.  It is responsible for:
  o  Opening and closing of sub-components
  o  Maintaining a component tree hierarchy
  o  Terminating the application
  o  Passing component related requests t...