Browse Prior Art Database

Smalltalk/V Presentation Manager Officevision/2 Release 2 Developer's Toolkit

IP.com Disclosure Number: IPCOM000122267D
Original Publication Date: 1991-Nov-01
Included in the Prior Art Database: 2005-Apr-04
Document File: 4 page(s) / 164K

Publishing Venue

IBM

Related People

Chandler, PR: AUTHOR [+3]

Abstract

Disclosed is a Developer's Toolkit which consists of an object-oriented class hierarchy environment which OfficeVision*/2 industry application developers can use to model and develop OfficeVision/2 desktop interactive applications. The class hierarchy was implemented in Smalltalk/ V** PM, but any similar object-oriented language could use the same technique. The goal of the Developer's Toolkit is to allow developers to build OfficeVision/2 desktop interactive applications without having to know or understand the OfficeVision/2 Application Programming Interfaces (hereafter referred to as APIs).

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

Smalltalk/V Presentation Manager Officevision/2 Release 2 Developer's
Toolkit

      Disclosed is a Developer's Toolkit which consists of an
object-oriented class hierarchy environment which OfficeVision*/2
industry application developers can use to model and develop
OfficeVision/2 desktop interactive applications.  The class hierarchy
was implemented in Smalltalk/ V** PM, but any similar object-oriented
language could use the same technique.  The goal of the Developer's
Toolkit is to allow developers to build OfficeVision/2 desktop
interactive applications without having to know or understand the
OfficeVision/2 Application Programming Interfaces (hereafter referred
to as APIs).

      There are currently no available tools to reduce the complexity
of developing an OfficeVision/2 desktop interactive application.
Currently, the only development option available to these developers
is to write the application using C language and Presentation
Manager* to access the OfficeVision/2 APIs.  (OfficeVision/2 provides
a set of 'C' function calls, macros, commands, messages and data
types collectively referred to as APIs.) OfficeVision/2 has an
object-oriented appearance but was not written in an object-oriented
language.  Another problem is the conversion of customer's non-'C'
programmers to a new methodology; the problem is with the vast amount
of time required to retrain programmers and with requiring the use of
a low level language like 'C'.  Maintaining interactive 'C' programs
from release to release of OfficeVision/2 will be extremely costly
and time-consuming.

      The power of object-oriented programming comes from arranging
classes in a hierarchy.  Classes high in the hierarchy represent
general characteristics, while lower classes represent specific
characteristics.  There are pieces of code called methods which
define the functionality of each class.  In the Developer's Toolkit,
the classes provided by Smalltalk/V PM have been added to and
subclassed to allow for specific OfficeVision/2 behavior.  These
classes are listed on the next page, most of the ones added for the
Developer's Toolkit are prefixed with "OV2".

      A typical C application integrated with OfficeVision/2 might
require 5000 lines of code, but to integrate the same application
using the Developer's Toolkit may require only 50 lines of Smalltalk
V/PM code.  The code developed using the Developer's Toolkit is also
much simpler to debug because of the interactive debugger provided by
Smalltalk/V PM.

      The Developer's Toolkit hides the OfficeVision/2 complexity
from the developer.  Full desktop interaction becomes easy, meaning
that no API  calls must be made by the developer because Smalltalk/V
PM "wrappers" of code are provided around the APIs, and also that
integration code is being completely provided.  Changes to
OfficeVision/2 in each new release will be shielded from the
developers wh...