Browse Prior Art Database

Object-Oriented Methodname Specification in WMS Panel Tag Language

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

Publishing Venue

IBM

Related People

Malcolm, J: AUTHOR [+3]

Abstract

When defining action items, such as pushbuttons and menu bar selection items, and using an object-oriented programming paradigm, it is necessary to tie object-oriented methods to these action items so that at run-time, the predefined methods could be called without the need to write more than a generic menu procedure that takes these method names and routes them back to the object to handle.

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

Object-Oriented Methodname Specification in WMS Panel Tag Language

      When defining action items, such as pushbuttons and menu bar
selection items, and using an object-oriented programming paradigm,
it is necessary to tie object-oriented methods to these action items
so that at run-time, the predefined methods could be called without
the need to write more than a generic menu procedure that takes these
method names and routes them back to the object to handle.

      Since Panel Definition Files (PDFs) provide a tag language to
define the panels, a tag was added to the language to allow the
action's methodname to be tagged right into the panel definition,
then made available at runtime to the object when selected.  This
solution allows generic methods, such as Save, Apply and Cancel, to
be defined and passed back to the object to handle in a specific
manner, then allow the object to pass control back to the generic
method to do standard processing.  This significantly reduces the
menu-handling code that needs to be written.  This also gives the
panel designer a direct tie into the available runtime methods
without writing any code by using the runtime availability of this
information and a standard handling method.  The solution was to add
a METHODNAME= tag, which precompiles the tagged method name into the
binary runtime files.

      This  solution is generic enough to fit into any OO or non-OO
programming model, as the methodname need not be an object...