Browse Prior Art Database

Method for Changing OfficeVision/2 Properties in Applications Using Smalltalk/V PM OfficeVision/2 Release 2 Developer's Toolkit

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

Publishing Venue

IBM

Related People

Miller, PC: AUTHOR [+3]

Abstract

This article describes a method for allowing OfficeVision*/2 industry applications created using the Smalltalk/V** PM OfficeVision/2 Release 2 Developer's Toolkit, to reflect changes made to the office properties made in OfficeVision/2 immediately.

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

Method for Changing OfficeVision/2 Properties in Applications Using
Smalltalk/V PM OfficeVision/2 Release 2 Developer's Toolkit

      This article describes a method for allowing
OfficeVision*/2 industry applications created using the Smalltalk/V**
PM OfficeVision/2 Release 2 Developer's Toolkit, to reflect changes
made to the office properties made in OfficeVision/2 immediately.

      The only development option available to OfficeVision/2
developers up to this date has been to write applications using C
language, Presentation Manager to access the OfficeVision/2
Application Programming Interfaces.  The use of C language and
retraining issues for customer's programmers are extremely costly.
There has been no method for creating an OfficeVision/2 desktop
interactive application that makes use of object-oriented concepts
and code reuse and that is cost effective for the customer.  So there
has also not been an easy method for reflecting changes in the office
properties in the application.  The properties are:
1.  Accelerators - a boolean (true or false) which indicates if
accelerator keys should be shown on the pull down menus (Fig. 1).
2.  Error Beeps - a boolean (true or false) which indicates if the
application should beep when an error condition occurs (Fig. 2).
3.  Message Area - a boolean (true or false) which indicates if the
window for the application should display a dynamic information line
(referred to as a DIL) (Fig. 3).
4.  Open Run - a boolean (true or false) which indicates if an object
being opened should be run if it is an executable file (Fig. 2).
5.  Replace Prompt - a boolean (true or false) which indicates if a
prompt should be displayed to the user if an object is going to be
replaced by a new object (Fig. 2).

      These properties are maintained by OfficeVision/2 and can be
changed at any time by the end user.  If any of these properties are
changed, any open object should instantly reflect these changes.  For
example, if the DIL is currently displayed and the user changes the
Message Area flag to false, the DIL should instantly disappear from
any opened object.

      Methods of the classes OV2Object and OV2Window are being
distributed to allow developers the ability to create OfficeVision/2
desktop interactive applications that respond to changes in the
OfficeVision/2 properties.  Using Smalltalk/V PM, these methods have
been created.  Code has been written in small programming code
structures (called methods in Smalltalk/V PM) which give OV2Object
and OV2Window the ability to change properties.  It is this set of
methods on which this article is focused.  An experienced Smalltalk/V
PM programmer is able to make use of these methods from within their
OfficeVision/2 desktop interactive applications.

      When an OfficeVision/2 property changes, a Presentation Manager
(PM) message is broadcast to all opened applications.  Methods have
been written in Smalltalk/V PM to accept these...