Processing Officevision/2 Release 2 Opentemplate Request With Non-Integrated Application
Original Publication Date: 1991-Jun-01
Included in the Prior Art Database: 2005-Apr-02
This article describes a method for an integrated application to process the OPENTEMPLATE request from OfficeVision*/2 Release 2 (OV2R2) via special preparation processing performed by an interface program.
Processing Officevision/2 Release 2 Opentemplate Request
describes a method for an integrated
application to process the OPENTEMPLATE request from OfficeVision*/2
Release 2 (OV2R2) via special preparation processing performed by an
Files in the
OV2R2 New Icons Folder are considered object
templates and marked read-only for update protection. The user may
appear to edit these files but he may only save these changes by
using a new filename. Existing applications, commonly, do not have
special processing code to handle the editing of read-only files.
Since the files are read-only, they cannot be revised, and
applications that check for this error condition before allowing the
user to revise a file will not be able to process the OPENTEMPLATE
request from OV2R2.
To avoid the
problem of modifying existing applications to
enable them to process the OPENTEMPLATE request from OV2R2, special
preparation of the read only file can take place by an interface
program that is written to communicate between OV2R2 and the existing
application. This interface program translates the OV2R2 requests
into input that the integrated product can interpret and process.
After receiving the OPENTEMPLATE request from OV2R2, the interface
program can do special processing before transferring the request to
the application. The special processing includes making a copy of
the template file passed as input. This copy of the file is not
marked read-only and can be passed to the existing application to
edit as it does any other file. When the user is finished editing