Browse Prior Art Database

Common Graphical User Interface for the Configuration of Distinct Application

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

Publishing Venue

IBM

Related People

McGuill III, AL: AUTHOR [+3]

Abstract

Disclosed is a method for providing a common graphical user interface for the configuration of various products or features of products. In today's increasingly complex software environment, every individual product presents its configuration information to the user in a unique way. This forces the user to learn many different and sometimes contradictory interfaces/methods for configuring features/products.

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

Common Graphical User Interface for the Configuration of Distinct
Application

      Disclosed is a method for providing a common graphical user
interface for the configuration of various products or features of
products.  In today's increasingly complex software environment,
every individual product presents its configuration information to
the user in a unique way.  This forces the user to learn many
different and sometimes contradictory interfaces/methods for
configuring features/products.

      Several distinct products, some ported from other platforms and
some newly developed, were being integrated into a cohesive family In
order to reduce the user's burden of having to understand several
separate methods of modifying configuration information, a common
user interface was developed.

      A graphical user interface based on CUA '91 with a notebook
control as the standard format was chosen as the common user
interface.  Each tab on the notebook control represents a
feature/product to be configured.  By placing appropriate controls on
the notebook pages, the information can be presented to the user in a
consistent fashion, removing the need to remember/understand
different methods of configuration.

      Past experience showed that a common user interface was not
sufficient.  A problem still existed in that the configuration tool
had to be "all knowing".  That is, the tool had to have prior
knowledge of each of the features/products it configures as well as
their respective parameters in order to build th...