Browse Prior Art Database

Smalltalk/V Presentation Manager Officevision/2 Device Object Component

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

Publishing Venue

IBM

Related People

Chandler, PR: AUTHOR [+3]

Abstract

This article describes a method for easily creating OfficeVision*/2 device objects for desktop interactive applications, through the use of the Smalltalk/V** Presentation Manager* (PM) object-oriented programming tool. This method reduces the 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 52% of the total text.

Smalltalk/V Presentation Manager Officevision/2 Device Object Component

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

      The only development option available to developers integrating
applications with OfficeVision/2 up to now has been to write
applications using C language, Presentation Manager to access the
OfficeVision/2 Application Programming Interfaces (hereafter referred
to as APIs).  The use of C language and retraining cycle for
customer's programmers are extremely costly.  There has been no
method for creating an OfficeVision/2 device object that makes use of
object-oriented concepts and code reuse and that is cost effective.

      Using the Smalltalk/V PM, a Device Object Component has been
created.  The Device Object Component is being distributed to allow
developers the ability to create OfficeVision/2 device objects.  The
Device Object Component has been labeled "OV2DeviceObject" in the
Smalltalk/V PM class hierarchy (see Fig. 1).  Code has been written
in small programming code structures (called methods in Smalltalk/V
PM) which gives the OV2DeviceObject its characteristics.  It is the
set of methods of the class OV2DeviceObject for which this article is
focused.  An experienced Smalltalk/V PM programmer is able to make
use of these OV2DeviceObject methods to create their OfficeVision/2
desktop interactive applications.

      "Device object" will now be defined.  In OfficeVision/2 there
are three types of objects: data, device and container.  A device
object is represented to the user as an icon (a visual picture
representing the object) on the OfficeVision/2 desktop.  The icon for
a device object may represent a printer or a shredder or a facsimile
(fax machine), for examples.  The OfficeVision/2 device objects have
specific characteristics and may perform only certain types of
actions.  A list of these characteristics and actions is provided in
the next paragraph.

      The methods written specifically for OV2DeviceObject give
applications the ability to:
1.   allow a selected object from an OfficeVision/2 desktop to be
dropped on a device object.  The selected object being dropped will
provide the necessary information to the device so the device will
know what object was dropped on them and what to do with it.  For
example, a document icon may be dropped on the printer.  The document
will provide the necessary information to the printer, so that the
printer will be able to print it.
2.   allow the properties option on the OfficeVision/2 file pulldown
to present information on a selected device icon.

     ...