Browse Prior Art Database

Smalltalk/V PM Officevision/2 Registration Manager

IP.com Disclosure Number: IPCOM000121502D
Original Publication Date: 1991-Sep-01
Included in the Prior Art Database: 2005-Apr-03
Document File: 5 page(s) / 173K

Publishing Venue

IBM

Related People

Chandler, PR: AUTHOR [+3]

Abstract

This article describes a method for easily creating OfficeVision/2* registration services files for desktop interactive applications, through the use of the Smalltalk/V** PM object-oriented programming tool. This method reduces time and complexity involved in integrating with OfficeVision/2.

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

Smalltalk/V PM Officevision/2 Registration Manager

      This article describes a method for easily creating
OfficeVision/2* registration services files for desktop interactive
applications, through the use of the Smalltalk/V** PM object-oriented
programming tool.  This method reduces time and complexity involved
in integrating with OfficeVision/2.

      There has been no method for creating an OfficeVision/2
Registration Services (ORS) file for integrated applications,
interactively by prompting for the information, and that reduces the
possibility of errors and makes the process faster and that also
makes use of object- oriented concepts and code reuse which is cost
effective. Currently, to create an integrated application's ORS file,
the developer must type in all of the parameters into a data file.

      Using Smalltalk/V PM, a Registration Manager has been created.
The Registration Manager is being distributed to allow developers the
ability to create OfficeVision/2 Registration Services (ORS) files.
The Registration Manager has been labeled "RegistrationManager" in
the Smalltalk/V PM class hierarchy (see Fig. 1), and uses the prompt
screens in "OV2RegisterDialog" and "OV2RegisterMoreDialog", also in
the hierarchy.  Code has been written in small programming code
structures (called methods in Smalltalk/V PM) which gives the
Registration Manager its characteristics.  It is the set of methods
of the classes "RegistrationManager", "OV2RegisterDialog" and
"OV2RegisterMoreDialog" on which this invention disclosure is
focused.  An experienced Smalltalk/V PM programmer is able to make
use of the Registration Manager created by these methods to create
their OfficeVision/2 Registration Services (ORS) files, thus reducing
the possibility of errors in the ORS file and speeding the process of
creating the ORS file.

      "Registration Manager" will now be defined.  In OfficeVision/2,
an application must be registered before it can be shown as an icon
(visual picture representing the application) on the OfficeVision/2
desktop.  A data file with the extension of .ORS (meaning
OfficeVision/2 Registration Services) must be created with all of the
information the OfficeVision/2 product will need in order to run the
application, and to know how to present the application's icons and
how to interact with the application when mouse functions such as
drag, drop and double-clicking are performed.  (See Fig. 2.)

      There are currently over twenty parameters which must be set up
in the ORS file in order to register an application to
OfficeVision/2.  These twenty parameters ask for information such as
the class, template name, handler parameters, icon id numbers.  Not
only does a user have to know which of the twenty or more parameters
are required, but also there is a certain format and coding that each
of the parameters looks for.

      The Registration Manager simplifies the process by presenting
to the user a set of...