Browse Prior Art Database

View Editor

IP.com Disclosure Number: IPCOM000111284D
Original Publication Date: 1994-Feb-01
Included in the Prior Art Database: 2005-Mar-26
Document File: 6 page(s) / 181K

Publishing Venue

IBM

Related People

Beisiegel, M: AUTHOR [+9]

Abstract

The view editor is a tool by means of which visualization information of a complex object structure can be altered directly. The view editor is incorporated into the IBM ScreenView product and allows an applications programmer to directly alter the views on a GenOVHa (Generic Object and View Handler) application rather than editing and then recompiling the User Interface Definition (UID) of the GenOVHa application.

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

View Editor

      The view editor is a tool by means of which visualization
information of a complex object structure can be altered directly.
The view editor is incorporated into the IBM ScreenView product and
allows an applications programmer to directly alter the views on a
GenOVHa (Generic Object and View Handler) application rather than
editing and then recompiling the User Interface Definition (UID) of
the GenOVHa application.

      The GenOVHa utilities within ScreenView allow two types of
relations between object classes to be defined:

o   A "consist-of" structure in which a single object class includes
    one or more further object classes.  This structure is
    particularly important when navigating through views of the
    object classes presented on a display device.

o   A "Relation" structure in which one object class has,
    independently of the "consist-of" structure, a relationship with
    one or more other object classes.

Within the GenOVHa utilities, two types of object classes are
defined.

o   A container object is an object class which can contain further
    child object classes in the form of a "consist-of" structure.  It
    has at least one defined view, i.e., at least one way in which it
    may be presented to the end user.

o   A data object contains only data; it cannot have any child object
    classes.

      Fig. 1 illustrates the concepts of container objects and data
objects by means of a class structure.  Object class A is a container
object and includes the child object classes B and D. B is also a
container class and includes the child object classes C and E. Object
classes D and E are both data objects and consequently have no child
classes.  Also illustrated in Fig. 1 are "relations" between object
classes B and D and between the object classes C and E.

      From the object structure depicted in Fig. 1, one may create
the view on the object class A as shown in Fig. 2A.  It should be
noted at this point that a view may incorporate several instances of
the same object class although this is not so in Fig. 2A.  Using the
view editor, further different views of the same object class may be
created.  Fig. 2B shows, for example, a partial view on object class
A which comprises only instances of the object classes B and D and a
pictorial representation of the relation between them.  One may also
create a view on the object class B as shown in Fig. 2C.

      The view editor provides facilities which allow the
applications programmer to directly manipulate views by:

o   Creating new views.

o   Deleting old views which are no longer required.

o   Altering the settings of the views, for example, changing the
    background of the view, declaring a particular view to be a
    default view or adjusting the layouting information supplied with
    the view.

      Within the view editor, the object classes are presented on a
displa...