Browse Prior Art Database

Yoke Control for Window-to-Window Communication in a Graphical User Interface

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

Publishing Venue

IBM

Related People

Buttigieg, M: AUTHOR [+5]

Abstract

With the proliferation of software on the workstation, there will be an increasing need to provide ways for end users to coordinate the use of many different windows. From an end user perspective, window-to-window communication would allow an end user to choose an action within a window that is actually applied to another window. The Yoke Control is a user interface implementation of a control for graphical user interfaces that will enable end users to define actions that they want to be able to perform across windows and the keys that they want to be able to use to perform these actions.

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

Yoke Control for Window-to-Window Communication in a Graphical User
Interface

      With the proliferation of software on the workstation, there
will be an increasing need to provide ways for end users to
coordinate the use of many different windows.  From an end user
perspective, window-to-window communication would allow an end user
to choose an action within a window that is actually applied to
another window.  The Yoke Control is a user interface implementation
of a control for graphical user interfaces that will enable end users
to define actions that they want to be able to perform across windows
and the keys that they want to be able to use to perform these
actions.

      The Yoke Control could exist as an object on the desktop or as
a control within the Settings view of an object or window.  After the
Yoke Control is opened (Figure), the user needs to specify the
controlling window and the yoked (remote) window.  For example, the
controlling window would be the Note window and the yoked window
would be the Document window.  These windows can be identified
through drop-down lists or the user can drag and drop the title bar
icons into the Yoke Control window.  The first icon dropped into the
window would be the controlling window and the second would be the
yoked window.

      After identifying the windows to be yoked, the user selects a
key assignment, in the controlling window, which will be associated
with an action in the yoked window.  The user is also presented with
a list of actions (yoked assignment) on the yoked window that can be
chosen.  Both the key assignment and the associated yoked assignment
are presented to the user in a drop-down list in the Yoke Control
window.

      Information associated with pre-existing yoked assignments can
be presented to the user as a message in the information area.  This
information could further be communicated to the user via the
organization of choices within the Key Assignment drop-down list.
This drop-down list could be organized such that unassigned keys are
listed first and then preassigned keys are listed last.  Some
non-selectable heading should be included within the drop-down list
to convey this difference.

      For example: In the Note wi...