US6023272A

US6023272A - Continuously accessible computer system interface

Info

Publication number: US6023272A
Application number: US09/021,556
Authority: US
Inventors: Mark A. Malamud; Renee Marceau; Joyce A. Grauman; Royce A. Levien; Daniel P. Oran; David A. Bolnick; David A. Barnes, Jr.; Russell Scott Johnson
Original assignee: Microsoft Corp
Current assignee: Microsoft Technology Licensing LLC
Priority date: 1993-12-13
Filing date: 1998-02-10
Publication date: 2000-02-08
Anticipated expiration: 2013-12-13
Also published as: US5825357A

Abstract

A system and method are described for presenting a continuously accessible computer system tool interface. The interface of the present invention comprises a separated applications section and system tray section. The applications section provides a portion of the graphic user interface for running applications programs. The tray section provides an alternative region of the graphic user interface for objects to surface their key features while occupying only a small portion of the display space. The tray section is supported by a Tray Object which provides a frame work for tray aware applications to dock.

Description

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 08/667,362 filed Jun. 21, 1996, now U.S. Pat. No. 5,825,357, which is a file wrapper continuation of U.S. Ser. No. 08/166,566 filed Dec. 13, 1993 (abandoned).

FIELD OF THE INVENTION

This invention relates to the field of user interfaces for computer systems, and more particularly to graphical user interfaces wherein a user selects from a collection of graphical representations displayed upon a video screen corresponding to actual computer resources.

BACKGROUND OF THE INVENTION

The United States has experienced an extraordinary expansion in the ownership and utilization of computers. Computers, once considered primarily the tools of scientists, can now be found in a substantial portion of the homes and businesses across the country. Though partial credit for the unprecedented growth in the utilization of computers is attributable to lower costs associated with manufacturing computers and related peripheral devices which has made such equipment affordable to a much larger segment of the public, the credit is equally, if not more, attributable to the enhanced versatility, ease in learning to use, and ease of using of computers which is provided by the operating systems and applications software running on the now affordable computers.

It is therefore a very important objective when designing an operating system, and more particularly a user interface for a computer system, to provide a high degree of user friendliness, which incorporates ease of learning and ease in using the computer system, as well as a high degree of versatility. Users appreciate a system which enables them to accomplish their computer related tasks with the least amount of obstacles and delays. A considerable number of the computer users/operators today base their like or dislike of a computer system upon the user interface and the user interface's time and effort saving features.

The Windows operating system and its series of menus and buttons has simplified the use of the computer system. The Windows operating system is unquestionably easier to learn than earlier operating systems. Even more importantly the Windows operating system enables a user to access a great number of computer resources from any given screen by selecting ones of the many menu items and control buttons.

In prior art operating systems, accessing files and computer resources requires traversing the directory tree structure. When a user wishes to gain access a particular file, or other computer resource, the user traces through the directory structure and opens up various directories and subdirectories before reaching the particular file or computer resource.

Though traversing the tree structure of a relatively non-complex file system in order to gain access to a desired resource does not present a very formidable task in itself, this task can be both time consuming and challenge the patience of a user when the directory tree must be repeatedly traversed in order to access resources located in different positions of the directory structure. This problem is multiplied when the separate resources are stored in divergent locations in a complex file directory structure. It is therefore desirable to operate a system wherein files and other computer resources are quickly and easily accessed, even when the files and resources are located in remote and divergent locations in the directory structure of the computer system data storage devices.

Another challenge facing computer system developers is to provide a flexible platform for accessing and executing computer resources in order to accommodate the unique needs of various users. Known user interfaces, referred to as command accelerators, provide a specific, pre-programmed set of direct access commands. However, these command accelerators lack flexibility. The programs which support these direct access commands cannot be altered or customized to meet the specific needs for a particular user or application. The prior art interfaces suffered from the inflexibility of a static set of commands. As a result, the prior art direct access command interfaces are either over-inclusive and provide unnecessarily large collections of computer resources, or they are too narrow and do not provide the desired direct access to a sufficient number of computer resources.

Padawer et al. U.S. Pat. No. 5,220,675, assigned to Microsoft Corporation of Redmond, Washington, discloses a computer system wherein additional menu items associated with computer programs are inserted on a menu and the programs represented by the menu items are executed when the menu items are selected by the user. A menu, however, is coupled to a specific application running on the computer system and that menu is not displayed unless the specific application responsible for the generation of that menu is surfaced. Furthermore, the modifiable menu in the Padawer et al. '675 patent extends to display the set of applications during the selection process and the menu is retracted when a selection is not being made by the user. Thus, for reasons related to the nature of the uses of a menu, the known alterable menu is not a persistent user interface mechanism. In other words, the menu's persistence is limited by the persistence of the application program that created the menu.

SUMMARY OF THE INVENTION

It is therefore an object of the present invention to enhance the ease with which a user of a computer accesses a modifiable set of computer resources.

It is another object of the present invention to enable the user to easily alter the modifiable set of computer resources.

It is a further object of the present invention to provide a flexible direct access command interface which supports a wide variety of uses for the computer system.

It is another related object of the present invention to provide a persistent user interface tool that minimizes interference with the portion of the video interface allocated for displaying images associated with application programs.

It is yet another object of the present invention to enable the user to control the execution of an extensible set of concurrently running programs by means of a computer resource accessed via a persistently available system tool.

It will also be apparent from the description of the preferred embodiment of the invention described below that a number of other objects concerning the goals for development of superior user interfaces including enhanced user friendliness, extensibility, and versatility are achieved as well by the present invention.

The above and other objects are achieved by an improved computer system which includes a central processing unit (CPU) and associated electronic memory for storing programs executed by the CPU. The computer system also includes a video interface coupled to the CPU for facilitating user access to the computer resources provided by the computer system. The video interface comprises an applications section for displaying images corresponding to signals transmitted by the CPU in accordance with the execution of application programs by the CPU. The video interface of the improved computer system includes a tray section. The tray section is a persistent and extensible graphic user interface facility. The tray section of the user interface provides both visual and operational direct access to an extensible, user modifiable, set of computer resources associated with the tray section and displayed within the tray section in the form of a set of representations.

A user modifies the set of computer resources associated with the tray section by means of a display set modifier. The display set modifier enables the user to transfer a computer resource associated with the applications section of the user interface to the tray section. The display set modifier enables the user to modify the set of computer resources associated with the tray section by a mouse controlled drag and drop operation on a window represented upon the video display interface or any other known manners for transferring the location of a computer resource displayed upon a video interface.

After a computer resource becomes associated with the tray section, the appearance of the computer resource may be altered, however, the window remains directly accessible to the user by accessing the portion of the tray occupied by the computer resource. The direct accessibility of the computer resource is unaffected by computer resource's location in the system directory structure in relation to the computer system's present point of access in the directory hierarchy.

The computer system of the present invention provides a versatile, extensible, user friendly command platform for enabling a wide variety of users to define their own set of directly accessible computer resources. The behavior of computer resources associated with the tray section is defined by the computer resource. The set of directly accessible computer resources associated with the tray section is adaptable to each user's particular needs.

BRIEF DESCRIPTION OF THE DRAWINGS

The appended claims set forth the features of the present invention with particularity. The invention, together with its objects and advantages, may be best understood from the following detailed description taken in conjunction with the accompanying drawings of which:

FIG. 1 is a schematic drawing of an exemplary computer system incorporating the present invention;

FIG. 2 is an illustrative depiction of the display for a computer system incorporating the present invention;

FIG. 3 is an illustrative depiction of the display for a computer system incorporating an alternative embodiment of the invention wherein the tray section of the screen comprises a palette; and

FIG. 4 is an illustrative depiction of the display when the tray section has been collapsed in order to enable a greater percentage of the total screen space of a video display interface to be occupied by the applications section.

FIG. 5 is a flow diagram summarizing the steps for re-defining the boundaries of the applications section due to a change in the display state of the tray section;

FIGS. 6a, 6b and 6c schematically depict the structure of the Tray Object;

FIG. 7 is a flow diagram summarizing the steps for docking an object to the tray section; and

FIG. 8 is a flow diagram summarizing the steps for undocking an object from the tray section.

DETAILED DESCRIPTION OF THE DRAWINGS

The computer system schematically illustrated in FIG. 1 comprises a central processing unit (CPU) 2 coupled by means of a bus 4 in a known manner to a random access memory 6. The CPU 2 is also coupled to a non-volatile secondary memory 7 for storing various system and applications routines and programs. The CPU 2 is coupled in known manner to a user interface 8 including a video display 9. The video display 9 may be any of a number of known display devices including, for example, monochrome and color cathode ray tubes and LCD displays. The user interface 8 also includes a keyboard 10 and mouse 11 to facilitate the submission of instructions to the CPU 2. Though not shown in FIG. 1, the computer system may also include a number of peripheral units as would be known to those skilled in the art. The computer system hardware depicted in FIG. 1 is intended merely to show a representative hardware configuration. It would of course be understood by one of ordinary skill in the art that the present invention encompasses other computer system hardware configurations and is not limited to the computer system hardware configuration described above.

Turning to FIG. 2, a display screen of a computer system embodying the present invention includes two general sections, a tray section 12 and an applications section 14. The applications section 14 is the area in which application windows may appear. An application window may occupy the entire applications section 14 or a smaller portion of the entire applications section 14.

The tray section 12 is a portion of the display screen reserved for presenting a modifiable collection of representations corresponding to computer resources which include both objects and controls. The tray section 12 displays representations corresponding to directly accessible computer resources including objects and controls. Display mode controls associated with the tray section 12 enable a user to define how, where, and when the tray section 12 and computer resources associated with the tray are displayed.

The user may either attach the tray section 12 to any of the four sides of the display screen or display the tray section 12 as a palette as shown in FIG. 3. In the palette mode of display for the tray section 12, both the dimensions and position of the tray section 12 are modifiable by the user. In the palette version of the tray section 12 such as the one displayed in FIG. 3, the boundaries of the applications section 14 are the boundaries of the display screen, and the tray section 12 occupies a portion of the display screen within the external boundaries of the applications section 14.

FIG. 2 provides an illustrative depiction of a display screen wherein an edge 17 of the tray section 12 is attached to an edge of the display screen. The user defines the edge of the screen on which the tray section 12 will be displayed by selecting a position presented from a list of options provided to the user by a parameter selection interface such as a user activated menu or dialogue box or direct manipulation via the mouse. When attached to an edge of the display screen, the tray section 12 limits the maximum area taken up by a window presented in the applications section 14 and cannot be displaced by a window displayed in the applications section 14.

In the illustrative depiction of a display screen shown in FIG. 2, the tray section 12 defines a bottom border 16 of the applications section 14 and occupies less than 10 percent of the total area of the video screen. However, the percentage of the display screen occupied by the tray section 12 in FIG. 2 is merely illustrative. The tray section 12 may occupy a greater or lesser percentage of the video screen space depending upon various design considerations and/or the preferences of a user. In one embodiment of the present invention, the user re-sizes the tray section 12 in a direction perpendicular to an attached screen edge by moving a mouse controlled pointer to the inside edge 18 of the tray section 12 and then dragging the edge 18.

Turning to FIG. 5, a flow diagram is provided that summarizes the steps executed by the computer system to re-define the boundaries of the applications section 14 when the user requests movement or re-sizing of the tray section 12. The computer system enters step 100 in response to a request by a user to modify the position and/or size of the tray section 12. Next, at step 102 the computer system saves the current position of the tray section 12 as a temporary variable. Next, at step 104, the computer system saves the requested new position of the tray section 12 and control passes to step 106.

At step 106, the computer system determines whether the requested new position of the tray section 12 is one of the edges of the display screen. If the new position of the tray section is at one of the edges of the screen, then control passes to step 108. At step 108, the computer system retrieves the dimensions of the screen area rectangle and control then passes to step 110. Next, at step 110, the computer system defines and stores in the memory the boundaries of the tray section 12 and the applications section 14 (based upon the new boundaries of the tray section 12). Control then passes to the end 111.

If, however, at step 106 the computer system determines that the user has requested the tray section 12 to be a palette view, then control passes to step 112. At step 112, the computer system determines whether the current position (stored at step 102) is a palette view. If the current position is a palette view, then control passes directly to the end 111 because there is no change in the boundaries of the applications section 14.

If, however, at step 112, the computer system determines that the current position of the tray section 12 is at one of the edges of the display screen, then control passes to step 114 wherein the computer system retrieves the dimensions of the screen area rectangle and control passes to step 116. At step 116, the computer system defines and stores in the memory the boundaries of the applications section 14 which are set equal to the boundaries of the display screen. Control then passes to the end 111.

In an embodiment of the present invention a mechanism is provided for hiding or minimizing the tray section 12 to allow the applications section 14 to occupy all or nearly all of the display screen. In one user specifiable display mode of the tray section 12, the user instructs the computer system to completely remove the tray section 12 from the display screen.

An alternative display mode collapses the tray section 12 so that the tray section 12 occupies a very small portion of the display screen. Turning now to FIG. 4, an illustrative depiction is provided of a display screen after a user prompts the computer system to collapse the tray section 12 to a width of four pixels thereby enabling the applications section 14 to occupy substantially the entire screen. A user causes the tray section 12 to be displayed in the collapsible mode by selecting a "collapse" command from a menu provided by the graphical user interface. Thereafter, the computer system collapses the tray section 12 and re-defines the boundaries of the applications section 14 to occupy almost the entire screen as depicted in FIG. 4.

After the computer system collapses the tray section 12, the user accesses the computer resources of the tray section 12 by bringing a mouse controlled pointer (not shown) into the vicinity of the collapsed tray section 12. When the mouse controlled pointer is placed in the vicinity of the collapsed tray section 12, the extended tray section 12 (illustrated in FIG. 2) replaces the collapsed version (illustrated in FIG. 4) thus providing direct access to computer resources corresponding to the representations displayed in the tray section 12.

Returning to FIG. 2, the tray section 12 includes a command area 22, an extended command area 23 (present when an object embeds and thereby becomes a part of the tray section 12 which is visible whenever the tray section is displayed), and a panel area 24. The command area 22 is always visible when the tray section 12 is visible. The command area 22 of the tray section 12 enables a user to access system commands such as Log Off, Help, Find, Create, etc. by means of a known mouse controlled pointer. The panel area 24 comprises the portion of the tray section 12 in which the user drags and drops objects which recognize and have defined behavior when interacting with the tray section 12. The objects become associated with the tray section 12 of the graphic user interface by means of a docking procedure explained herein below. The extended command area 23 comprises a portion of the tray section 12 that displays embedded applications.

Continuing with the description of FIG. 2, the command area 22 displays a system icon 28. The system icon 28 provides persistent, direct access to a set of operating system commands. Selecting the system icon 28 causes the computer system to display a menu including a set of system commands. The user selects a system command from the menu by means of the mouse 11 or other suitable selection device such as a keyboard 10.

Though the command area 22 of the tray section 12 depicted in FIG. 2 contains only the system icon 28, other computer resources may be included in the command area 22. Further computer resources permanently embedded in the command area may include a searching utility and a help utility. Though three specific examples of computer resources which may reside in the command area have been provided, those of ordinary skill in the art will appreciate that other computer resources can be added to the command area 22.

Continuing with the description of FIG. 2, the panel area 24 of the video interface comprises a set of advanceable panels. In one embodiment of the present invention only one panel is displayed in the tray section 12 at any given point in time. When more than one panel exists for the tray section 12, the user advances through the panels displayed at the panel area 24 by moving a mouse controlled pointer over the panel button 34 and thereafter clicking a mouse button to advance the set of panels associated with the panel area 24 to a desired panel. The selection of a particular panel is alternatively accomplished by selecting the panel from a menu associated with the panel area 24. Though only one panel is visible at any given time, other embodiments of the present invention may provide for the simultaneous display of multiple panels in the tray section 12.

Continuing to reference FIG. 2, the panel area 24 is the portion of the tray section 12 utilized by a user to dock independent objects including: open electronic folders such as Bob's Folder 40, open word documents such as My Document 42, and an unlimited number of other types of applications and computer resources having the necessary information for instructing the computer system how to handle the docking of the application or computer resource and thereafter adding a display element to the tray section 12 corresponding to the docked object. The panel area 24 illustratively depicted in FIG. 2 also displays a printer icon 36 and a wastebasket 38 thus facilitating persistent, direct user access to those well known computer resources. Other computer resources suitable for the tray section 12 are described below.

Having described the display characteristics of the tray section 12, attention is now directed to the internal structure of the portion of the computer system supporting the tray section 12 and the relation of the tray section 12 and the objects associated with the tray section 12 to the rest of the computer system. The general structure of the "Tray Object" responsible for the display and behavior of the tray section 12 of the graphic user interface will be described in conjunction with FIGS. 6a, 6b and 6c. Thereafter, the steps for modification of the contents of the tray section 12 are described in conjunction with the flow diagrams provided in FIGS. 7 and 8.

The portion of the operating system responsible for the tray section 12 of the graphic user interface is a system container that manages, both visually and logically, objects that allow direct access to computer resources encapsulated within the objects. The tray section 12 includes visual display areas defined by the portion of the operating system responsible for the tray section 12 and also areas where independent objects which have become associated with the tray section 12 are displayed. A user, through the graphic user interface, manipulates where and when the independent objects are displayed in the tray section 12.

The collection of representations corresponding to the independent objects (which appear in a form defined by the objects) displayed within the tray section 12 comprise graphic user interface images which are the manifestation of, and result from, interaction between objects encapsulating computer resources which have become associated with the tray section 12 and a portion of the computer system which provides a framework for the displaying and accessing the computer resources when the objects encapsulating the computer resources become associated with the tray section 12. More specifically, the visual and logical behavior of the objects once they become associated with the tray section 12 is determined by properties specified by the objects which are then applied to the framework provided by the portion of the computer system which supports the tray section 12 of the graphic user interface.

Turning now to FIG. 6a, the Tray Object 50 comprises a number of distinct fields relating to the display behavior of the tray section 12 as well as the behavior of independent objects which have become associated with the tray section 12. The Tray Object 50 includes internal tray objects 52, panel objects 54, a pointer to an embedded object 56, a pointer to the current panel object 58, a tray display state variable 60, and a tray position variable 62.

Turning briefly to FIG. 6b, the internal tray objects 52 include the Menu Object 64 which supports the display, selection by a user, and execution of system commands listed within a popup menu associated with the system icon 28 in the command area 22 of the tray. Also included in the Menu Object 64 are the dimensions and placement of the rectangle corresponding to the popup menu associated with the system icon. The Panel Control Object 66 supports the display and selection by a user of a list of panels associated with the tray section 12 from a popup menu associated with the panel button 34. Also included in the Panel Control Object 66 are the dimensions and placement of the rectangle corresponding to the popup menu associated with the panel button 34.

Turning now to FIG. 6c, each panel displayed in the panel area 24 of the tray section 12 is associated with a panel object. The individual panel objects are maintained by an array of pointers stored in the panel objects 54 data structure. If the computer system presently has N panels associated with the panel area 24, then the panel objects 54 comprise an array of N pointers. Returning to FIG. 6a, the Tray Object 50 includes the pointer to the current panel object 58 which points to the location in the panel objects 54 array corresponding to the panel currently visible in the tray section 12.

In an embodiment of the present invention, the tray section 12 supports only a single embedded object. The single embedded object is addressed by the pointer to embedded object 56. Other embodiments of the invention may include multiple embedded objects.

The display state (visible, collapsed, or hidden) as well as the position (palette or attached to an edge) of the tray section 12 have been previously discussed. The tray display state 60 and tray position state 62 variables maintain these two user modifiable characteristics of the tray section 12.

The act of causing an independent object to become associated with the Tray Object 50 is referred to herein as "docking". One manner in which a user invokes the docking process on an independent object is by guiding the mouse controlled pointer to a window displayed in the applications section 14 of the display screen and thereafter selecting a dock command on a menu associated with the window. Alternatively, the user docks an object by selecting the window using the mouse controlled pointer, dragging the window to the panel area 24 and dropping the window in the panel area 24. Of course other methods for a user to invoke the process of docking an independent object to the Tray Object 50 would be known to those skilled in the art in view of the above description of docking a computer resource.

The steps illustrated in FIG. 7 are executed by the computer system when a user attempts to dock an independent object to the tray section 12. In response to the above described user actions, the Dock Object function is called at step 200. Initially, the computer system requires the application responsible for the object to be docked to pass a pointer to the object to be docked. Control then passes to step 202 wherein the computer system determines whether the user is attempting to dock the independent object to the panel area 24.

If, at step 202, the computer system determines that the independent object is to be embedded, then control passes to step 204 wherein the computer system determines whether an embedded object currently exists in the Tray Object 50. If an embedded object currently exists in the Tray Object 50, then control passes to step 206 wherein the computer system discards the currently embedded object according to known Object Linking and Embedding (OLE) procedures. Control then passes to step 208 wherein the computer system stores the pointer to the new embedded object in the pointer to embedded object 56 field of the Tray Object 50 and performs known OLE procedures for embedding the independent object.

If at step 204, the computer system determines that an embedded object did not previously exist in the Tray Object 50, then control passes to step 208. After completion of step 208, control passes to step 210 wherein the computer system determines whether an embedded object previously existed prior to the embedding of the independent object. If no embedded object previously existed in the Tray Object 50, then control passes to step 212 wherein the computer system adjusts the allocation of the space in the tray section 12 to accommodate the portion of the tray section 12 allocated for displaying an embedded object and redraws the panel area to reflect the new space allocation. Thereafter, control passes to step 214 wherein the computer system informs the independent object that it is now embedded in the Tray Object 50 and sets the display state for the embedded object to "visible" to enable display of the embedded object within the tray section 12.

If, however, at step 210 the computer system determines that an embedded object did previously exist in the Tray Object 50, then control passes to step 214 described above. Control then passes to the end step 216.

If, however, at step 202 the computer system determines that the independent object is to be added in the panel area 24, then control passes to step 218 wherein the computer system in a known manner informs the currently displayed panel in a known manner that it is being displaced by a new panel. The display state of the current panel is set to "invisible". Control then passes to step 220 wherein the computer system stores the pointer to the independent object in the array of panel objects 54 field of the Tray Object 50 and performs known OLE procedures for adding the independent object to the Tray Object 50. In addition the pointer to current panel object 58 is modified to point to the location of the new panel object in the array of panel objects 54. Control then passes to step 222 wherein the computer system informs the independent object that it is now associated with the Tray Object 50 and sets the display state for the object to "visible" to enable display of the object within the tray section 12.

From the above description of the docking process, it is apparent that when an object is docked, its relationship to the objects empaneled or embedded in the tray section 12 is characterized in one of two ways.

In a first instance, the docking of the object requires the computer system to create a new panel. A previously displayed panel disappears from view and is replaced by a new panel when the object is docked. An example of such an application is a program manager application described below.

In a second instance, the docked object becomes a part of a permanently displayed extended command area 23 of the tray section 12. This is referred to as an "embedded" computer resource. Advancing the panels in the panel area 24 of the tray section 12 does not cause an embedded computer resource to disappear from the display screen. As a consequence, the portion of the tray section 12 allocated to the panel area 24 is decreased by the amount of display space consumed by the embedded computer resource. An example of such an application is a digital clock display 44 illustratively depicted in FIG. 2. The advanceable panel area 24 is reduced to the area between the command area 22 and the embedded digital clock display 44.

When an application becomes docked to the tray section 12, the independent object defines a set of resources of the object that are easily accessed by the user by means of the tray section 12 and the Tray Object 50 which provides the framework for docked tray objects. When a user docks an application, the application may instruct the CPU 2 to continue executing the docked application displayed in the tray section 12. Because an application is capable of exposing features directly accessible by the user through the application, the docked application can expose key features of its user interface thus enabling the user to control the operation of the docked window without crowding the applications section 14 of the display screen or selecting and de-selecting the window.

An example of the ability of docked resources to expose features which are accessible to the user by means of the graphic user interface is the "Explorer Object". The Explorer Object (shown in the panel section 24 of FIG. 2), in addition to providing a wastebasket and printer facility, also provides a container for dragging and dropping opened folders and documents for temporary storage and easy retrieval. This pseudo-docking of computer resources within a docked object is intended to illustrate the versatility of the Tray Object 50.

The docking of a program manager window is another example of the advantages provided by the tray section 12 of the present invention. In its undocked state, a program manager presents a list of active application programs to the user and means for controlling the execution of the applications programs. The program manager enables the user to cause any of the listed applications to be surfaced (i.e., displayed in the applications section 14). In the docked state, the program manager interface, when displayed in the panel area 24, comprises a set of mouse-controlled pointer-sensitive buttons corresponding to the list of running application programs. The user selects the running application programs for display in the applications section 14 by guiding the pointer to a button representing the desired application displayed in the tray section 12 occupied by the docked program manager and thereafter selecting the application by clicking the mouse.

In an embodiment of the present invention, each application capable of docking within the tray section 12 includes a set of descriptors which inform the computer system of the application program's behavior in regard to the tray section 12. The application program informs the system whether to add the application's docked window image to the currently displayed panel area 24. The application also specifies a desired width for the docked window image. The application designates whether or not the docked application is an embedded form and therefore permanently displayed in the command area 22 of the tray section 12 when docked. Embedded docked applications are discussed in greater detail below.

In order to prevent accidental docking of an application, an application includes a drag/drop enable field. When set to false, a user cannot dock the application by means of the drag/drop process.

An application program also designates a minimum size requirement. Before docking, the CPU 2 determines whether the available space in the present panel exceeds the minimum size requirement for the application. If the CPU 2 determines there is insufficient space available in the presently displayed panel, then the CPU 2 will prevent docking of the application within the current panel area 24.

In a multi-tasking environment, it is important for the computer system to avoid excessive processing of an application which is of lesser importance to the user once the application is docked. As a consequence, each application contains a priority setting designating a relative decrease in execution activity when the application is docked. For example, if an application is allocated 40 percent of the CPU time and the priority setting designates a slow down to 25 percent of its non-docked CPU time, then only 10 percent of the CPU time will be allocated to the docked application. As a further refinement, the application designates distinct priority settings for a visible docked application and a non-visible docked application.

The act of causing an object associated with the Tray Object 50 to become disassociated with the Tray Object 50 is referred to herein as "undocking". In order to "undock" an object residing in the tray section 12, the user selects the computer resource by guiding a mouse-controlled pointer to the display space of the tray section 12 corresponding to the object and thereafter selecting an undock command. Alternatively, the user may undock an object from the panel area 24 by dragging the panel or embedded object out of the tray section 12 and then dropping the panel or embedded object. Of course other methods for undocking a computer resource in the panel area 24 would be known to those skilled in the art in view of the above description of the steps for undocking a computer resource.

The steps illustrated in FIG. 8 are executed by the computer system when a user attempts to undock an empaneled or embedded object from the tray section 12. In response to the above described user actions, the Undock Object is called at step 300. Control then passes to step 302 wherein the computer system determines whether the user is attempting to undock the independent object from the panel area 24. If the computer system determines at step 302 that an embedded object is to be undocked, then control passes to step 304 wherein the computer system discards the embedded object according to known OLE procedures. Control then passes to step 306 wherein the computer system adjusts the allocation of the space in the tray section 12 to accommodate the portion of the tray section 12 re-allocated for displaying the panel area 24 and redraws the panel area to reflect the new space allocation. Control then passes to the end step 308.

If at step 302, the computer system determines that a panel object is to be undocked, then control passes to step 310 wherein the computer determines whether the panel to be removed is the currently displayed panel. If at step 310 the panel to be removed is not the currently displayed panel, then control passes to step 320 wherein the computer system discards the undocked object according to known OLE procedures.

If, however, at step 310 the computer system determines that the panel object to be removed is the currently displayed panel, then control passes to step 312 wherein the computer system informs the panel object that it is being undocked in accordance with known OLE procedures, and the display state of the panel object is set to invisible. Control then passes to step 314 wherein the computer system sets the pointer to current panel object to the next panel object in the array of panel objects 54. Control then passes to step 316 wherein the computer system informs the next panel object in the array of panel objects 54 that it is now the currently displayed panel object and sets the display state of the new current panel object to visible. Control then passes step 320 wherein the computer system discards the undocked panel object according to known OLE procedures. Control then passes to the end step 308.

A number of other applications programs are envisioned. Applications well suited to docking on the tray section 12 include an accessibility package monitor for the visually impaired user, an alarm clock, an application launcher (in contrast to a program manager) which not only surfaces windows but also starts programs. Other examples of possible applications amenable to the tray environment include: a compact disc (CD) or television control panel, a clipboard, a control panel containing a set of most used applications, a drive/volume panel containing a set of memory storage locations, file search facilities, project time clocks, a queue manager, a network manager, a stock ticker tape, a portable personal computer control panel for controlling the energy management routines of the portable computer. Another example for an application suitable for the tray section 12 is a file courier. The file courier would comprise a set of drop fields for files corresponding to such objects as a file compressor, a wastebasket, and an encryption utility. This list of possible applications suitable for the tray environment is certainly not complete. The possibilities for other applications are limitless.

The preferred embodiment of a modifiable, persistent system interface has been described. It would of course be known to one of ordinary skill in the area of user interfaces for computers and operating systems in general to make certain modifications to the afore-described system which would not depart from the scope and spirit of the invention described in the claims appended hereinafter. Such changes might entail modifying the actual computer resources accessed by means of the persistently accessible, user modifiable interface described above. It would also be known to modify the above disclosed system so that it is incorporated within a local area network, or a group of computer work stations sharing a mainframe operating system.

Claims

What is claimed is:

1. A computer system providing constant direct access to a set of computer resources, the system comprising:

an electronic data storage;

a central processing unit (CPU) coupled to the electronic data storage for executing electronically encoded machine commands retrieved from the electronic data storage;

a user interface facilitating user access to the variety of computer resources, the user interface including:

a video display for presenting video images in accordance with signals transmitted by the CPU and constituting a video interface between a user and the CPU, said video interface including:

an applications section defined by an applications section boundary for displaying images corresponding to signals transmitted by the CPU in accordance with the execution of an application program by the CPU, the executing application being displayed in a window that is fully contained within the boundary of the applications section; and

a resizable tray section defined by a tray section boundary and displayed as being attached to an edge of the video display for displaying a collection of representations corresponding to the variety of computer resources, the tray section boundary being used to delimit the applications section boundary such that the tray section and the applications section do not overlap;

a display set modifier for altering the collection of representations displayed in the tray section; and

means for accessing the variety of computer resources corresponding to the collection of representations by selecting ones of the collection of representations displayed in the tray section.

2. A computer system providing constant direct access to a set of computer resources, the system comprising:

an electronic data storage having electronically encoded machine commands;

a central processing unit (CPU) coupled to the electronic data storage for executing the electronically encoded machine commands retrieved from the electronic data storage; and

a user interface facilitating user access to the variety of computer resources, the user interface including a video display for presenting video images in accordance with signals transmitted by the CPU and constituting a video interface between a user and the CPU, the video interface including an application section for displaying a windowed representation of an executing application program docked on the application section and an extensible tray section displayed as being attached to an edge of the video display for displaying an iconic representation of the executing application program docked on the tray section, wherein the application section is defined by an application section boundary, the tray section is defined by a tray section boundary, the tray section boundary delimits the application section boundary such that the tray section and the application section do not overlap, and the windowed representation of the executing application program is fully contained within the application section boundary irrespective of any changes made to the boundary of the extensible tray section.

3. The computer system as recited in claim 2, wherein the application section occupies a substantial majority of the video interface and the tray section occupies a substantial minority of the video interface.

4. The computer system as recited in claim 3, wherein the tray section is hideable.

5. The computer system as recited in claim 3, wherein the tray section is minimizeable.

6. A graphical user interface for a computer system, the graphical user interface providing a user continuous convenient access to computer resources associated with a plurality of active applications, the graphical user interface comprising:

a video display having an application section for displaying a windowed representation of an executing application program docked on the application section and an extensible tray section for displaying an iconic representation of the executing application program docked on the tray section, wherein the application section is defined by an application section boundary, the tray section is defined by a tray section boundary, the tray section boundary delimits the application section boundary such that the tray section and the application section do not overlap, and the windowed representation of the executing application program is fully contained within the application section boundary irrespective of any changes made to the boundary of the extensible tray section.

7. The graphical user interface as recited in claim 6, wherein the user responsive means comprises a mouse.

8. The graphical user interface as recited in claim 7, wherein the application section occupies a substantial majority of the video display and the tray section occupies a substantial minority of the video display.

9. The graphical user interface as recited in claim 8, wherein the tray section is hideable.

10. The graphical user interface as recited in claim 8, wherein the tray section is minimizeable.

11. In a computer system having a graphical user interface, a method for providing a user continuous convenient access to computer resources associated with an executing application, the method comprising the steps of:

causing a display space to be partitioned into an application section and an extensible tray section, wherein the tray section is displayed as being attached to a side of the display space, the application section is defined by an application section boundary, the tray section is defined by a tray section boundary and the tray section boundary delimits the application section boundary such that the tray section and the applications section do not overlap;

causing a first image representative of the executing application program docked on the application section to be displayed in the application section in a window, the window being fully contained within the application section boundary irrespective of any changes made to the tray section boundary;

allowing a command to be issued to change the docking of the executing application program from the application section to the tray section; and

causing, in response to the issuance of the command, a second image representative of the executing application program docked on the tray section to be displayed on the tray section while causing the first image to be removed from the application section.

12. The method as recited in claim 11, further comprising the step of assigning a priority to the executing application program when docked on the tray section, the priority designating a relative decrease in execution activity.

13. The method as recited in claim 11, wherein the step of causing the display space to be partitioned comprises the step of allocating a substantial majority of the display space to the application section a substantial minority of the display space to the tray section.

14. The method as recited in claim 13, further comprising the step of accepting a command to hide the display of the tray section.

15. The method as recited in claim 13, further comprising the step of accepting a command to minimize the display of the tray section.