Browse Prior Art Database

Object-oriented Officevision Design

IP.com Disclosure Number: IPCOM000121011D
Original Publication Date: 1991-Jul-01
Included in the Prior Art Database: 2005-Apr-03
Document File: 3 page(s) / 116K

Publishing Venue

IBM

Related People

Cavendish, C: AUTHOR [+2]

Abstract

The current version of OfficeVision*/2 (OV/2) was designed as an object-based application with an object-oriented user interface. Current technology advances in object-oriented programming environments make the development of a fully object-oriented version of OfficeVision a logical reality. Underlying this full OOPS (object-oriented programming system) version is an application framework design which ensures the reusability of classes and ease in integration of new applications into the system. Such a framework provided here alleviates current inconsistencies in interfaces, such as error handling, validation, control and communication, when integrating sets of classes built or designed by different developers.

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

Object-oriented Officevision Design

      The current version of OfficeVision*/2 (OV/2) was
designed as an object-based application with an object-oriented user
interface. Current technology advances in object-oriented programming
environments make the development of a fully object-oriented version
of OfficeVision a logical reality. Underlying this full OOPS
(object-oriented programming system) version is an application
framework design which ensures the reusability of classes and ease in
integration of new applications into the system. Such a framework
provided here alleviates current inconsistencies in interfaces, such
as error handling, validation, control and communication, when
integrating sets of classes built or designed by different
developers.

      Provided here is a design schema for a full OOPS version of
OfficeVision which greatly increases platform independence and allows
easy integration of new applications into the existing framework. It
overcomes the current difficulties in writing OV/2 applications for
multiple platforms and display systems (both windowed and
non-windowed) by separating the EUI (end user interface)-specific
behaviors of objects from the data itself. In addition, it
centralizes the methods needed to create a new office object,
enabling complete reuse by subclassing. It also defines a common
level of error and exception handling for the system.

      This design incorporates a model-view schema, which is a design
allowing complete separation of the viewing portion of an application
from its functionality. The model-view schema involves separating the
data-dependent part of an application (called the 'model') from its
visual representation (the 'view').

      The new design includes office objects in the class hierarchy -
the model objects - representing the applications and data, database
objects to interface with a relational database and view objects - a
view handler, and specific windows, icons and menus for each model
object.

      OfficeObject is the model superclass for the 'application'.
This class manages a list of dependents in a kind of parent-child
relationship. Dependents of a model can be both other models and
views of models. OfficeObject defines the messages that are sent to
the dependents to inform them of certain events:
- modelDispose parent - informs a view handler that its parent model
is closing so it can shut down gracefully.
- modelAddNew child   - the parent has received an open message and
the database has returned new instances....