Browse Prior Art Database

Dynamic Template Replacement Capability in Officevision/2

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

Publishing Venue

IBM

Related People

Bell, LK: AUTHOR [+3]

Abstract

This article describes a method for an OfficeVision*/2 (OV/2) user to dynamically replace a template from the New Icons Folder or the New Modified Template dialog box. Currently, users must first delete the user-modified template they wish to replace and then re-register the template from "scratch". This results in extra steps for the user who wishes to replace a currently existing template in OV/2. In addition, lack of a replace capability does not allow users to take advantage of template information already saved by Registration for currently existing templates.

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

Dynamic Template Replacement Capability in Officevision/2

      This article describes a method for an OfficeVision*/2
(OV/2) user to dynamically replace a template from the New Icons
Folder or the New Modified Template dialog box. Currently, users must
first delete the user-modified template they wish to replace and then
re-register the template from "scratch".  This results in extra steps
for the user who wishes to replace a currently existing template in
OV/2.  In addition, lack of a replace capability does not allow users
to take advantage of template information already saved by
Registration for currently existing templates.

      OV/2 provides the New Icons Folder as the container for OV/2
templates.  Templates are the patterns used to create OV/2 objects.
There are two basic kinds of templates: base class templates and
derived templates.

      Base class templates are registered with all class information
necessary to run an application.  If the base template is deleted,
the information needed to run the application is deleted and the
application can no longer be invoked by OV/2.  Class information
includes class name, application path, working directory, and
procedure entrypoint (if applicable) and icon information (icon dll
and icon ids) and application type.  Changes made to a base template
affect the behavior of ALL associated modified templates.

      Derived templates are templates that are derived from a base
class template.  They use the base template class information to
start.  If the base class is deleted, the derived template can no
longer be invoked by OV/2 Office. Template information includes
template data file name, template property file name and template
type.  Changes made to a modified template affect the behavior of
only that modified template.

      An OV/2 Office Organizer is a special list that exists in a
Presentation Manager* client window.  It uses OV/2 List Control code
for its different presentation styles, such as icons with text on
right, icons with text on top, icons with text on bottom and mini
icons with text on right.  OV/2 objects are represented by the items
in the organizer's list (icons or mini icons) and actions on the
organizer's objects are handled by special icon procedure code
(iproc).  Each object in the organizer can have special data
associated with it, such as its list position, organizer position and
instance data.

      Each object in New Icons Folder us...