Browse Prior Art Database

Backward Compatibility to Native Presentation Manager from an Extended Presentation Manager Architecture

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

Publishing Venue

IBM

Related People

Morgan, SA: AUTHOR [+2]

Abstract

Programming to the OS/2* Presentation Manager* (PM) to create an application's graphical user interface often takes a large portion of the total effort required to develop the application. It therefore serves a development team well to make use of a user-interface development tool such as the Window Management System (WMS). A development tool as extensive as WMS provides a great deal of function, including:

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

Backward Compatibility to Native Presentation Manager from an Extended
Presentation Manager Architecture

      Programming to the OS/2* Presentation Manager* (PM) to create
an application's graphical user interface often takes a large portion
of the total effort required to develop the application.  It
therefore serves a development team well to make use of a
user-interface development tool such as the Window Management System
(WMS).  A development tool as extensive as WMS provides a great deal
of function, including:

o   Relational control definition in a panel definition file.

o   Dynamic panel layout at runtime, based on text length of the
    current language strings in use, and up to date with the current
    CUA guidelines.

o   Runtime panel management to provide such functions as panel
    scrolling, non-scrollable function key areas, font support, text
    drag-drop and view swapping.

o   Control extensions such as text wrapping, entry field validation,
    directly editable title bar text, and extended select and
    multi-column list boxes.

o   A non-operating-system specific messaging and API interface to
    allow portability between different platforms.

      Such a tool is wonderful for applications being developed from
scratch, because it relieves so much of the PM programming burden
from the application's development team.  However, for applications
written directly to native PM that have already been developed, or
partially developed, adapting to use this kind of tool would require
extensive rewriting of code.  There needs to be a way that allows
applications in this situation to use major portions of the
user-interface tool without having to rewrite the PM code they
already use.

      The solution to this problem is for the user-interface
development tool to provide levels of backward compatibility from its
extended PM architecture to native PM code.  This backward
compatibility would allow the application to migrate from PM to the
development tool without having to rewrite its PM code already
written.  Two different levels of backward compatibility can be made
available to the PM application:

1.  The first level of backward compatibility lets the application
    use the panel definition files and the runtime panel layout
    support only.  This would make the application only have to
    re-tag their panels from the standard PM dialog templates to the
    development tool's panel definition files and change what API it
    called to cause the panels to appear on the screen.

    For this minimal outlay the application can define the controls
   ...