Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Smalltalk/V PM Officevision/2 Error Manager

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

Publishing Venue

IBM

Related People

Chandler, PR: AUTHOR [+3]

Abstract

The only development option available to OfficeVision*/2 industry application developers up to this date has been to write applications using C language and Presentation Manager* with the OfficeVision/2 Application Programming Interfaces. The use of C language and retraining issues for a customer's programmers are extremely costly. There has been no method for managing OfficeVision/2 error processing that makes use of object-oriented concepts and code reuse and that is cost effective for the customer.

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

Smalltalk/V PM Officevision/2 Error Manager

      The only development option available to OfficeVision*/2
industry application developers up to this date has been to write
applications using C language and Presentation Manager* with the
OfficeVision/2 Application Programming Interfaces.  The use of C
language and retraining issues for a customer's programmers are
extremely costly.  There has been no method for managing
OfficeVision/2 error processing that makes use of object-oriented
concepts and code reuse and that is cost effective for the customer.

      Using Smalltalk/V** PM, an OfficeVision/2 Error Manager has
been created.  The Error Manager is being distributed to allow
developers the ability to manage OfficeVision/2 error processing.
The Error Manager has been labeled "OV2ErrorManager" in the
Smalltalk/V PM class hierarchy (see the figure).  Code has been
written in small programming code structures (called methods in
Smalltalk/V PM) which gives the OV2ErrorManager its characteristics.
It is the set of methods of the class OV2ErrorManager on which this
disclosure is focused.  An experienced Smalltalk/V PM programmer is
able to make use of these OV2ErrorManager methods within their
OfficeVision/2 desktop interactive applications.

      "Error Manager" will now be explained.  The Error Manager
handles the initialization of OV2ErrorDictionary within Smalltalk/V
PM and the displaying of errors that occur within OfficeVision/2 and
from the OfficeVision/2 classes.  For example, a user might select
the rename operation for an object.  If the name they type already
exists, the Error Manager will prompt them with a message box to
verify that they really want to write over the existing object name.
Another example would be when an application written in Smalltalk/V
PM tries to access the OfficeVision/2 Mail Service and an error
occurs.  The Error Manager would be able to display the actual return
code from the OfficeVision/2 call and correspond it to the error
message that should appear to the user as well as determine the types
of options the user would have available from the error (cancel,
continue, yes, no...).

      To manage all of this information, the Error Manager has an
OV2ErrorDictionary.  The dictionary is structured as follows:  code
(type, number of variables, string).  Code is the number assigned to
the error code.  In the second example above, the code would be the
return code issued by OfficeVision/2.  Type determines the type of
dialog to be displayed, such as whether it is a warning or an error
and also which options should be allowed (cancel, continue...).
Number of variables is the number of variables to pass to the error
string.  This is useful when the same error string could be used
multiple times by just passing a new parameter to it eac...