Browse Prior Art Database

User Interface to Support Multiple Actions Within a Connection

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

Publishing Venue

IBM

Related People

Coskun, N: AUTHOR [+2]

Abstract

A link within a visual builder is specified by naming a source event on a source object, and then defining a target method on a target object. Creating a link is usually represented as drawing a line. Using competitive builders can be tedious because only a single action can be supported by each link In addition, the order in which the links are processed is unclear.

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

User Interface to Support Multiple Actions Within a Connection

A link within a visual builder is specified by naming a source event
on a source object, and then defining a target method on a target
object.  Creating a link is usually represented as drawing a line.
Using competitive builders can be tedious because only a single
action can be supported by each link  In addition, the order in which
the links are processed is unclear.

      This problem can be solved by changing the semantics of a link.
In our new model, a link is defined to be ALL methods that are
invoked as a result of event on a corresponding source.  If the user
desires, the user can draw a line as described in the above problem
text.  This disclosure lets the user specify links with our new model
as well.

      In this model, the user selects the source object and selects
the "link" action from a menu (or by some other mechanism).  Then, a
user can choose a source event, followed by a list of target methods
and corresponding target object.  This model is more natural for many
tasks.  For example, all event links for an "OK button pressed" event
can be defined at once, such as calculate a worksheet and then
destroy the window object.  With this user interface, there is no
ambiguity as to the order of the target methods that will be invoked,
and the user interface is more efficient.