Browse Prior Art Database

Communication Between Non-Presentation Manager Application And Officevision/2 Release 2

IP.com Disclosure Number: IPCOM000120749D
Original Publication Date: 1991-Jun-01
Included in the Prior Art Database: 2005-Apr-02
Document File: 1 page(s) / 53K

Publishing Venue

IBM

Related People

Chun, EG: AUTHOR [+2]

Abstract

This article describes a method of communication between a non-Presentation Manager* (non-PM) application and OfficeVision*/2 Release 2 (OV2R2) via an interface program. This interface program translates the OV2R2 requests to the non-PM application and offers an opportunity for the non-PM application to return data to OV2R2 to be displayed in a PM window.

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

Communication Between Non-Presentation Manager Application And Officevision/2
Release 2

      This article describes a method of communication between
a non-Presentation Manager* (non-PM) application and OfficeVision*/2
Release 2 (OV2R2) via an interface program. This interface program
translates the OV2R2 requests to the non-PM application and offers an
opportunity for the non-PM application to return data to OV2R2 to be
displayed in a PM window.

      In order to integrate an existing non-PM application with
OV2R2, a specific protocol is required to be followed in order for
this application to understand input data such as command, filenames,
etc.  from OV2R2.  Existing applications generally do not naturally
accept input in the same way as defined by OV2R2 and therefore, these
applications would require modification requiring a possibly
expensive re- release of their product that contained the special
code to interface with OV2R2.

      To avoid the problem of modifying existing applications in
order to work with OV2R2, an interface program can be written that
will communicate between OV2R2 and the existing application. This
interface program will translate the OV2R2 requests into input that
the external product can interpret and process.

      An interface program was written to communicate between
DisplayWrite* 5/2 (DW5/2) and OV2R2 in order to allow DW5/2 to be
used as an optional editor in the OV2R2 environment. When called
directly, DW5/2's inpu...