Browse Prior Art Database

Flexible Interface, Teams, for Program Development Environments

IP.com Disclosure Number: IPCOM000108131D
Original Publication Date: 1992-Apr-01
Included in the Prior Art Database: 2005-Mar-22
Document File: 2 page(s) / 90K

Publishing Venue

IBM

Related People

Lunzer, AE: AUTHOR

Abstract

The concept of this disclosure is to give the user of a development environment control over grouping, organizing and connecting of windowed tools, thereby combining the benefits of a modular tool set with those of automatic display and organization of information related to the same task. A program development environment provides a user interface for developing, manipulating and examining programs; the interface can be thought of as a set of tools. In environments currently available, the inflexibility of the tools provided can be a great frustration to the user.

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

Flexible Interface, Teams, for Program Development Environments

       The concept of this disclosure is to give the user of a
development environment control over grouping, organizing and
connecting of windowed tools, thereby combining the benefits of a
modular tool set with those of automatic display and organization of
information related to the same task.  A program development
environment provides a user interface for developing, manipulating
and examining programs;  the interface can be thought of as a set of
tools.  In environments currently available, the inflexibility of the
tools provided can be a great frustration to the user.  This
solution, which has been developed in the domain of Object-Oriented
Programming on a window-based operating system, proposes providing
tools in the form of simple, specialized units that a user can
collect easily into cooperating "teams" suited to each task and to
the user's personal preferences.  Characteristics of the Teams
proposal are detailed below.
Tools that can take part in teams

      The development environment includes definitions for a number
of specialized kinds of tool unit, each suited to the display and
manipulation of a different aspect of program data.
Creation of a new team

      A new team is created when the user asks to start a new task.
The team should initially contain only the tool (or tools) considered
indispensable for this kind of task.  This behavior is preferable to
creating a standard collection of tools (e.g., the four panes created
in a Smalltalk browser) since some of them might not be required on
this particular occasion, and their creation wastes time and screen
space.
Adding to a team

      For any existing tool the user can choose to attach another
tool as a "dependent", to show related information. This dependent is
made a member of the same team as the parent.  The dependent can be
an instance of any type of tool able to use the information provided
by the parent, and may, in turn, act as parent to other tools.  Any
number o...