US 7,624,356 B1Grant

Task-sensitive methods and systems for displaying command sets

Issue Date:2009-11-24

•43 Claims

•14 Drawing Sheets

Abstract

Methods and systems present commands to a user within a software application program by determining the user's context within the application program and automatically presenting in a user interface commands that pertain to the user's current context. When the user's context changes, the context-sensitive commands are automatically removed from the user interface. In one implementation context blocks and context panes are employed to present the commands.

Metadata

Assignee

Microsoft Corporation

Inventors

Eric S. Rockey
Shannon P. Talbott
Gavin M. Kelly
Nancy E. Jacobs
Michael J. Hopcroft
Daniel J. Westreich
Jonathan D. Perlow
Paul R. Erickson

Application Information

Application Number:US 09/599,086

Filing Date:2000-06-21

Priority Date:2000-06-21

Art Unit:2173

Classifications

IPC:

G06F3/048

Patent Drawings (14 sheets)

Description

RELATED APPLICATIONS

[0001] The following patent applications are related to the present application, are assigned to the assignee of this patent application, and are expressly incorporated by reference herein:

- [0002] U.S. patent application Ser. No. 09/599,298, entitled “Single Window Navigation Methods and Systems”, and filed on the same date as this patent application;
- [0003] U.S. patent application Ser. No. 09/599,806, entitled “Methods and Systems of Providing Information to Computer Users”, and filed on the same date as this patent application;
- [0004] U.S. patent application Ser. No. 09/599,299, entitled “Methods, Systems, Architectures and Data Structures For Delivering Software via a Network”, and filed on the same date as this patent application;
- [0005] U.S. patent application Ser. No. 09/599,048, entitled “Network-based Software Extensions”, and filed on the same date as this patent application;
- [0006] U.S. patent application Ser. No. 09/599,813, entitled “Authoring Arbitrary XML Documents Using DHTML and XSLT”, and filed on the same date as this patent application;
- [0007] U.S. patent application Ser. No. 09/599,812, entitled “Architectures For And Methods Of Providing Network-based Software Extensions”, filed on the same date as this patent application.

TECHNICAL FIELD

[0008] This invention relates generally to methods and systems that expose commands in software application programs.

BACKGROUND

[0009] Typically, application programs contain command sets that include individual commands that can be used by a user when working in a particular application program. These commands are specific to the purpose of the application program. For example, a word processing application program will typically include a command set that can be used to manipulate the text and/or format of a document. These command sets, however, are not always as easy to use as one would like. This situation can be complicated when a user is not familiar with the command set of an application program that they are currently using.

[0010] Current problems with application program command sets include that they can be difficult to use or browse because of the large number of commands that can be included in a command set, and that they often times can temporarily obscure a document when a user attempts to use them. In addition, command sets are typically presented in a manner that is not related to the tasks in which the user might be engaged.

[0011] With respect to the browsing difficulty of command sets, consider the following. Command sets can typically contain many different commands that are available for use. Since, in a typical user display, there is only a limited amount of space to present information without undesirably obscuring a work area, it logically follows that not all commands can be displayed at all times for the user. To address this problem, solutions have included providing a static tool bar that can expose some commands and contain a menu structure that can be browsed by the user. Consider, for example, FIG. 1 which shows an exemplary user display 10 that includes a tool bar 12 that includes a menu structure 14 and a collection of commands 16. The menu structure 14 includes individual entries, e.g. “File”, “Edit”, “View”, “Insert”, etc. Each of these entries is associated with a drop down menu that contains a collection of individual commands that are logically related to their entry. For example, for the “File” entry, individual drop down menu-accessible commands include “new”, “open”, “close”, “print”, “print preview” and additional commands that are accessible via an “options” selection that further extends the drop down menu to display the additional commands. Each of the top line menu entries in the menu structure 14 can be associated with a drop down menu. Also, some of the commands are gathered into broad groups (such as the Font Formatting dialog) and the user needs to know what Font Formatting is, in order to find the commands in this group. Needless to say, the number of available commands can often times be quite numerous so that browsing through them is not an easy task. In addition, an inherent inefficiency with this approach is that many if not most of the displayed commands will have little or nothing to do with what the user is currently looking for. Often, in fact, many of the commands are grayed out and disabled because they are not relevant to the current task. Regardless, they are exposed to the full subset of commands.

[0012] Consider how this problem is exacerbated when a user is only moderately familiar or not familiar at all with an application program. Having to figure out and navigate through an extensive set of commands that are not explained (except for perhaps a “Help” dialog) can make the user's experience difficult and time consuming. In addition, many application programs are physically or logically tapped out as far as including additional commands. Specifically, in many application programs there are simply so many commands in the command set that including more commands would require the menu structure to include more “options” buttons that, in turn, would present more and more commands, thus requiring a user to physically navigate through more commands.

[0013] Additionally, many application programs display their command sets in a manner that can obscure the work area for the user. For example, consider FIG. 2 which shows a “Font” dialog box 18 that is presented in the middle of the user's work area. To get to this dialog box, the user had to click on the “Format” menu entry in menu structure 14, and then select the “Font” command within the drop down menu that was presented. As a result the illustrated dialog box 18 is displayed. Although this is helpful for enabling a user to see an extensive list of commands, it is not optimal for a couple of different reasons. First, the user's document is partially obscured by the dialog box 18. This is undesirable because the user may wish to keep the work area in view. In addition, in order to work within the dialog box, the user has to quit working within their document. Thus, the dialog box is referred to as having “mode” or being “modal”, meaning that a user must enter into a particular mode that renders them unable to work within their document in order to work within the dialog box. Second, and perhaps more important, the user's command selection is not implemented immediately, and, even if it were, the document is obscured by the dialog box. Specifically, in order to have a command implemented, e.g. a “strikethrough” command, the user must select text in the document that they are working on and pull up the dialog box. Only after they click on the “strikethrough” box and on the “OK” box is the command implemented (this is somewhat related to the mode aspect mentioned above). In addition, if a user desires to implement a command on multiple different portions of text, they must separately select each text portion and apply the command for each selected portion of text. That is, for each portion of text, they must separately and individually pull up the appropriate dialog box to apply the command. This is not optimal.

[0014] Consider also the collection of commands 16. Many application programs provide such a feature where frequently used commands are displayed in a manner in which they can be quickly clicked on by a user and applied within the context of the application program. These commands are often presented as so-called “modeless” commands (as contrasted with “modal” commands) because they can be used while still working within a document. That is, in the illustrated example, individual commands from the collection include “bold”, “italics”, and “underline” commands. Yet, even though the goal of displaying these frequently-used commands is directed to improving user efficiency, this attempt falls short of the mark for the following reason. Even though the commands that are displayed might be considered as those that are most frequently used, their use occurrence may constitute only a very small portion of a user session, if at all. To this extent, having the commands displayed when they are not being used is wasteful in that valuable display real estate is consumed. This is a direct manifestation of the fact that the displayed commands have nothing to do with the specific context of the user. Yes—the user might in the course of their computing session have the need to use a particular command, but until that command is specifically needed by the user, its display bears no logical relation to the user's computing context.

[0015] Accordingly, this invention arose out of concerns associated with providing improved methods and systems for presenting command sets to users. Specifically, the invention arose out of concerns associated with providing methods and systems of presenting commands in a task-sensitive manner, which assist in using physical screen space in a more efficient manner.

SUMMARY

[0016] Methods and systems present commands to a user within a software application program by determining the user's context within the application program and automatically presenting in a user interface context-sensitive commands that pertain to the user's current context. When the user's context changes, the context-sensitive commands are automatically added to the user interface or removed from the user interface so that space can be freed up for additional, more relevant commands.

[0017] In one implementation context blocks and context panes are employed to present the commands. The context blocks and panes are displayed in a context UI container that is located adjacent a document area in a user interface. When displayed, the context blocks and context panes do not obscure a user's document.

[0018] The context blocks and panes each comprise a title bar area that labels the block or pane, and a controls area that presents commands to the user. The commands within the controls area can be logically grouped. The context blocks contain primary commands that pertain to a user's present context. More than one context block can be displayed in the context UI container. Context panes are associated with a context block and are not automatically displayed. Rather, a user can select one or more context panes from a particular context block, keyboard shortcut, or from other tool bars. The context panes contain additional commands that are logically associated with the commands of their associated context block. When displayed, the context panes replace the context blocks in the context UI container and must be closed by the user.

[0019] In one embodiment, a user's context is determined by monitoring the user's action within a particular application program. A series of expressions are provided and describe conditions that are associated with aspects of a user's interaction with the application program. Each expression is associated with a context block. As the user's context changes, at least portions of the expressions are evaluated to determine whether its associated context block should be displayed. In one optimization, each expression is represented as a tree structure with a root node and multiple nodes associated with the root node. Each of the nodes has a value associated with it that can change as a user's context changes. When a user's context changes, individual node values are evaluated for a change. If a node value changes, then its parent node is notified with the change. The parent node then evaluates its value to ascertain whether it has changed responsive to its child's value change. This process continues whenever a node value changes. If the root node value changes, then the context block with which it is associated is either automatically displayed or removed.

[0020] In one particular advantageous implementation, a single application program is provided with a single navigable window. The application program comprises multiple different functionalities to which the single navigable window can be navigated. The different functionalities enable a user to accomplish different tasks. For example, in one implementation, a user might read electronic mail, compose an electronic mail message, or navigate to sites on the web. As the user navigates between functionalities and as their context changes within particular functionalities, context blocks are automatically presented and/or removed so that they can have useful commands at hand to use. The functionalities of the single application program are desirably extensible, e.g. by incorporating third party functionalities that can be delivered over the web, so that the application can incorporate many different types of functionalities. Each of the incorporated functionalities can come with its own collection of automatically displayable context blocks.

BRIEF DESCRIPTION OF THE DRAWINGS

[0021] FIG. 1 is an illustration of an exemplary user display in accordance with the prior art.

[0022] FIG. 2 is an illustration of an exemplary user display that includes a dialog box in accordance with the prior art.

[0023] FIG. 3 is a high level block diagram of an exemplary computer system that can be utilized to implement various inventive embodiments.

[0024] FIG. 4 is a flow diagram that describes steps in a method in accordance with one described embodiment.

[0025] FIG. 5 is a diagram of an exemplary user interface in accordance with one described embodiment.

[0026] FIG. 6 is a diagram of an exemplary context block in accordance with one described embodiment.

[0027] FIG. 7 is a diagram of an exemplary context pane in accordance with one described embodiment.

[0028] FIG. 8 is a flow diagram that describes steps in a method in accordance with one described embodiment.

[0029] FIG. 9 is a diagram of a table in accordance with one described embodiment.

[0030] FIG. 10 is a diagram of a tree structure in accordance with one described embodiment.

[0031] FIG. 11 is a flow diagram that describes steps in a method in accordance with one described embodiment.

[0032] FIG. 12 is a diagram of a user interface in accordance with one described embodiment.

[0033] FIG. 13 is a diagram of a user interface in accordance with one described embodiment that illustrates an exemplary functionality.

[0034] FIG. 14 is a diagram of a user interface in accordance with one described embodiment that illustrates an exemplary functionality.

[0035] FIG. 15 is a flow diagram that describes steps in a method in accordance with one described embodiment.

DETAILED DESCRIPTION

Overview

[0036] The methods and systems described below present commands to a user within a software application program by determining the user's context within the application program and automatically presenting, in a user interface, context-sensitive commands that pertain to the user's current context. When the user's context changes, the context-sensitive commands can be automatically removed from the user interface.

Exemplary Computer System

[0037] FIG. 3 shows an exemplary computer system that can be utilized to implement the embodiment described herein. Computer 130 includes one or more processors or processing units 132, a system memory 134, and a bus 136 that couples various system components including the system memory 134 to processors 132. The bus 136 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. The system memory 134 includes read only memory (ROM) 138 and random access memory (RAM) 140. A basic input/output system (BIOS) 142, containing the basic routines that help to transfer information between elements within computer 130, such as during start-up, is stored in ROM 138.

[0038] Computer 130 further includes a hard disk drive 144 for reading from and writing to a hard disk (not shown), a magnetic disk drive 146 for reading from and writing to a removable magnetic disk 148, and an optical disk drive 150 for reading from or writing to a removable optical disk 152 such as a CD ROM or other optical media. The hard disk drive 144, magnetic disk drive 146, and optical disk drive 150 are connected to the bus 136 by an SCSI interface 154 or some other appropriate interface. The drives and their associated computer-readable media provide nonvolatile storage of computer-readable instructions, data structures, program modules and other data for computer 130. Although the exemplary environment described herein employs a hard disk, a removable magnetic disk 148 and a removable optical disk 152, it should be appreciated by those skilled in the art that other types of computer-readable media which can store data that is accessible by a computer, such as magnetic cassettes, flash memory cards, digital video disks, random access memories (RAMs), read only memories (ROMs), and the like, may also be used in the exemplary operating environment.

[0039] A number of program modules may be stored on the hard disk 144, magnetic disk 148, optical disk 152, ROM 138, or RAM 140, including an operating system 158, one or more application programs 160, other program modules 162, and program data 164. A user may enter commands and information into computer 130 through input devices such as a keyboard 166 and a pointing device 168. Other input devices (not shown) may include a microphone, joystick, game pad, satellite dish, scanner, or the like. These and other input devices are connected to the processing unit 132 through an interface 170 that is coupled to the bus 136. A monitor 172 or other type of display device is also connected to the bus 136 via an interface, such as a video adapter 174. In addition to the monitor, personal computers typically include other peripheral output devices (not shown) such as speakers and printers.

[0040] Computer 130 commonly operates in a networked environment using logical connections to one or more remote computers, such as a remote computer 176. The remote computer 176 may be another personal computer, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to computer 130, although only a memory storage device 178 has been illustrated in FIG. 3. The logical connections depicted in FIG. 3 include a local area network (LAN) 180 and a wide area network (WAN) 182. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets, and the Internet.

[0041] When used in a LAN networking environment, computer 130 is connected to the local network 180 through a network interface or adapter 184. When used in a WAN networking environment, computer 130 typically includes a modem 186 or other means for establishing communications over the wide area network 182, such as the Internet. The modem 186, which may be internal or external, is connected to the bus 136 via a serial port interface 156. In a networked environment, program modules depicted relative to the personal computer 130, or portions thereof, may be stored in the remote memory storage device. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used.

[0042] Generally, the data processors of computer 130 are programmed by means of instructions stored at different times in the various computer-readable storage media of the computer. Programs and operating systems are typically distributed, for example, on floppy disks or CD-ROMs. From there, they are installed or loaded into the secondary memory of a computer. At execution, they are loaded at least partially into the computer's primary electronic memory. The invention described herein includes these and other various types of computer-readable storage media when such media contain instructions or programs for implementing the steps described below in conjunction with a microprocessor or other data processor. The invention also includes the computer itself when programmed according to the methods and techniques described below.

[0043] For purposes of illustration, programs and other executable program components such as the operating system are illustrated herein as discrete blocks, although it is recognized that such programs and components reside at various times in different storage components of the computer, and are executed by the data processor(s) of the computer.

Context Sensitive Commands

[0044] In the described embodiment, command sets that include one or more individual commands are automatically presented to a user depending on the user's context. Specifically, depending on the type of action the user has taken, commands that are specific to that action will appear automatically thus obviating the need for the user to hunt through a menu structure to find commands of interest. This improves upon past approaches, which always presented top level commands, even when they were not needed by the user. This is also advantageous from the standpoint of assisting users who are unfamiliar with a particular software application. In the past, these users would have to hunt through an unfamiliar menu structure to find commands that may or may not be pertinent to an action that the user desired to take. Users also had to know the names of the functionality in order to find the tools (e.g. the user needed to know what a “table” was to know that there are tools for tables in an appropriate menu). In the present case, contextually-appropriate commands are automatically presented and removed in an interface so that a user need not worry about finding appropriate commands. That is, the described embodiment maintains an invariant that contextually applicable commands are visible and other non-applicable commands are hidden from the user.

[0045] As an example, consider the following: A user is working in a word processing application and is in the process of preparing a document. The user selects, with their cursor, a portion of the text that they believe to be spelled incorrectly. Instead of having to go to a tool bar menu at the top of the document and pull down one or more other menus to find the spell checking feature, a spell checking context block automatically appears in an interface adjacent the document. The user can then correct the incorrectly spelled word using the spell checking context block. Once the word is corrected and the user's context is not longer associated with an incorrectly spelled word, the spell checking context block automatically disappears. As the user's context changes within their document, so too do the sets of automatically presented and removed commands. Consider further that the user has included a table in their document and that they wish to manipulate the table or its contents with table specific commands. In the past, the user would typically have to pull down a table menu entry and then select from one or more commands, some of which might present a dialog box that would obscure the user's document. In the present example, a user would simply select the table by placing the cursor inside of the table to have table-specific commands that are contextually accurate and appropriate automatically displayed in a dedicated space. Thus, a user need not hunt through a large menu structure to find commands that are appropriate for use. Here, contextually proper commands are automatically presented for the user. As the user's context changes, so too do the displayed command sets.

[0046] FIG. 4 is a flow diagram that describes steps in a method in accordance with the described embodiment. The illustrated method can be implemented in any suitable hardware, software, firmware, or combination thereof. In the present example, the method is implement in software that is executing on a user's computer.

[0047] At step 400 the method starts and step 402 then determines whether the user's current context has changed. The user's current context relates to various tasks that the user is attempting to accomplish. Context can be determined from almost any detectable state in a program. In the above example, two exemplary tasks included correcting an incorrectly-spelled word and manipulating the contents of a table. The context associated with each of these tasks can be determined from such things as the type of document a user is working in (i.e. which of the multiple different functionalities the user is accessing), the state that the document is currently in, for example, whether the document is in read-only (or browse) mode or is editable, the cursor's current location within a document (i.e. is the cursor located within a table, spreadsheet, etc. within a document), or a particular selection that might be made within the document (i.e. selection of text, a table, etc.). Other examples of things from which context can be determined include, without limitation, whether or not a certain extension has been installed, today's date is after the due date of a particular document, the document contains comments that need to be addressed, the subject line of an email message is missing, the document contains misspelled words, and the like. Any suitable way can be used to ascertain whether a user's context has changed.

[0048] If step 402 ascertains that a user's current context has changed, step 404 makes a command set change as a function of the user's context. Specifically, command sets can be added and/or removed automatically based upon the user's context.

Context Container, Context Blocks, Context Panes

[0049] FIG. 5 shows an exemplary user interface (UI) display 500 that constitutes but one implementation of a system that automatically presents context-sensitive commands to a user. Other implementations can, of course, be used without departing from the claimed subject matter.

[0050] In the illustrated example, display 500 includes a context UI container 502 and a document area 504 adjacent the context UI container. The context UI container is a narrow, vertically aligned user interface space that can be used to expose commands in a software application. The context UI container 502 is designed, in a particular implementation, to work with applications whose functionalities are primarily oriented around interacting with documents. The context UI container 502 does not preclude other UI constructs in the application, and indeed this design assumes some additional UI such as a toolbar with commands on it such as would be displayed in global toolbar area 506. Such commands can include, without limitation, an address well for a web browser, a “Create New” button for creating a new document type, or a button that brings up “search” or “help”.

[0051] The context UI container 502 is designed, in this example, to lay to the left of the document area 504 in the application. It could, however, be situated in any suitable location. The context UI container 502 contains two types of objects that are utilized to display context-sensitive commands to a user. A first type of object is a context block, exemplary ones of which are shown at 508a-c. Context blocks are essentially context-based palettes with command “shortcuts”, giving the user top-level tools for the current user contexts. In the present example, there are context blocks for editing commands (block 508a), text commands (block 508b ), and table commands (block 508c). The assumption in this example is that a user has a table selected, and thus all three of these blocks are relevant. A second type of object is a context pane. Context panes provide access to secondary tools for a context and are used to complete a specific task. The secondary tools are generally more specific or more advanced functionalities relating to the context block with which the pane is associated.

[0052] In the described embodiment, context blocks automatically appear and disappear based on the user's context and have two primary forms when visible: expanded and collapsed. Context blocks are expanded by default and collapse only by manual action from the user. Context panes take up the entire context UI container 502 and focus the user on completing a task before they can continue with other commands in the application.

Context UI Container

[0053] The context UI container 502 is a collapsible vertical area that contains context blocks and context panes. The context UI container 502 can toggle between expanded and collapsed states as indicated above. When collapsed, the container is not visible at all. When expanded, the context UI container 502 is typically of a fixed size, e.g. 184 pixels wide, though it can grow wider to accommodate wider context blocks or context panes.

Changing the Context UI Container Expansion State

[0054] In the described embodiment, the user can manually change the expansion state of the context UI container by clicking on a “Tools” button on a global toolbar in an application. This button can toggle container's expansion state. When the container is expanded, the button is visualized as toggled “on”. When the container is collapsed, the button is visualized as toggled “off”.

[0055] In addition, the context UI container 502 can be expanded programmatically. For example, if the user clicks on a command elsewhere in the application that requires that the container to be open, then the context UI container automatically opens. When the context UI container opens, the left border of the document being viewed by the application shifts over and the document's total width is decreased by the size of the context UI container 502.

Population of the Context UI Container

[0056] The context UI container 502 can be populated with both context blocks or context panes. In addition, the context UI container can be populated with a help pane. The help pane looks like a context pane, but appears next to either a context pane or the context blocks; it is approximately the same size and shape as a context pane, is launched programmatically, and is associated with a context block or context pane. Context blocks appear in the context UI container by default. Exemplary context blocks 508a-c are shown in FIG. 5. Context block 508a contains commands that are associated with editing a document; context block 508b contains commands that are associated with manipulating text within a document; and context block 508c contains commands blocks that are associated with operating on a table. As is evident, more than one context block can be displayed at one time.

[0057] Context panes, on the other hand, are configured in this example so that they can only be viewed one at a time. And, while context blocks are displayed automatically depending on the user's context, context panes are displayed, in this example, when they are selected by a user. Context panes are task oriented and are dismissed by a user when the task is completed. Although the user dismisses them, context panes are modeless in that the user can continue acting on the document while the pane is open. Context panes can also be used to communicate an alert to a user. For example, if the user is trying to publish a document, but cannot do so because of a merge conflict, a merge conflict user interface may be provided through a context pane.

[0058] To determine which context blocks to automatically display, one implementation uses an expression-based system that ascertains the user's context and then sees to it that the proper context blocks are displayed. An exemplary expression-based system is described in more detail below in a section entitled “Expression Evaluation”.

Sizing and Overflow Issues

[0059] The context UI container 502 is of fixed size vertically, but the number and size of context blocks is not limited. Therefore, there may be situations in which an application does not have enough room to display all of the current context blocks. This is referred to as an “overflow case”. The overflow case occurs when there is not enough vertical room in the context UI container 502 to display all of the context blocks. One solution of the overflow case, in this particular example, is as follows: When an overflow occurs, the application can display a small scroll button at the bottom of the context block container. This button serves as an indicator that there are one or more context blocks scrolled out of the container. Clicking on the button once scrolls down by a predetermined number of pixels, e.g. 44 pixels, or to the end of the last context block, whichever is less. This, in turn, causes part or all of some context block to scroll off of the top of the context UI container 502. Accordingly, the context UI container 502 will also show a scroll button at its top when this occurs. Clicking on this top button will scroll up by a predetermined number of pixels, e.g. 44 pixels, or to the top of the first context block, whichever is less.

[0060] If there are no more context blocks or parts of context blocks scrolled out of the container in a certain direction (either up or down), then the corresponding respective scroll button will disappear. Since the scroll buttons take up space in the container 502, the calculation for when the scroll buttons should disappear takes into account the additional room that would appear if the button were not there.

Application Window Resizing Issues and the Context UI Container

[0061] The context UI container 502 is defined in the illustrated example to have a standard size horizontally and is sized to fit the application window vertically. The context UI container 502 responds to window/resolution resizing issues as follows: Vertically, the container resizes to fit into the space left over in the application frame from any other UI areas at its top or bottom. If the vertical space is not enough to hold all context blocks, then the overflow mechanism described above is invoked. Horizontally, the context UI container does not resize except to accommodate larger context blocks or context panes. Other than this case, the container only expands or collapses completely. The container does not resize horizontally due to the application window resizing. If the user resizes the window horizontally so that the window is narrower than the context UI container, the container will be clipped.

Context Blocks

[0062] In the illustrated example, context blocks are rectangular control containers that expose top-level commands for a given context. A context is anything that can be described by an “expression” in the application. Examples of expressions are given below. Typical contexts include: the type of document being currently viewed, the state that the document is currently in, for example, whether the document is in read-only (or browse) mode or is editable, and any objects that are currently selected in the document. Other contexts were listed above. Context blocks appear and disappear based on whether an expression that describes their context is true or false, respectively. This is discussed in more detail in the “Expression Evaluation” section below.

[0063] FIG. 6 shows exemplary context block 508b apart from the context UI container 502 of FIG. 5. Context block 508b displays text formatting commands. Each block comprises a title bar area 600 and a controls area 602.

[0064] The title bar area 600 provides a location to label the entire context block, provides expand/collapse functionality, and also contains a button 604 that opens up the context block menu. The user can click anywhere on the title bar outside of the menu button to toggle the expansion state of the context block. On the right-hand side of the title bar area 600, button 604 can be clicked to bring up a menu that can contain links to context panes, as well as commands that execute immediately without invoking a context pane. The menu then closes after the user invokes a command from it.

[0065] The controls area 602 is the main area of the context block and exposes commands to the user. In the illustrated example, the controls area allows any arbitrary HTML code to be filled into it, so commands can be exposed in any way that HTML supports. Of course, other manners of defining commands other than HTML can be used. Context blocks are advantageously “modeless” meaning that any action taken by the user is immediately applied to the user's selection in the document. This is advantageous over past methods because a user can experiment with different selections that are available through the context block and see their choices immediately effectuated in their document. In some cases, this eliminates the need for a costly (in terms of both space and time) “preview pane.” This does not, however, mean that the context blocks must always be modeless. For example, a context block for inserting a table could be provided where the user sets the number of rows and columns before pressing an “insert” button.

[0066] One feature of context blocks that prevents them from being inadvertently displayed is that a selection that is made by the user in a particular document (e.g. with their cursor) must contain only content that is pertinent to a particular set of displayable commands. If the user's selection includes an object but also additional content around the object, then the context block for that object will not be displayed. So for example, in order to have a table formatting context block visible, the user's selection would need to contain only the table, or the user's insertion point (i.e. cursor) would have to be in the table.

Context Panes

[0067] In the described embodiment, context panes, like context blocks, are also rectangular controls containers. One primary difference in this implementation is that context panes are typically larger than context blocks and only one context pane can be viewed at one time. It will be appreciated, however, that this is simply a choice for this particular implementation.

[0068] Context panes are used to expose secondary commands as well as task-based UIs, such as stepping through document publishing merge conflicts, in the application. Context panes can also be used to display various error messages related to the current document, such as when there are versioning problems when publishing a document and the user needs to make a decision about which version to keep. To maintain consistency, commands that are contained in context blocks are also repeated in their associated context panes.

[0069] Context panes can be accessed from the menus of their associated context blocks, through keyboard shortcuts, or from other UIs in the application, such as from a global toolbar. In the described embodiment, when a context pane is invoked, the entire content of the context UI container 502 (FIG. 5) is replaced with the context pane. Advantageously, context panes are typically modeless with respect to the document. This means that the user can continue to interact with their document while a context pane is open. For example, if a user wishes to use a strikethrough command repeatedly in a portion of text, the user can do this time after time by simply selecting the appropriate text and clicking on a strikethrough box in the context pane. In the past, a user would have had to traverse a menu structure for each separate invocation of the strikethrough command.

[0070] FIG. 7 shows an exemplary context pane 700 that includes secondary format font commands. Context pane 700 includes a title bar 702 and a controls area 704 that contains individual commands. A context pane looks similar to a context block that fills up the entire context UI container. There are, however, a few differences in the described example. Here, context panes are not collapsible. That is, they are displayed in their entirety for a user during the course of a user's interaction with them. In addition, context panes have a standard way to be closed, e.g. a “Close” button or the equivalent at the bottom of the panel can be clicked on by the user.

[0071] In addition, whereas a user does not have to request a context block in order for it to appear, a user does, in most cases, request a context pane for it to appear. That is, context panes are not automatically displayed as a result of an expression evaluation. Rather, they are displayed based on some event or function call. There can be, however, some context panes that are expression based and are not end-user initiated (e.g. an error context pane that informs a user of an error condition). In addition, in this example, the user must also physically dismiss a context pane when it is no longer needed. That is, the context pane will not automatically disappear. Thus, the user is free to move their selection around the document while interacting with a context pane. If the context pane's functionality is context sensitive (for instance if it contains tools that only apply to a table within the document), then the controls in the context pane become disabled if they are out of context. The context pane typically does not disappear or collapse, in many instances, when it goes out of context.

User Assistance in Context Panes

[0072] Context panes are used to provide access to the full range of commands in an application. In this way, context panes complement context blocks. There may be instances where a user may not be familiar with all of the commands that are displayed in the context pane. Accordingly, in the described embodiment, the context panes provide context-sensitive access to help for their commands via a pop-out help pane. This help pane appears to the right of the context pane and causes the context UI container to grow horizontally. This pushes the user's document somewhat to the right. The help pane provides quick, contextual help on how to use the controls on the pane or context block. In the FIG. 7 example, the help pane is accessed by a help icon 706 (“?”) on the right side of the context pane's title bar 702.

[0073] This is much different from current help features in most current application programs. Presently in many applications, a user will have to either search through a help menu to find particular topics of interest, or they may have to enter a search query through a dialog box that typically pulls up multiple topics that relate to their search. They must then navigate through the different multiple topics to find the one in which they are interested. “Help” in these instances, is typically delivered as a separate application, overlaying, obscuring, or displaying outside of the user's application window. There is no awareness of the context of the user's work. Here, however, the described approach is somewhat different. First, the help function is contextually related to the current context pane. Thus, the user only receives help information that is pertinent to their current context. Additionally, because the help information is specifically tailored to the user's current context, and because there is a dedicated space for the context blocks and context panes, more thorough help information can be displayed in the container UI than would normally be possible in present systems. In addition, the help feature is rendered in a “modeless” fashion so that the user can continue working in their document while the help menu is displayed. Further, it is worth noting that the contextual help provided by the present example is tailored not only to the user's context, but to the tasks and troubleshooting steps that are most likely to be needed by the user in that context. For instance, if the user is correcting a misspelled word in the document by using a context pane designed for that purpose, the help pane associated with that context pane may contain information about how to correct the misspelled word with one of the provided choices, how to add the word in question to the system dictionary, and how to replace the word in question with a different word altogether. Accordingly, the user is provided with assistance in a much more efficient and informative way.

Stackability

[0074] Although only one context pane can be viewed at a time, it is possible for multiple panes to be stored in a stack. In this case, closing one context pane reveals the next context pane in the stack. There are a number of cases where context panes can get stacked on top of each other. The following constitute some exemplary cases:

- [0075] A context pane is open and then an error context pane is displayed
- [0076] A context pane is open and the user then opens up another context pane from a button on the global toolbar.
- [0077] A context pane has a button that opens another context pane.
- [0078] A context pane is open and the user hits an accelerator key that opens up another context pane

[0079] In each case above, the latter context pane opened goes to the top of the stack, while the previous context pane goes underneath it on the stack.

[0080] In addition, each document can have its own stack of context panes. If the user navigates away from a document and back to it, the document's stack of context panes persists and is redisplayed (though it is possible for members of a stack to be aged out).

Expression Evaluation

[0081] As described above, context blocks are automatically presented to the user depending on the user's current context. In the described embodiment, an expression-based method is used to ascertain which contexts blocks to present and when to present them.

[0082] One way of implementing an expression-based method is as follows. Each context block is associated with an expression that can evaluate to a predetermined value. Each expression is essentially a defined condition that describes some aspect of a user's interaction with a document. As a user interacts with a document, the expressions, or at least portions of the expressions, are evaluated to ascertain whether they evaluate to the predetermined value. When one or more of the expressions evaluates to the predetermined value, the context block that is associated with that expression is displayed for the user.

[0083] FIG. 8 is a flow diagram that describes steps in a method in accordance with the described embodiment. The described method can be implemented in any suitable hardware, software, firmware or combination thereof. In the illustrated example, the method is implemented in software.

[0084] Step 800 associates a context-sensitive UI with a visibility expression. An exemplary context-sensitive UI is a context block as described above. In the described example, a table is used for the association and includes two columns, one of which is associated with a particular context block, the other of which is associated with the context-block's visibility expression. FIG. 9 shows an exemplary table 900 with columns 902 and 904. Column 902 contains entries associated with each context block, while column 904 contains so-called visibility expressions that are associated with each of the context blocks. In the illustrated example, two exemplary context blocks are shown in column 902 with their corresponding visibility expressions in column 904. For example, for the “Font Format” context block the visibility expression is “em & ts”. The visibility expression is a Boolean expression that describes a condition in which the application is in “edit mode” (i.e. “em”) with a portion of text having been selected (i.e. “ts”). For the “Table Commands” context block, the visibility expression is “em & ip=t+tbs” which translates to a condition in which the application is in edit mode and an insertion point lies within a table (i.e. “ip=t”), or a table has been selected (i.e. “tbs”).

[0085] Step 802 determines whether a visibility expression has changed in value because of a user's action. A user's action can typically change their context. A user's context could be based upon any type of variable such as user selection, insertion point, time of day, user's name, to name just a few. If the value of a visibility expression has changed, then step 804 removes visible UIs (i.e. context blocks) that are not applicable to the current context. Step 806 displays UIs that previously were not visible but are applicable to the user's current context.

[0086] The visibility expressions can be evaluated in any suitable fashion. For example, each time the user takes an action within a document, all of the expressions in table 900 can be evaluated. A more desirable approach is as follows:

[0087] Each of the expressions is represented in a data structure known as a “tree”. FIG. 10 shows exemplary tree structures for the two illustrated visibility expressions of FIG. 9. Here, the top node of each tree comprises an operation. In the present case, the operation happens to be an “AND” operation for each expression. Each top node has one or more children nodes that can either be operands or operations. In the case of the font format context block expression, each of the children nodes 1002, 1004 is an operand (i.e. “edit mode” and “text selected” respectively). For the table commands context block expression, child node 1008 is an operand (i.e. “edit mode”) and child node 1010 is an operation (i.e. an “OR” operation). In turn, node 1010 has two operand nodes 1012, 1014 (i.e. “insertion point =table”, and “table selected” respectively).

[0088] Each tree structure can evaluate to either “TRUE” or “FALSE”. If the tree structure evaluates to “TRUE”, then its corresponding context block is displayed. If the tree structure evaluates to “FALSE”, or remains in a false state after some of the nodes have been evaluated, the context block is not displayed. The expression value of a tree, however, cannot change unless the value of its operands changes. For example, consider the font format tree structure. Assume that its current value is “FALSE” (indicated by the “F” adjacent node 1000). Assume also that its edit mode operand 1002 has a value of “TRUE” and its text selected operand 1004 has a value of “FALSE”. In this case, the user is currently in edit mode but has not selected any text. In order for this tree structure to change in value, the value of its text selected operand 1004 must change from “FALSE” to “TRUE”. This will only happen when a user has selected some text with their cursor. In accordance with the described embodiment, when the value of a child node changes, it generates a notification to its parent node that its value has changed. The parent node expression is then re-evaluated to ascertain whether its value has changed. If its value has changed, then if it has a parent node, it generates a notification that is sent to its parent node. This continues until either a parent node's expression does not change in value, or the top parent node's expression changes in value. If the latter is the case, a corresponding context block is either displayed or removed. If the former is the case, then a current state is maintained (i.e. if the context block was previously displayed, then it is still displayed; and if the context block was not previously displayed, then it is not displayed). Thus, in many cases, only a portion of the visibility expression will need to be evaluated.

[0089] As another example, consider the visibility expression for the table commands context block. Assume that the current state of the expression is as indicated in the table below:

[0090]


	Node	Value

	AND	FALSE
	Em	TRUE
	OR	FALSE
	ip = t	FALSE
	tab sel	FALSE

[0091] In this example, the table commands context block is not being displayed because the top node 1006 has evaluated to “FALSE”. The user is in edit mode and neither the insertion point is in a table nor has a table been selected. Assume now that the user selects a table with their cursor. In this case, the value associated with node 1014 is changed to “TRUE”. Because this node changed in value, it generates a notification and sends the notification to its parent node 1010. Node 1010 is an OR expression whose value now re-evaluates to “TRUE”. Because this node has changed in value, it generates a notification and sends the notification to its parent node 1006. Node 1006 is an AND expression that now evaluates to “TRUE”. Since this is the top node and it now evaluates to “TRUE”, the context block with which it is associated is now displayed for the user. This logically follows from the user's actions. That is, in order to change the value of node 1014, the user had to select a table. When the user selects the table, the table commands context block should automatically be displayed for the user. If and when the user “unselects” the table, the value associated with node 1014 will change and this change will be propagated up the tree in the form of notifications until the top node 1006 is re-evaluated to “FALSE” and the context block is removed.

[0092] FIG. 11 is a flow diagram that describes steps in an exemplary expression-evaluation method in accordance with the above-described embodiment. The described method can be implemented in any suitable hardware, software, firmware, or combination thereof. In the illustrated example, the method is implemented in software.

[0093] Step 1100 represents each expression as a tree structure having multiple nodes. Exemplary expressions and tree structures are shown and described in connection with FIGS. 9 and 10. Step 1102 gets the first tree or tree structure and step 1104 gets the first leaf node on the tree. In the FIG. 10 example, exemplary leaf nodes are shown at 1002, 1004 for the font format tree, and 1008, 1012, and 1014 for the table commands tree. Step 1106 evaluates the node. Step 1108 determines whether the node value has changed. If the node value has not changed, then step 1110 determines whether there are more nodes on the tree, and if so, step 1112 gets the next node and returns to step 1106. If there are no more nodes on the tree, step 1114 determines whether there are more trees. If there are additional trees, step 1116 gets the next tree and returns to step 1104 to evaluate the nodes of the tree. If there are no additional trees, then step 1114 returns to step 1102. Note, that the return of step 1114 can take place automatically to repeat the above process, or the return can be effected by a user's context change.

[0094] If, at step 1108, the node value has changed, step 1118 determines whether this node is the root node of the tree. If the node is the root node, then the method branches to step 1126 to ascertain whether the value of the node is “TRUE” or “FALSE”. If the value is “FALSE, then step 1128 hides the context block that is associated with that particular visibility expression. If, on the other hand, the value is “TRUE”, then step 1130 displays the context block that is associated with that particular visibility expression. If, at step 1118, the node is not the root node, step 1120 gets the parent node of that particular node and step 1122 evaluates the parent node. If the node value changes (step 1124), then the method branches back to step 1118. If, on the other hand, the node value does not change, then the method branches to step 1110.

[0095] The above-described process is advantageous in that many times the complete expressions that are associated with the context blocks need not be evaluated. Many times, only portions of the expressions need to be evaluated. If a particular portion of the expression has changed in value, then additional portions of the expression can be evaluated. If particular portions of the expression have not changed in value, then it is possible to terminate the expression-evaluation process thereby saving processing overhead.

[0096] Note that a small delay function can be built into the system so that the expression evaluation process is not initiated immediately when a user takes a particular action. For example, the system might be programmed so that the expression evaluation process is not initiated until a user has left their cursor in a particular location for a definable amount of time. Such delay mechanisms will be understood by those of skill in the art and are not discussed in detail any further.

Single Navigable Window Application

[0097] In accordance with one implementation, the context-sensitive context blocks and context panes can be employed in connection with a single application program having multiple different functionalities to which a user can navigate and accomplish multiple different tasks. As the user navigates to the different functionalities, their context inevitably changes. As their context changes, so too do the context blocks and context panes that are displayed for the user. An exemplary single application program with multiple different functionalities is described in the U.S. Patent Application entitled “Single Window Navigation Methods and Systems”, incorporated by reference above.

[0098] In the exemplary single application program that is subject of the reference incorporated above, software provides a user interface (UI) that presents a user with a single navigable window that can be navigated from functionality to functionality by a user. The individual functionalities are desirably provided by a single application program the result of which is a highly integrated software product.

[0099] A user, through the use of various navigation instrumentalities can navigate between the functionalities and when doing so, the single window ensures that only one functionality is presented to a user at a time. In this described embodiment, one navigation instrumentality is provided in the form of a web browser-like navigation tool. The choice of a web browser-like navigation tool follows from concerns that navigation instrumentalities be of a type that is readily understood by most individuals familiar with computing environments. Thus, when a user first encounters the inventive navigable single window concept for the first time, they do not have to learn an unfamiliar navigation concept. Another navigation instrumentality includes links to each of the multiple different functionalities. These links can be clicked on by a user and the single navigable window is automatically navigated to the selected functionality.

[0100] FIG. 12 shows but one exemplary user interface (UI) 1200 in accordance with one described embodiment. It will be appreciated that other UIs could be used to implement the inventive concepts described herein and that the illustrated UI constitutes but one way of doing so. In the illustrated example, UI 1200 includes a navigation bar 1202, one or more command areas 1204, and a display or document area 1206 that constitutes the single navigable window.

[0101] Navigation bar 1202 is located adjacent the top of display area 1206 and contains browser-like navigation buttons 1208 in the form of a “back” button, a “forward” button, a “stop” button and the like. The navigation bar can be located anywhere on the UI. Its illustrated placement, however, is similar in appearance to the placement of traditional web browsing navigation features. In addition to the navigation buttons 1208, the navigation bar 1202 also includes links 1210 to the different functionalities that can be accessed by the user. In the illustrated example, links to three exemplary functionalities (i.e. functionality 1, functionality 2, and functionality 3) are shown. These functionalities are typically different functionalities that can enable a user to complete different respective tasks. Examples of different tasks are given below in more detail. These functionalities are all provided within the context of a single application. To access a particular functionality, a user simply clicks on one of the links and a window that pertains to the selected functionality is immediately presented in the display area 1206.

[0102] Command areas 1204 are located adjacent the top and left side of the display area 1206. The command area(s) can, however, be located in any suitable location. The command areas provide commands that are both global in nature and specific to the particular context the user has selected. For example, some commands such as “search” and “help” might be considered as global in nature since they can find use in many contexts. Other commands, such as “text bold” or “reply to all” are more specific to the particular context that the user has selected. For the “text bold” command, the user's context may likely be a word processing context, while the “reply to all” command may likely be employed in an email context.

EXAMPLE

[0103] As an example of the single navigable window provided by a single application consider FIGS. 13 and 14.

[0104] In this example, the multiple functionalities 1210 that can be navigated by a user include a browser functionality (indicated by the home icon), a mail functionality (indicated by the letter icon), a planner functionality (indicated by the clock icon), a contacts functionality (indicated by the people icon), a documents functionality (indicated by the folder icon), and a links functionality (indicated by the world icon). These functionalities are so-called “document-centric” functionalities because they all relate in some way to a document that a user interacts with, e.g. a Web page document, an email document, a calendar document, etc.

[0105] FIG. 13 shows an example of a display that is rendered in the display area 1206 when a user clicks on the link to the browser functionality. By clicking on the link (i.e. the home icon) to the browser functionality, single application program software executing on the user's computer executes to implement a browser functionality. In this example, the browser functionality displays the user's home page in display area 1206. Notice also that navigation buttons 1208 are provided for navigation between the different selectable functionalities. The command areas 1204 contain context blocks designated as “Favorites” and “Browsing” that include command sets with commands that are specific to the context that the user has selected. In this example, the user's context is a browsing context. Accordingly, the leftmost command area contains commands that are specific to the browsing functionality. Such commands include ones that a user would normally expect to find in a web browser. Notice also that the command area 1204 adjacent the top of display area 1206 also contains commands that are specific to the browsing context, i.e. “Add to Favorites” and an address well in which the user can type a URL of a particular destination web site. Thus, context blocks that are displayable in the leftmost command area are automatically presented to the user as the user's context changes.

[0106] FIG. 14 shows an example of a display that is rendered in the display area 1206 when the user clicks on the link to the mail functionality (i.e. the folder icon). By clicking on this link, single application program software executing on the user's computer executes to implement the mail functionality. In this example, the mail functionality displays a user's inbox with messages that have been received by the user. Notice that the leftmost command area has been minimized by the user and that command area 1204 adjacent the top of the display area 1206 contains commands that are specific to the user's current context, e.g. “New” for generating a new email message, “Reply” for replying to an email message, “Reply to All” for replying to all recipients of an email message and the like. When the user's context within this functionality changes in a way that requires one or more context blocks to be displayed, the context blocks will be automatically displayed in the leftmost command area. For example, a user may author an email message and desire to italicize a portion of text. Upon selecting a portion of text, a text formatting context block will automatically appear for the user to use. As another example, assume that a user incorporates a table into their email message, if they then move the cursor inside of the table, the table formatting context block will automatically appear in the leftmost command area.

[0107] Although not specifically illustrated, the user could have displays for the planner, contacts, documents, and links functionalities presented in the display area 1206 by simply clicking on the links to these specific functionalities. When so displayed, context blocks that are associated with the user's context in these particular functionalities will be automatically displayed in accordance with the user's particular context. The navigation bar 1208 provides the user with the ability to navigate through these different functionalities in a browser-like manner.

[0108] It is important to note that the above example constitutes but one exemplary way in which multiple different functionalities and context blocks can be presented to a user within the construct of a navigable structure. It should be understood that the specifically illustrated functionalities (i.e. browser, mail, planner etc.) constitute specific examples of different functionalities that are capable of being incorporated into the single application program that provides the navigable window. Accordingly, other different functionalities can be employed. This aspect is discussed in more detail in the section entitled “Extensible Functionalities” below. It should also be noted that various context panes are associated with the individual context blocks that form the basis of this example. The context panes have not specifically been described in this example because they were explained above.

[0109] FIG. 15 is a flow diagram that describes steps in a method in accordance with the described embodiment. The illustrated method can be implemented in any suitable hardware, software, firmware, or combination thereof. In the illustrated example, the method is implemented in software.

[0110] Step 1500 provides a single application program with multiple different functionalities. The functionalities, as pointed out above, are advantageously different so as to enable a user to accomplish different tasks. One specific non-limiting example of different functionalities was given above in the context of document-centric functionalities that enable a user to make use of browser, mail, planner, contacts, documents, and links functionalities. Step 1500 can be implemented by configuring a computing device, such as a user's computer, with the single application program having the multiple different functionalities. This step can also be implemented by providing a software platform in the form of a generic single application shell that is extensible and adaptable to receive different extensions or software modules that embody various different functionalities, as described in various patent applications incorporated by reference above. These different extensions are then presented to the user in the context of the single application having the multiple different functionalities.

[0111] These extensions can be delivered to the platform in any suitable way and through any suitable delivery mechanism. For example, one way of delivering the various extensions or functionalities is to deliver them via a network such as an Intranet or the Internet. Regardless of the manner in which the single application is provided, step 1502 presents a user interface (UI) with a single window and links to the multiple different functionalities. The UI can also advantageously include navigation instrumentalities that enable a user to navigate between the different functionalities in a browser-like manner. FIGS. 13-14 give specific examples of an exemplary UI that can be used in accordance with the described embodiment. Step 1504 ascertains whether a user has selected a particular link to a functionality or whether the user has used one of the navigation instrumentalities to navigate to a particular functionality. If a user has not done either, the method branches back to step 1502. If, on the other hand, a user has selected a particular link or used a navigation tool to navigate to a particular functionality, step 1506 presents a functionality-specific display within the single window. That is, the single navigable window is navigated by the software to the selected functionality. Specific examples of this were given above in connection with FIGS. 13 and 14 in which browsing and mail functionalities were respectively displayed within display area 1206. In connection with presenting the functionality-specific display in step 1506, step 1508 can present functionality-specific commands in a command area of the UI. This is advantageously done automatically as a user navigates from functionality to functionality. That is, as a user changes functionalities, command sets that are specific to the user's current context or functionality are automatically displayed in the command area. In connection with this step, context blocks can be automatically displayed as described above. It will also be appreciated that step 1508 includes the step of presenting various context panes in response to the user selecting them as described above. Step 1508 then branches back to step 1504 to ascertain whether the user has navigated to another functionality.

Context Block and Context Pane Persistence

[0112] In the multi-functionality application scenario, context blocks or context panes can be provided that are not specifically associated with a specific document. Rather, these context blocks and context panes remain open regardless of the document, until the user explicitly closes them. Such context blocks and panes are referred to herein as “Application-level context blocks” and “Application-level context panes”.

[0113] Application-Level Context Blocks and Application-Level Context Panes

[0114] Application-level context blocks are context blocks that are not removed from the UI, even when the user navigates to another document. So, instead of being associated with a particular document, they are associated with a state of the application as a whole. Application-level context panes are similar: they are context panes that stay open even when the user navigates to another document.

[0115] As an example, consider a user that desires to use a “search” function. If the user opens the search function, a context pane corresponding to the search function will populate the context UI container. The search context pane is specific to the user's particular functionality. Thus, if the user has navigated to their email inbox, the search context pane will enable them to search their inbox. If the user has navigated to a particular document, the search context pane will enable them to search that document. As long as the search context pane is not closed by the user it will navigate with them from functionality to functionality and enable them to specifically conduct searches with the individual functionalities.

[0116] Application-Level Context Panes and Stacking

[0117] Application-level context panes are implemented with special behavioral characteristics with regards to the stacking of context panes. In this example, there are two types of context panes: those with affinity to a particular document, and those with no affinity to any document. A stack of context panes that have been opened is maintained. The stack is ordered so that the most recent pane is on the top of the stack. This stack does not contain any panes that have been explicitly closed by the user. The first pane in the stack that meets one of the following two criteria is displayed: (1) the pane has affinity to the current document, and (2) the pane has no affinity to any document. If no pane in the stack meets these criteria, then the context blocks are displayed. Note that this has the effect of hiding any pane that does not have affinity to the current document. This means that when navigation occurs, panes with affinity to the previous document are suppressed. Panes with affinity to the new document and those with no affinity to any document become candidates for display. They are considered as candidates because only the pane closest to the top of the stack is actually displayed.

CONCLUSION

[0118] The embodiments described above provide methods and systems that automatically present a user with commands that are specific to a task in which the user happens to be engaged. Advantageously, as the user's context changes within an application, the commands that are presented automatically change as well. In various implementations, the user can be given the opportunity to select additional context-sensitive commands for display. Overall, the methods and systems advantageously enable a user to take advantage of many different commands without requiring the user to know much about the application that they are using. In one particular implementation, a single application comprises multiple functionalities that enable a user to accomplish different tasks. These multiple functionalities are presented in the context of a single window that is navigable by a user between the different functionalities. Advantageously, navigation instrumentalities are provided that are, in some instances, browser-like in appearance and allow the user to navigate between the application-provided functionalities in a browser-like manner. Functionality-specific commands can be automatically presented to the user when they navigate to a particular functionality. The functionality-specific commands are presented, in the illustrated example, in the form of context blocks and content panes as described above. One aspect of the single navigable window application is that the application can serve as a basis for an extensible platform that can be configured with different functionalities. Software modules incorporating the different functionalities, as well as appropriate command sets that are displayable in the context blocks and panes, can be desirably included in the software modules. When the modules are plugged into the platform, a set of extensible functions is provided. Each of the extensible functions can have their own set of unique context blocks and panes that can be automatically displayed in a manner that is defined by the software developer of the module.

[0119] Although the invention has been described in language specific to structural features and/or methodological steps, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific features or steps described. Rather, the specific features and steps are disclosed as preferred forms of implementing the claimed invention.

Claims

The invention claimed is:

1. A method of exposing commands in a document-centric application program executed by a computer, the method comprising:

automatically displaying, by the computer, a window on a display device, the window generated by the document-centric application program, the document-centric application program operating at the computer, the window containing a work area and a controls area, the work area containing a document, the controls area not initially containing a context block;

storing, by the computer, Hyper-Text Markup Language (HTML) code that specifies a title of the context block and a set of commands of the context block, the set of commands executable by the document-centric application program, the title identifying a task, the set of commands useful to a user in accomplishing the task;

storing a tree data structure, the tree data structure stored at the computer, the tree data structure comprising an overall set of nodes, each node in the overall set of nodes being an independent data structure, the overall set of nodes including a root node and a set of child nodes, each node in the set of child nodes being a child of one other node in the overall set of nodes, the overall set of nodes comprising a set of leaf nodes and a set of non-leaf nodes, no node in the overall set of nodes being a child of any node in the set of leaf nodes, each node in the set of non-leaf nodes having at least one child node in the overall set of nodes, the root node not being a child of any node in the overall set of nodes, each node in the overall set of nodes associated with a value, each node in the overall set of nodes associated with a Boolean expression, the Boolean expressions associated with each of node in the set of non-leaf nodes taking as operands the values associated with each child node of the node, the set of leaf nodes including a first leaf node and a second leaf node;

ascertaining, at the computer, whether a change has occurred to a position of a cursor, the cursor being controlled by a user, the cursor being within the document, the document being worked on by the user;

ascertaining, at the computer, whether a change has occurred to selected text portions of the document, the selected text portions of the document being portions of the document selected by the user using the cursor;

in response to ascertaining that the change has occurred to the position of the cursor, making, at the computer, a change to the value associated with the first leaf node;

in response to ascertaining that the change has occurred to the selected text portions of the document, making, by the computer, a change to the value associated with the second leaf node;

in response to a change to the value associated with any non-root node, using, at the computer, the Boolean expression associated with a parent node to make a determination whether to change a value associated with the parent node, the non-root node being in the set of child nodes, the parent node being a parent of the non-root node;

in response to making a determination to change the value associated with the parent node, changing, at the computer, the value associated with the parent node;

in response to determining that the value associated with the root node has changed from the second value to the first value, automatically causing, at the computer, the user interface not to contain the context block.

2. The method of claim 1, wherein said at least one command is displayed in a modeless fashion in which the user is able to continue to work within the document while said at least one command is displayed.

3. The method of claim 1 further comprising after automatically causing the user interface to contain the context block, executing the at least one command without requiring any action from the user other than selecting the at least one command.

4. The method of claim 1, wherein said tree data structure pertains to a task the user is attempting to accomplish.

5. The method of claim 1,

wherein said set of leaf nodes includes a third leaf node, the value associated with the third leaf node dependent on one or more of the following: a type of the document and a state of the document.

6. The method of claim 1, wherein causing the user interface to contain the context block comprises causing, by the computer, the user interface to contain the context block independent of the user selecting any displayed menu item.

7. One or more computer-readable storage media having computer-readable instructions thereon which, when executed by a computer, cause the computer to:

storing, by the computer at one or more computer-readable storage media, Hyper-Text Markup Language (HTML) code that specifies a title of the context block and a set of commands of the context block, the set of commands executable by the document-centric application program, the title identifying a task, the set of commands useful to a user in accomplishing the task;

store a tree data structure at the computer, the tree data structure comprising an overall set of nodes, each node in the overall set of nodes being an independent data structure, the overall set of nodes including a root node and a set of child nodes, each node in the set of child nodes being a child of one other node in the overall set of nodes, the overall set of nodes comprising a set of leaf nodes and a set of non-leaf nodes, no node in the overall set of nodes being a child of any node in the set of leaf nodes, each node in the set of non-leaf nodes having at least one child node in the overall set of nodes, the root node not being a child of any node in the overall set of nodes, each node in the overall set of nodes associated with a value, each node in the overall set of nodes associated with a Boolean expression, the Boolean expressions associated with each of node in the set of non-leaf nodes taking as operands the values associated with each child node of the node, the set of leaf nodes including a first leaf node;

ascertain whether a change has occurred to selected text portions of the document, the selected text portions of the document being portions of the document selected using a cursor, the cursor being controlled by a user, the document being a document in which the user is working;

in response to ascertaining that the change has occurred to the selected text portions of the document, make a change to the value associated with the first leaf node;

in response to a change to the value associated with any non-root node, use the Boolean expression associated with a parent node to make a determination whether to change a value associated with the parent node, the non-root node being in the set of child nodes, the parent node being a parent of the non-root node;

in response to making a determination to change the value associated with the parent node, change the value associated with the parent node;

in response to determining that the value associated with the root node has changed from a first value to a second value, automatically cause the controls area of the user interface to contain the context block, the context block containing the title of the context block and the set of commands of the context block, the context block not obscuring the document, at least one command in the set of commands of the context block being displayed in a modeless fashion in which the user is able to continue to work within the document while said at least one command is displayed, and wherein said at least one command in the set of commands of the context block is selectable by the user to perform an action on the selected text portions of the document; and

in response to determining that the value associated with the root node has changed from the second value to the first value, automatically cause the user interface not to contain the context block.

8. The computer-readable storage media of claim 7,

wherein the set of leaf nodes includes a second leaf node; and

wherein the instructions further cause the computer to:

ascertain whether a change has occurred to a position of the cursor; and

in response to making ascertaining that the change has occurred to the position of the cursor, making a change to the value associated with the second leaf node.

9. A method of exposing commands in a document-centric application program executed by a computer, the method comprising:

storing, by the computer, Hyper-Text Markup Language (HTML) code that specifies a title of the context block and a set of commands of the context block, the set of command executable by the document-centric application program, the title identifying a task, the set of commands useful to a user in accomplishing the task;

storing a tree data structure at the computer, the tree data structure comprising an overall set of nodes, each node in the overall set of nodes being an independent data structure, the overall set of nodes including a root node and a set of child nodes, each node in the set of child nodes being a child of one other node in the overall set of nodes, the overall set of nodes comprising a set of leaf nodes and a set of non-leaf nodes, no node in the overall set of nodes being a child of any node in the set of leaf nodes, each node in the set of non-leaf nodes having at least one child node in the overall set of nodes, the root node not being a child of any node in the overall set of nodes, each node in the overall set of nodes associated with a value, each node in the overall set of nodes associated with a Boolean expression, the Boolean expressions associated with each of node in the set of non-leaf nodes taking as operands the values associated with each child node of the node, the set of leaf nodes including a first leaf node;

in response to ascertaining that the change has occurred to the selected text portions of the document, making, at the computer, a change to the value associated with the first leaf node;

in response to making a determination to change the value associated with the parent node, changing, at the computer, the value associated with the parent node;

in response to determining that the value associated with the root node has changed from a first value to a second value, automatically causing, at the computer, the controls area of the user interface to contain the context block, the context block containing the title of the context block and the set of commands of the context block, the computer causing the user interface to contain the context block independent of the user selecting any displayed menu item, the context block not obscuring the document, each command in the set of commands of the context block being selectable by the user, at least one command in the set of commands of the context block being selectable by the user to perform an action on the selected text portions of the document;

10. The method of claim 9, wherein each value associated with each node in the overall set of nodes is a Boolean value.

11. The method of claim 9,

wherein the set of leaf nodes includes a second leaf node, the value associated with the second leaf node being based on one or more of the following: a type of the document, a state of the document, and objects within the document that are selectable by the user.

12. The method of claim 9, wherein automatically causing the user interface to contain the context block comprises causing the context block to contain a title bar area, the title bar area containing the title of the context block.

13. The method of claim 12, wherein the title bar area is configured to enable the context block to be toggled between expanded and collapsed states.

14. The method of claim 12, wherein the title bar area comprises a menu display button, the menu display button being configured to enable a menu, the menu associated with the context block.

15. The method of claim 14, wherein the menu contains links to one or more context panes, each of the context panes comprising additional context-sensitive commands, each of the context panes being modeless.

16. The method of claim 9, wherein the context block includes a command area that exposes the set of commands of the context block to the user.

17. The method of claim 16, wherein a command display within the command area is defined in Hypertext Markup Language (HTML).

18. The method of claim 9, wherein automatically causing the user interface to contain the context block comprises displaying said context block in a modeless fashion.

19. A method of exposing commands in a document-centric application program executed by a computer, the method comprising:

automatically displaying, by the computer, a window on a display device, the window generated by the document-centric application program, the window containing a work area and a controls area, the work area containing a document, the controls area not initially containing a context block;

storing a tree data structure at the computer, the tree data structure comprising an overall set of nodes, each node in the overall set of nodes being an independent data structure, the overall set of nodes including a root node and a set of child nodes, each node in the set of child nodes being a child of one other node in the overall set of nodes, the overall set of nodes comprising a set of leaf nodes and a set of non-leaf nodes, no node in the overall set of nodes being a child of any node in the set of leaf nodes, each node in the set of non-leaf nodes having at least one child node in the overall set of nodes, the root node not being a child of any node in the overall set of nodes, each node in the overall set of nodes associated with a value, each node in the overall set of nodes associated with a Boolean expression, the Boolean expression associated with each node in the set of non-leaf nodes taking as operands the values associated with each child node of the node, the set of leaf nodes including a first leaf node;

automatically ascertaining, at the computer, whether a change has occurred to selected text portions of the document, the selected text portions of the document being portions of the document selected by the user using a cursor the cursor being controlled by a user, where the document is a document the user is working in;

in response to ascertaining that the change has occurred to the selected text portions of the document, making, at the computer, a change to the value associated with the first leaf node;

in response to a change to the value associated with any non-root node, using, at the computer, a Boolean expression associated with a parent node to make a determination whether to change a value associated with the parent node, the Boolean expression associated with the parent node taking as operands the values associated with each child node of the parent node, the non-root node being in the set of child nodes, the parent node being a parent of the non-root node;

in response to making a determination to change the value associated with the parent node, changing, at the computer, the value associated with the parent node;

in response to determining that the value associated with the root node has changed from the second value to the first value, automatically causing, at the computer, the controls area not to contain the context block; and

while the controls area contains the context block, enabling, with the computer, the user to select and apply various commands in the set of commands of the context block to the document multiple times.

20. The method of claim 19 further comprising applying, by the computer, one or more selected commands when selected by the user, without further user interaction, the selected commands being in the set of commands of the context block.

21. The method of claim 19, wherein automatically causing the controls area to contain the context block comprises causing, at the computer, the controls area to display the context block responsive to the user selecting a menu item, the menu item being in a menu, the menu supported by the context block.

22. The method of claim 19, wherein causing the controls area to contain the context block comprises displaying, by the computer, the context block in a modeless manner.

23. The method of claim 19, wherein automatically causing the controls area to contain the context block comprises displaying, by the computer, the context block within a context pane, the context pane having a title bar and a controls area, the title bar of the context pane labeling the context pane, the controls area of the context pane including the set of commands.

24. The method of claim 23, wherein the context pane is not collapsible.

25. The method of claim 23, wherein the context pane must be closed by the user.

26. The method of claim 23, wherein the user must request the context pane to be displayed.

27. The method of claim 23, wherein some commands in the set of commands are disabled.

28. The method of claim 23, wherein the context pane includes a context-sensitive help feature, the context-sensitive help feature displaying help information, the help information contextually related to the context pane.

29. The method of claim 28, wherein the context-sensitive help feature is accessible via an icon on the title bar.

30. The method of claim 28, wherein the context-sensitive help feature is displayed in a modeless manner.

31. The method of claim 23, wherein multiple context panes are stackable in a queue.

32. One or more computer-readable storage media having computer-readable instructions thereon which, when executed by a computer, cause the computer to perform the method of claim 19.

33. An electronic computing system comprising:

one or more processing units;

a display device; and

a system memory storing:

Hyper-Text Markup Language (HTML) code that specifies a title of a context block and a set of commands of the context block, the set of commands executable by the document-centric application program, the title identifying a task, the set of commands useful to a user in accomplishing the task;

a tree data structure, the tree data structure comprising an overall set of nodes, each node in the overall set of nodes being an independent data structure, the overall set of nodes including a root node and a set of child nodes, each node in the set of child nodes being a child of one other node in the overall set of nodes, the overall set of nodes comprising a set of leaf nodes and a set of non-leaf nodes, no node in the overall set of nodes being a child of any node in the set of leaf nodes, each node in the set of non-leaf nodes having at least one child node in the overall set of nodes, the root node not being a child of any node in the overall set of nodes, each node in the overall set of nodes being associated with a Boolean value, each node in the overall set of nodes being associated with a Boolean expression, the Boolean expression associated with each of node in the set of non-leaf nodes taking as operands the Boolean values associated with each child node of the node, the set of leaf nodes including a first leaf node, a second leaf node and a third leaf node; and

a single document-centric application program, the single document-centric application program being configured to:

cause the display device to display a single navigable window, the single navigable window containing a work area, the work area containing a document that a user is working in;

provide a plurality of functionalities, the user being able to navigate the single navigable window to each functionality in the plurality of functionalities;

cause the single navigable window to contain at least one context-sensitive command area, the context-sensitive command area not obscuring the document, the context-sensitive command area not initially containing the context block,

ascertain whether a change has occurred to a position of a cursor, the cursor being controlled by the user, the cursor being within the document;

ascertain whether a change has occurred to selected text portions of the document, the selected text portions of the document being portions of the document selected by the user using the cursor;

in response to ascertaining that the change has occurred to the position of the cursor, make a change to the Boolean value associated with the first leaf node;

in response to ascertaining that the change has occurred to the selected text portions of the document, make a change to the Boolean value associated with the second leaf node;

change the Boolean value associated with the third leaf node when the user changes between functionalities in the plurality of functionalities;

in response to a change to the Boolean value associated with any non-root node, use the Boolean expression associated with a parent node to make a determination whether to change a Boolean value associated with the parent node, the non-root node being in the set of child nodes, the parent node being a parent of the non-root node;

in response to making a determination to change the Boolean value associated with the parent node, change the Boolean value associated with the parent node;

in response to determining that the Boolean value associated with the root node has changed from a first value to a second value, automatically cause the context-sensitive command area to contain the context block, the context block containing the title of the context block and the set of commands of the context block, at least one command in the set of commands being selectable by the user to perform an action on the selected text portions of the document; and

in response to determining that the Boolean value associated with the root node has changed from the second value to the first value, automatically cause the context-sensitive command area not to contain the context block.

34. The computing system of claim 33, wherein the single document-centric application program is configured to cause the single navigable window to contain navigation instrumentalities, the navigation instrumentalities being configured for use by the user to navigate the single navigable window to different functionalities in the plurality of functionalities.

35. The computing system of claim 34, wherein one of the navigation instrumentalities comprises links, each of the links being associated with a functionality in the plurality of functionalities.

36. The computing system of claim 34, wherein one of the navigation instrumentalities comprises browser-like navigation buttons, the browser-like navigation buttons being usable by the user to navigate the single navigable window between different functionalities in the plurality of functionalities.

37. The computing system of claim 33, wherein each functionality in the plurality of functionalities comprises document-centric functionalities.

38. An electronic computing system comprising:

a processing unit;

a display device; and

a system memory storing:

a tree data structure, the tree data structure comprising an overall set of nodes, each node in the overall set of nodes being an independent data structure, the overall set of nodes including a root node and a set of child nodes, each node in the set of child nodes being a child of one other node in the overall set of nodes, the overall set of nodes comprising a set of leaf nodes and a set of non-leaf nodes, no node in the overall set of nodes being a child of any node in the set of leaf nodes, each node in the set of non-leaf nodes having at least one child node in the overall set of nodes, the root node not being a child of any node in the overall set of nodes, each node in the overall set of nodes being associated with a value, each node in the overall set of nodes being associated with a Boolean expression, the Boolean expressions associated with each of node in the set of non-leaf nodes taking as operands the values associated with each child node of the node, the set of leaf nodes including a first leaf node;

a single document-centric application program, the single document-centric application, when executed at the processing unit, cause the processing unit to:

display, on the display device, a single navigable window, a user being able to use the single navigable window in navigating between multiple different functionalities provided by the single document-centric application program;

display a document in a work area of the single navigable window;

display at least one context-sensitive command area in the single navigable window, the context-sensitive command area not obscuring the document, the context-sensitive command area not initially containing the context block;

in response to ascertaining that the change has occurred to the selected text portions of the document, make a change to the value associated with the first leaf node;

in response to making a determination to change the value associated with the parent node, change the value associated with the parent node;

in response to determining that the value associated with the root node has changed from a first value to a second value, automatically cause the context-sensitive command area to contain the context block, the context block containing the title of the context block and the set of commands of the context block, at least one command in the set of commands being selectable by the user to perform an action on the selected text portions of the document; and

in response to determining that the value associated with the root node has changed from the second value to the first value, automatically cause the context-sensitive command area not to contain said context block.

39. The computing system of claim 38, wherein the single document-centric application program is configured to cause the processing unit to provide navigation instrumentalities associated with the single navigable window, the navigation instrumentalities being configured for use by the user to navigate the single navigable window to the different functionalities.

40. The computing system of claim 39, wherein one of the navigation instrumentalities comprises links associated with each of the multiple different functionalities to which the single navigable window can be navigated.

41. The computing system of claim 39, wherein one of the navigation instrumentalities comprises browser-like navigation buttons that can be used to navigate the single navigable window between the different functionalities.

42. A computing method comprising:

storing, by the computer, at one or more computer-readable storage media, Hyper-Text Markup Language (HTML) code that a title of a context block and a set of commands of the context block, the set of commands executable by a document-centric application program, the title identifying a task, the set of commands useful to a user in accomplishing the task;

storing a tree data structure, the tree data structure being stored at a computer, the tree data structure comprising an overall set of nodes, each node in the overall set of nodes being an independent data structure, the overall set of nodes including a root node and a set of child nodes, each node in the set of child nodes being a child of one other node in the overall set of nodes, the overall set of nodes comprising a set of leaf nodes and a set of non-leaf nodes, no node in the overall set of nodes being a child of any node in the set of leaf nodes, each node in the set of non-leaf nodes having at least one child node in the overall set of nodes, the root node not being a child of any node in the overall set of nodes, each node in the overall set of nodes being associated with a Boolean value, each node in the overall set of nodes being associated with a Boolean expression, the Boolean expressions associated with each of node in the set of non-leaf nodes taking as operands the Boolean values associated with each child node of the node, the set of leaf nodes including a first leaf node and a second leaf node;

displaying, on a display device, a user interface, the user interface comprising a single navigable window capable of being navigated between multiple different functionalities provided by the single document-centric application program, the single navigable window containing a word area and a controls area, the work area containing a document, the controls area not initially containing a context block;

receiving, at the computer, user input that indicates selection of a particular one of the functionalities;

responsive to receiving said user input, navigating, at the computer, the single navigable window to the particular one of the functionalities and displaying in said single navigable window indicia of said particular one of the functionalities, said particular one of the functionalities enabling a user to accomplish a task associated with the particular one of the functionalities;

in response to receiving said user input, changing, at the computer, the Boolean value associated with the first leaf node;

in response to ascertaining that the change has occurred to the selected text portions of the document, making, at the computer, a change to the Boolean value associated with the second leaf node;

in response to a change to the Boolean value associated with any non-root node, using, at the computer, the Boolean expression associated with a parent node to make a determination whether to change the Boolean value associated with the parent node, the non-root node being in the set of child nodes, the parent node being a parent of the non-root node;

in response to making a determination to change the Boolean value associated with the parent node, changing, at the computer, the value associated with the parent node; and

in response to determining that the Boolean value associated with the root node has changed from a first value to a second value, automatically displaying, by the computer on the display device, the context block in the controls area, the context block containing the title of the context block and the set of commands of the context block, the context block not obscuring the document, the computer displaying the context block independent of the user selecting any displayed menu item, at least one command in the set of commands selectable by the user to perform an action on the selected text portions of the document; and

in response to determining that the value associated with the root node has changed from the second value to the first value, automatically causing, by the computer, the user interface not to contain the context block.

43. A method of exposing commands in a document-centric application program, the method comprising:

storing, at a system memory, a table containing a plurality of entries, each entry in the plurality of entries specifying a context block in a plurality of context blocks and a visibility expression in a plurality of visibility expressions, each visibility expression in the plurality of visibility expressions represented as a tree data structure in a plurality of tree data structures, each tree data structure in the plurality of tree data structures comprising an overall set of nodes, each node in the overall set of nodes being an independent data structure, the overall set of nodes including a root node and a set of child nodes, each node in the set of child nodes being a child of one other node in the overall set of nodes, the overall set of nodes comprising a set of leaf nodes and a set of non-leaf nodes, no node in the overall set of nodes being a child of any node in the set of leaf nodes, each node in the set of non-leaf nodes having at least one child node in the overall set of nodes, the root node not being a child of any node in the overall set of nodes, each node in the overall set of nodes associated with a Boolean value, each node in the overall set of nodes associated with a Boolean expression, the Boolean expression associated with each node in the set of non-leaf nodes taking as operands the Boolean values associated with each child node of the node,

storing, at the system memory. Hyper-Text Markup Language (HTML) code that specifies a title of each context block in the plurality of context blocks and a set of commands of each context block in the plurality of context blocks. the sets of commands of the context blocks executable by the document-centric application program, the titles of the context blocks identifying individual tasks in a plurality of tasks, the sets of commands of the context blocks useful to a user in accomplishing the tasks identified by the titles of the context blocks,

wherein at least one tree data structure in the plurality of tree data structures includes a leaf node associated with a Boolean expression dependent on a selected text portion of a document, the selected text portion of the document being a portion of the document selected by a user of a computer;

display, by the computer, a single navigable window containing a document area and a command area, the command area not initially containing a context block in the plurality of context blocks, the document area containing the document, wherein the user is working on the document;

evaluating, at the computer, each tree data structure in the plurality of tree data structures by repeatedly:

selecting, at the computer, a current tree data structure in the plurality of tree data structures; and

after selecting the current tree data structure, evaluating, at the computer, each leaf node in the set of leaf nodes of the current tree data structure, wherein evaluating one of the leaf nodes of the current tree data structure comprises:

selecting, at the computer, an unevaluated leaf node in the set of leaf nodes of the current tree data structure as a current node;

after selecting the unevaluated leaf node as the current node, evaluating, at the computer, the Boolean expression associated with the current node;

after evaluating the Boolean expression associated with the current node, determining, at the computer, whether the Boolean value associated with the current node has changed;

(a) in response to determining that the Boolean value associated with the current node has changed, determining, at the computer, whether the current node is the root node of the current tree data structure;

(b) in response to determining that the current node is not the root node of the current tree data structure, setting, at the computer, a parent of the current node as the current node;

(c) after setting the parent of the current node as the current node, evaluating, at the computer, the Boolean expression associated with the current node;

(d) after evaluating the Boolean expression associated with the current node, determining, at the computer, whether the Boolean value associated with the current node has changed;

(e) in response to determining that the Boolean value associated with the current node has not changed, completing, at the computer, evaluation of the unevaluated leaf node;

(f) in response to determining that the Boolean value associated with the current node has changed, performing, at the computer, steps (a)-(f) again;

in response to determining that the current node is the root node of the current tree data structure, determining, at the computer, whether the Boolean value associated with the current node is changed and is a first Boolean value;

in response to determining that the Boolean value associated with the current node is changed and is the first Boolean value, automatically displaying, by the computer on the display device, a given context block in the plurality of context blocks, the given context block displayed in the command area, the given context block containing the title of the given context block and the set of commands of the given context block, the table containing an entry specifying the given context block and the visibility expression represented by the current tree data structure, the given context block containing at least one command selectable by the user to perform an action on the document; and

in response to determining that the Boolean value associated with the current node is changed and is not the first Boolean value, hiding, by the computer, the given context block from the command area.

Patent Citations (660)

Patent	Date	Inventor	Cited By
US4201978(A)	1980-05-01	Nally	Applicant
US4498147(A)	1985-02-01	Agnew et al.	Applicant
US4514800(A)	1985-04-01	Gruner et al.	Applicant
US4564752(A)	1986-01-01	Lepic et al.	Applicant
US4641274(A)	1987-02-01	Swank	Applicant
US4674040(A)	1987-06-01	Barker et al.	Applicant
US4723211(A)	1988-02-01	Barker et al.	Applicant
US4739477(A)	1988-04-01	Barker et al.	Applicant
US4815029(A)	1989-03-01	Barker et al.	Applicant
US4847749(A)	1989-07-01	Collins et al.	Applicant
US4910663(A)	1990-03-01	Bailey	Applicant
US4933880(A)	1990-06-01	Borgendale et al.	Applicant
US4962475(A)	1990-10-01	Hernandez et al.	Applicant
US5025484(A)	1991-06-01	Yamanari et al.	Applicant
US5072412(A)	1991-12-01	Henderson, Jr. et al.	Applicant
US5179703(A)	1993-01-01	Evans	Applicant
US5182709(A)	1993-01-01	Makus	Applicant
US5187786(A)	1993-02-01	Densmore et al.	Applicant
US5191645(A)	1993-03-01	Carlucci et al.	Applicant
US5195183(A)	1993-03-01	Miller et al.	Applicant
US5204947(A)	1993-04-01	Bernstein et al.	Applicant
US5206951(A)	1993-04-01	Khoyi et al.	Applicant
US5218672(A)	1993-06-01	Morgan et al.	Applicant
US5222160(A)	1993-06-01	Sakai et al.	Applicant
US5228100(A)	1993-07-01	Takeda et al.	Applicant
US5237680(A)	1993-08-01	Adams et al.	Applicant
US5249275(A)	1993-09-01	Srivastava	Applicant
US5274803(A)	1993-12-01	Dubin et al.	Applicant
US5297249(A)	1994-03-01	Bernstein et al.	Applicant
US5297283(A)	1994-03-01	Kelly, Jr. et al.	Applicant
US5313631(A)	1994-05-01	Kao	Applicant
US5313646(A)	1994-05-01	Hendricks et al.	Applicant
US5317686(A)	1994-05-01	Salas et al.	Applicant
US5333317(A)	1994-07-01	Dann	Applicant
US5339423(A)	1994-08-01	Beitel et al.	Applicant
US5339424(A)	1994-08-01	Fushim	Applicant
US5341478(A)	1994-08-01	Travis, Jr. et al.	Applicant
US5369766(A)	1994-11-01	Nakano et al.	Applicant
US5369778(A)	1994-11-01	San Soucie et al.	Applicant
US5371675(A)	1994-12-01	Greif et al.	Applicant
US5377323(A)	1994-12-01	Vasudevan	Applicant
US5379419(A)	1995-01-01	Heffernan et al.	Applicant
US5381547(A)	1995-01-01	Flug et al.	Applicant
US5390325(A)	1995-02-01	Miller	Applicant
US5396623(A)	1995-03-01	McCall et al.	Applicant
US5408665(A)	1995-04-01	Fitzgerald	Applicant
US5410646(A)	1995-04-01	Tondevold et al.	Applicant
US5410688(A)	1995-04-01	Williams et al.	Applicant
US5412772(A)	1995-05-01	Monson	Applicant
US5434975(A)	1995-07-01	Allen	Applicant
US5436637(A)	1995-07-01	Gayraud et al.	Examiner
US5438659(A)	1995-08-01	Notess et al.	Applicant
US5440744(A)	1995-08-01	Jacobson et al.	Applicant
US5446842(A)	1995-08-01	Schaeffer et al.	Applicant
US5455875(A)	1995-10-01	Chevion et al.	Applicant
US5459865(A)	1995-10-01	Heninger et al.	Applicant
US5481722(A)	1996-01-01	Skinner	Applicant
US5497489(A)	1996-03-01	Menne	Applicant
US5504898(A)	1996-04-01	Klein	Applicant
US5517655(A)	1996-05-01	Collins et al.	Applicant
US5535389(A)	1996-07-01	Elder et al.	Applicant
US5542070(A)	1996-07-01	LeBlanc et al.	Applicant
US5550976(A)	1996-08-01	Henderson et al.	Applicant
US5551035(A)	1996-08-01	Arnold et al.	Applicant
US5555325(A)	1996-09-01	Burger	Applicant
US5566330(A)	1996-10-01	Sheffield	Applicant
US5572643(A)	1996-11-01	Judson	Applicant
US5572648(A)	1996-11-01	Bibayan	Examiner
US5577252(A)	1996-11-01	Nelson et al.	Applicant
US5581686(A)	1996-12-01	Koppolu et al.	Applicant
US5581760(A)	1996-12-01	Atkinson et al.	Applicant
US5600789(A)	1997-02-01	Parker et al.	Applicant
US5602996(A)	1997-02-01	Powers et al.	Examiner
US5608720(A)	1997-03-01	Biegel et al.	Applicant
US5625783(A)	1997-04-01	Ezekiel et al.	Applicant
US5627979(A)	1997-05-01	Chang et al.	Applicant
US5630126(A)	1997-05-01	Redpath	Applicant
US5634121(A)	1997-05-01	Tracz et al.	Applicant
US5634124(A)	1997-05-01	Khoyi et al.	Applicant
US5640544(A)	1997-06-01	Onodera et al.	Applicant
US5644738(A)	1997-07-01	Goldman et al.	Applicant
US5649099(A)	1997-07-01	Theimer et al.	Applicant
US5659729(A)	1997-08-01	Nielsen	Applicant
US5664178(A)	1997-09-01	Sinofsky	Applicant
US5668966(A)	1997-09-01	Ono et al.	Examiner
US5669005(A)	1997-09-01	Curbow et al.	Applicant
US5682536(A)	1997-10-01	Atkinson et al.	Applicant
US5689667(A)	1997-11-01	Kurtenbach	Applicant
US5689703(A)	1997-11-01	Atkinson et al.	Applicant
US5704029(A)	1997-12-01	Wright, Jr.	Applicant
US5706501(A)	1998-01-01	Horikiri et al.	Applicant
US5717939(A)	1998-02-01	Bricklin et al.	Applicant
US5721824(A)	1998-02-01	Taylor	Applicant
US5740439(A)	1998-04-01	Atkinson et al.	Applicant
US5742504(A)	1998-04-01	Meyer et al.	Examiner
US5745683(A)	1998-04-01	Lee et al.	Applicant
US5745712(A)	1998-04-01	Turpin et al.	Applicant
US5748807(A)	1998-05-01	Lopresti et al.	Applicant
US5758184(A)	1998-05-01	Lucovsky et al.	Applicant
US5758358(A)	1998-05-01	Ebbo	Applicant
US5761408(A)	1998-06-01	Kolawa et al.	Applicant
US5761683(A)	1998-06-01	Logan et al.	Applicant
US5764984(A)	1998-06-01	Loucks	Applicant
US5764985(A)	1998-06-01	Smale	Applicant
US5778372(A)	1998-07-01	Cordell et al.	Applicant
US5778402(A)	1998-07-01	Gipson	Applicant
US5784555(A)	1998-07-01	Stone	Applicant
US5790796(A)	1998-08-01	Sadowsky	Applicant
US5798757(A)	1998-08-01	Smith	Examiner
US5801701(A)	1998-09-01	Koppolu et al.	Applicant
US5802304(A)	1998-09-01	Stone	Applicant
US5806079(A)	1998-09-01	Rivette et al.	Applicant
US5815830(A)	1998-09-01	Anthony	Applicant
US5826265(A)	1998-10-01	Van Huben et al.	Applicant
US5835777(A)	1998-11-01	Staelin	Applicant
US5838906(A)	1998-11-01	Doyle et al.	Applicant
US5842018(A)	1998-11-01	Atkinson et al.	Applicant
US5845077(A)	1998-12-01	Fawcett	Applicant
US5845090(A)	1998-12-01	Collins, III et al.	Applicant
US5854630(A)	1998-12-01	Nielsen	Applicant
US5859973(A)	1999-01-01	Carpenter et al.	Applicant
US5862372(A)	1999-01-01	Morris et al.	Applicant
US5862379(A)	1999-01-01	Rubin et al.	Applicant
US5864819(A)	1999-01-01	DeArmas et al.	Applicant
US5907704(A)	1999-05-01	Gudmundson et al.	Applicant
US5910895(A)	1999-06-01	Proskauer et al.	Applicant
US5911776(A)	1999-06-01	Guck	Applicant
US5915112(A)	1999-06-01	Boutcher	Applicant
US5922072(A)	1999-07-01	Hutchinson et al.	Applicant
US5928363(A)	1999-07-01	Ruvolo	Applicant
US5929858(A)	1999-07-01	Shibata et al.	Applicant
US5940075(A)	1999-08-01	Mutschler, III et al.	Applicant
US5950010(A)	1999-09-01	Hesse et al.	Applicant
US5956481(A)	1999-09-01	Walsh et al.	Applicant
US5960199(A)	1999-09-01	Brodsky et al.	Applicant
US5963964(A)	1999-10-01	Nielsen	Applicant
US5973696(A)	1999-10-01	Agranat et al.	Applicant
US5974454(A)	1999-10-01	Apfel et al.	Applicant
US5982370(A)	1999-11-01	Kamper	Applicant
US5983348(A)	1999-11-01	Ji	Applicant
US5987480(A)	1999-11-01	Donohue et al.	Applicant
US5991710(A)	1999-11-01	Papineni et al.	Applicant
US5991731(A)	1999-11-01	Colon et al.	Applicant
US5991877(A)	1999-11-01	Luckenbaugh	Applicant
US5995103(A)	1999-11-01	Ashe	Applicant
US5999740(A)	1999-12-01	Rowley	Applicant
US6005570(A)	1999-12-01	Gayraud et al.	Applicant
US6014135(A)	2000-01-01	Fernandes	Applicant
US6016520(A)	2000-01-01	Facq et al.	Applicant
US6018743(A)	2000-01-01	Xu	Applicant
US6026379(A)	2000-02-01	Haller et al.	Applicant
US6026416(A)	2000-02-01	Kanerva et al.	Applicant
US6031989(A)	2000-02-01	Cordell	Applicant
US6035297(A)	2000-03-01	Van Huben et al.	Applicant
US6035309(A)	2000-03-01	Dauerer et al.	Applicant
US6044205(A)	2000-03-01	Reed et al.	Applicant
US6052531(A)	2000-04-01	Waldin et al.	Applicant
US6054987(A)	2000-04-01	Richardson	Examiner
US6072870(A)	2000-06-01	Nguyen et al.	Applicant
US6078326(A)	2000-06-01	Kilmer et al.	Applicant
US6078327(A)	2000-06-01	Liman et al.	Applicant
US6078924(A)	2000-06-01	Ainsbury et al.	Applicant
US6081610(A)	2000-06-01	Dwork et al.	Applicant
US6084585(A)	2000-07-01	Kraft et al.	Applicant
US6088708(A)	2000-07-01	Burch et al.	Applicant
US6091417(A)	2000-07-01	Lefkowitz	Applicant
US6094657(A)	2000-07-01	Hailpern et al.	Applicant
US6097382(A)	2000-08-01	Rosen et al.	Applicant
US6098081(A)	2000-08-01	Heidorn et al.	Applicant
US6108637(A)	2000-08-01	Blumenau	Applicant
US6108783(A)	2000-08-01	Krawcyzk et al.	Applicant
US6115646(A)	2000-09-01	Fiszman et al.	Applicant
US6121965(A)	2000-09-01	Kenney et al.	Applicant
US6122647(A)	2000-09-01	Horowitz et al.	Applicant
US6144969(A)	2000-11-01	Inokuchi et al.	Applicant
US6151624(A)	2000-11-01	Teare et al.	Applicant
US6154128(A)	2000-11-01	Wookey et al.	Applicant
US6163772(A)	2000-12-01	Kramer et al.	Applicant
US6167521(A)	2000-12-01	Smith et al.	Applicant
US6167523(A)	2000-12-01	Strong	Applicant
US6182094(B1)	2001-01-01	Humpleman et al.	Applicant
US6182095(B1)	2001-01-01	Leymaster et al.	Applicant
US6188401(B1)	2001-02-01	Peyer	Applicant
US6191797(B1)	2001-02-01	Politis	Examiner
US6192367(B1)	2001-02-01	Hawley et al.	Applicant
US6195661(B1)	2001-02-01	Filepp et al.	Applicant
US6199204(B1)	2001-03-01	Donohue	Applicant
US6209128(B1)	2001-03-01	Gerard et al.	Applicant
US6216152(B1)	2001-04-01	Wong et al.	Applicant
US6219698(B1)	2001-04-01	Iannucci et al.	Applicant
US6225996(B1)	2001-05-01	Gibb et al.	Applicant
US6235027(B1)	2001-05-01	Herzon	Applicant
US6253366(B1)	2001-06-01	Mutschler, III	Applicant
US6253374(B1)	2001-06-01	Dresevic et al.	Applicant
US6263313(B1)	2001-07-01	Milsted et al.	Applicant
US6266810(B1)	2001-07-01	Tanaka et al.	Applicant
US6268852(B1)	2001-07-01	Lindhorst et al.	Applicant
US6272506(B1)	2001-08-01	Bell	Applicant
US6275227(B1)	2001-08-01	DeStefano	Applicant
US6275599(B1)	2001-08-01	Adler et al.	Applicant
US6279042(B1)	2001-08-01	Ouchi	Applicant
US6281896(B1)	2001-08-01	Alimpich et al.	Applicant
US6282711(B1)	2001-08-01	Halpern et al.	Applicant
US6286033(B1)	2001-09-01	Kishinsky et al.	Applicant
US6292897(B1)	2001-09-01	Gennaro et al.	Applicant
US6297819(B1)	2001-10-01	Furst	Applicant
US6300948(B1)	2001-10-01	Geller et al.	Applicant
US6307955(B1)	2001-10-01	Zank et al.	Applicant
US6308273(B1)	2001-10-01	Goertzel et al.	Applicant
US6311271(B1)	2001-10-01	Gennaro et al.	Applicant
US6314415(B1)	2001-11-01	Mukherjee	Applicant
US6321259(B1)	2001-11-01	Ouellette et al.	Applicant
US6321334(B1)	2001-11-01	Jerger et al.	Applicant
US6327628(B1)	2001-12-01	Anuff et al.	Applicant
US6331864(B1)	2001-12-01	Coco et al.	Applicant
US6342907(B1)	2002-01-01	Petty et al.	Applicant
US6343149(B1)	2002-01-01	Motoiwa	Applicant
US6343302(B1)	2002-01-01	Graham	Applicant
US6345256(B1)	2002-02-01	Milsted et al.	Applicant
US6345278(B1)	2002-02-01	Hitchcock et al.	Applicant
US6345361(B1)	2002-02-01	Jerger et al.	Applicant
US6349408(B1)	2002-02-01	Smith	Applicant
US6351574(B1)	2002-02-01	Yair et al.	Applicant
US6353851(B1)	2002-03-01	Anupam et al.	Applicant
US6353926(B1)	2002-03-01	Parthesarathy et al.	Applicant
US6356906(B1)	2002-03-01	Lippert et al.	Applicant
US6357038(B1)	2002-03-01	Scouten	Examiner
US6366907(B1)	2002-04-01	Fanning et al.	Applicant
US6366912(B1)	2002-04-01	Wallent et al.	Applicant
US6367013(B1)	2002-04-01	Bisbee et al.	Applicant
US6369840(B1)	2002-04-01	Barnett et al.	Applicant
US6369841(B1)	2002-04-01	Salomon et al.	Applicant
US6374402(B1)	2002-04-01	Schmeidler et al.	Applicant
US6381742(B2)	2002-04-01	Forbes et al.	Applicant
US6381743(B1)	2002-04-01	Mutschler, III	Applicant
US6389434(B1)	2002-05-01	Rivette et al.	Applicant
US6393456(B1)	2002-05-01	Ambler et al.	Applicant
US6396488(B1)	2002-05-01	Simmons et al.	Applicant
US6405221(B1)	2002-06-01	Levine et al.	Applicant
US6408311(B1)	2002-06-01	Baisley et al.	Applicant
US6414700(B1)	2002-07-01	Kurtenbach et al.	Applicant
US6421070(B1)	2002-07-01	Ramos et al.	Applicant
US6421656(B1)	2002-07-01	Cheng et al.	Applicant
US6425125(B1)	2002-07-01	Fries et al.	Applicant
US6429885(B1)	2002-08-01	Saib et al.	Applicant
US6434563(B1)	2002-08-01	Pasquali et al.	Applicant
US6434564(B2)	2002-08-01	Ebert	Applicant
US6442563(B1)	2002-08-01	Bacon et al.	Applicant
US6442583(B1)	2002-08-01	Eilert et al.	Applicant
US6442755(B1)	2002-08-01	Lemmons et al.	Applicant
US6446110(B1)	2002-09-01	Lection et al.	Applicant
US6449617(B1)	2002-09-01	Quinn et al.	Applicant
US6457009(B1)	2002-09-01	Bollay	Applicant
US6463419(B1)	2002-10-01	Kluss	Applicant
US6470349(B1)	2002-10-01	Heninger et al.	Applicant
US6473800(B1)	2002-10-01	Jerger et al.	Applicant
US6476828(B1)	2002-11-01	Burkett et al.	Applicant
US6476833(B1)	2002-11-01	Moshfeghi	Applicant
US6477544(B1)	2002-11-01	Bolosky et al.	Applicant
US6480860(B1)	2002-11-01	Monday	Applicant
US6487566(B1)	2002-11-01	Sundaresan	Applicant
US6490601(B1)	2002-12-01	Markus et al.	Applicant
US6493006(B1)	2002-12-01	Gourdol et al.	Examiner
US6493702(B1)	2002-12-01	Adar et al.	Applicant
US6501864(B1)	2002-12-01	Eguchi et al.	Applicant
US6502101(B1)	2002-12-01	Verprauskus et al.	Applicant
US6502103(B1)	2002-12-01	Frey et al.	Applicant
US6505230(B1)	2003-01-01	Mohan et al.	Examiner
US6505300(B2)	2003-01-01	Chan et al.	Applicant
US6507856(B1)	2003-01-01	Chen et al.	Applicant
US6516322(B1)	2003-02-01	Meredith	Applicant
US6519617(B1)	2003-02-01	Wanderski et al.	Applicant
USRE38070(E)	2003-04-01	Spies et al.	Applicant
US6546546(B1)	2003-04-01	Van Doom	Applicant
US6549221(B1)	2003-04-01	Brown et al.	Applicant
US6549878(B1)	2003-04-01	Lowry et al.	Applicant
US6549922(B1)	2003-04-01	Srivastava et al.	Applicant
US6553402(B1)	2003-04-01	Makarios et al.	Applicant
US6560616(B1)	2003-05-01	Garber	Applicant
US6560620(B1)	2003-05-01	Ching	Applicant
US6560640(B2)	2003-05-01	Smethers	Applicant
US6563514(B1)	2003-05-01	Samar	Examiner
US6571253(B1)	2003-05-01	Thompson et al.	Applicant
US6578144(B1)	2003-06-01	Gennaro et al.	Applicant
US6581061(B2)	2003-06-01	Graham	Applicant
US6584469(B1)	2003-06-01	Chiang et al.	Applicant
US6584548(B1)	2003-06-01	Bourne et al.	Applicant
US6585778(B1)	2003-07-01	Hind et al.	Applicant
US6589290(B1)	2003-07-01	Maxwell et al.	Applicant
US6594686(B1)	2003-07-01	Edwards et al.	Applicant
US6598219(B1)	2003-07-01	Lau	Applicant
US6603489(B1)	2003-08-01	Edlund et al.	Applicant
US6604099(B1)	2003-08-01	Chung et al.	Applicant
US6609200(B2)	2003-08-01	Anderson et al.	Applicant
US6611840(B1)	2003-08-01	Baer et al.	Examiner
US6611843(B1)	2003-08-01	Jacobs	Applicant
US6613098(B1)	2003-09-01	Sorge et al.	Applicant
US6615276(B1)	2003-09-01	Mastrianni et al.	Applicant
US6629109(B1)	2003-09-01	Koshisaka	Applicant
US6631357(B1)	2003-10-01	Perkowski	Applicant
US6631379(B2)	2003-10-01	Cox	Applicant
US6631497(B1)	2003-10-01	Jamshidi et al.	Applicant
US6631519(B1)	2003-10-01	Nicholson et al.	Applicant
US6632251(B1)	2003-10-01	Rutten et al.	Applicant
US6635089(B1)	2003-10-01	Burkett et al.	Applicant
US6636845(B2)	2003-10-01	Chau et al.	Applicant
US6643633(B2)	2003-11-01	Chau et al.	Applicant
US6643652(B2)	2003-11-01	Helgeson et al.	Applicant
US6643684(B1)	2003-11-01	Malkin et al.	Applicant
US6651217(B1)	2003-11-01	Kennedy et al.	Applicant
US6654737(B1)	2003-11-01	Nunez	Applicant
US6654932(B1)	2003-11-01	Bahrs et al.	Applicant
US6658417(B1)	2003-12-01	Stakutis et al.	Applicant
US6658622(B1)	2003-12-01	Aiken et al.	Applicant
US6661920(B1)	2003-12-01	Skinner	Applicant
US6668369(B1)	2003-12-01	Krebs et al.	Applicant
US6671805(B1)	2003-12-01	Brown et al.	Applicant
US6675202(B1)	2004-01-01	Perttunen	Examiner
US6678717(B1)	2004-01-01	Schneider	Applicant
US6681370(B2)	2004-01-01	Gounares et al.	Applicant
US6691230(B1)	2004-02-01	Bardon	Applicant
US6691281(B1)	2004-02-01	Sorge et al.	Applicant
US6697944(B1)	2004-02-01	Jones et al.	Applicant
US6701434(B1)	2004-03-01	Rohatgi	Applicant
US6701486(B1)	2004-03-01	Weber et al.	Applicant
US6704906(B1)	2004-03-01	Yankovich et al.	Applicant
US6711679(B1)	2004-03-01	Guski et al.	Applicant
US6720985(B1)	2004-04-01	Silverbrook et al.	Applicant
US6725426(B1)	2004-04-01	Pavlov	Applicant
US6728755(B1)	2004-04-01	de Ment	Applicant
US6735721(B1)	2004-05-01	Morrow et al.	Applicant
US6745367(B1)	2004-06-01	Bates et al.	Applicant
US6748385(B1)	2004-06-01	Rodkin et al.	Applicant
US6751777(B2)	2004-06-01	Bates et al.	Applicant
US6754874(B1)	2004-06-01	Richman	Applicant
US6757826(B1)	2004-06-01	Paltenghe	Applicant
US6757868(B1)	2004-06-01	Glaser et al.	Applicant
US6760723(B2)	2004-07-01	Oshinsky et al.	Applicant
US6763343(B1)	2004-07-01	Brooke et al.	Applicant
US6772139(B1)	2004-08-01	Smith, III	Applicant
US6772165(B2)	2004-08-01	O'Carroll	Applicant
US6774926(B1)	2004-08-01	Ellis et al.	Applicant
US6779154(B1)	2004-08-01	Nussbaum et al.	Applicant
US6781609(B1)	2004-08-01	Barker et al.	Applicant
US6782144(B2)	2004-08-01	Bellavita et al.	Applicant
US6799299(B1)	2004-09-01	Li et al.	Applicant
US6801929(B1)	2004-10-01	Donoho et al.	Examiner
US6816849(B1)	2004-11-01	Halt, Jr.	Applicant
US6845380(B2)	2005-01-01	Su et al.	Applicant
US6845499(B2)	2005-01-01	Srivastava et al.	Applicant
US6847387(B2)	2005-01-01	Roth	Applicant
US6848078(B1)	2005-01-01	Birsan et al.	Applicant
US6871220(B1)	2005-03-01	Rajan et al.	Applicant
US6874130(B1)	2005-03-01	Baweja, et al.	Applicant
US6876996(B2)	2005-04-01	Czajkowski et al.	Applicant
US6889359(B1)	2005-05-01	Conner et al.	Applicant
US6901403(B1)	2005-05-01	Bata et al.	Applicant
US6915454(B1)	2005-07-01	Moore et al.	Applicant
US6931532(B1)	2005-08-01	Davis et al.	Applicant
US6941510(B1)	2005-09-01	Ozzie et al.	Applicant
US6941511(B1)	2005-09-01	Hind et al.	Applicant
US6941521(B2)	2005-09-01	Lin et al.	Applicant
US6948129(B1)	2005-09-01	Loghmani	Applicant
US6948133(B2)	2005-09-01	Haley	Applicant
US6948135(B1)	2005-09-01	Ruthfield et al.	Applicant
US6950980(B1)	2005-09-01	Malcolm	Applicant
US6961897(B1)	2005-11-01	Peel, Jr. et al.	Applicant
US6963875(B2)	2005-11-01	Moore et al.	Applicant
US6968503(B1)	2005-11-01	Chang et al.	Applicant
US6968505(B2)	2005-11-01	Stoll et al.	Applicant
US6993714(B2)	2006-01-01	Kaler et al.	Applicant
US6996776(B1)	2006-02-01	Makely et al.	Applicant
US6996781(B1)	2006-02-01	Myers et al.	Applicant
US7000179(B2)	2006-02-01	Yankovich et al.	Applicant
US7002560(B2)	2006-02-01	Graham	Applicant
US7003722(B2)	2006-02-01	Rothchiller et al.	Applicant
US7010580(B1)	2006-03-01	Fu et al.	Applicant
US7020869(B2)	2006-03-01	Abriari et al.	Applicant
US7024417(B1)	2006-04-01	Russakovsky et al.	Applicant
US7032170(B2)	2006-04-01	Poulose et al.	Applicant
US7036072(B1)	2006-04-01	Sulistio et al.	Applicant
US7039875(B2)	2006-05-01	Khalfay et al.	Applicant
US7051273(B1)	2006-05-01	Holt et al.	Applicant
US7058663(B2)	2006-06-01	Johnston et al.	Applicant
US7062764(B2)	2006-06-01	Cohen et al.	Applicant
US7065493(B1)	2006-06-01	Homsi	Applicant
US7080083(B2)	2006-07-01	Kim	Applicant
US7080325(B2)	2006-07-01	Treibach-Heck et al.	Applicant
US7086009(B2)	2006-08-01	Resnick et al.	Applicant
US7086042(B2)	2006-08-01	Abe et al.	Applicant
US7088374(B2)	2006-08-01	David et al.	Applicant
US7100147(B2)	2006-08-01	Miller et al.	Applicant
US7103611(B2)	2006-09-01	Murthy et al.	Applicant
US7106888(B1)	2006-09-01	Silverbrook et al.	Applicant
US7107282(B1)	2006-09-01	Yalamanchi	Applicant
US7107521(B2)	2006-09-01	Santos	Applicant
US7146564(B2)	2006-12-01	Kim et al.	Applicant
US7152205(B2)	2006-12-01	Day et al.	Applicant
US7168035(B1)	2007-01-01	Bell et al.	Applicant
US7178166(B1)	2007-02-01	Taylor et al.	Applicant
US7190376(B1)	2007-03-01	Tonisson	Applicant
US7191394(B1)	2007-03-01	Ardeleanu et al.	Applicant
US7213200(B2)	2007-05-01	Abe et al.	Applicant
US7236982(B2)	2007-06-01	Zlatanov et al.	Applicant
US7272789(B2)	2007-09-01	O'Brien	Applicant
US7281018(B1)	2007-10-01	Begun et al.	Applicant
US7296017(B2)	2007-11-01	Larcheveque et al.	Applicant
US7313758(B2)	2007-12-01	Kozlov	Applicant
US7316003(B1)	2008-01-01	Dulepet et al.	Applicant
US7318237(B2)	2008-01-01	Moriconi et al.	Applicant
US7334178(B1)	2008-02-01	Stanciu et al.	Applicant
US2001/0007109(A1)	2001-07-01	Lange	Applicant
US2001/0022592(A1)	2001-09-01	Alimpich et al.	Applicant
US2001/0024195(A1)	2001-09-01	Hayakawa	Applicant
US2001/0037345(A1)	2001-11-01	Kiernan	Applicant
US2001/0054004(A1)	2001-12-01	Powers	Applicant
US2001/0056429(A1)	2001-12-01	Moore et al.	Applicant
US2001/0056460(A1)	2001-12-01	Sahota	Applicant
US2002/0010700(A1)	2002-01-01	Wotring	Applicant
US2002/0010743(A1)	2002-01-01	Ryan et al.	Applicant
US2002/0010746(A1)	2002-01-01	Jilk, Jr. et al.	Applicant
US2002/0013788(A1)	2002-01-01	Pennell et al.	Applicant
US2002/0019941(A1)	2002-02-01	Chan et al.	Applicant
US2002/0023113(A1)	2002-02-01	Hsing et al.	Applicant
US2002/0026441(A1)	2002-02-01	Kutay et al.	Applicant
US2002/0026461(A1)	2002-02-01	Kutay et al.	Applicant
US2002/0032590(A1)	2002-03-01	Anand et al.	Applicant
US2002/0032692(A1)	2002-03-01	Suzuki et al.	Applicant
US2002/0032706(A1)	2002-03-01	Perla et al.	Applicant
US2002/0032768(A1)	2002-03-01	Voskuil	Applicant
US2002/0035579(A1)	2002-03-01	Wang et al.	Applicant
US2002/0035581(A1)	2002-03-01	Reynar et al.	Applicant
US2002/0040469(A1)	2002-04-01	Pramberger	Applicant
US2002/0049790(A1)	2002-04-01	Ricker et al.	Applicant
US2002/0054126(A1)	2002-05-01	Gamon	Applicant
US2002/0054128(A1)	2002-05-01	Lau et al.	Applicant
US2002/0057297(A1)	2002-05-01	Grimes et al.	Applicant
US2002/0065798(A1)	2002-05-01	Bostleman et al.	Applicant
US2002/0065847(A1)	2002-05-01	Furukawa et al.	Applicant
US2002/0070973(A1)	2002-06-01	Croley	Applicant
US2002/0078074(A1)	2002-06-01	Cho et al.	Applicant
US2002/0078103(A1)	2002-06-01	Gorman et al.	Applicant
US2002/0083318(A1)	2002-06-01	Larose	Applicant
US2002/0099952(A1)	2002-07-01	Lambert et al.	Applicant
US2002/0100027(A1)	2002-07-01	Binding et al.	Applicant
US2002/0112224(A1)	2002-08-01	Cox	Applicant
US2002/0129056(A1)	2002-09-01	Conant et al.	Applicant
US2002/0133484(A1)	2002-09-01	Chau et al.	Applicant
US2002/0152222(A1)	2002-10-01	Holbrook	Applicant
US2002/0152244(A1)	2002-10-01	Dean et al.	Applicant
US2002/0156772(A1)	2002-10-01	Chau et al.	Applicant
US2002/0156846(A1)	2002-10-01	Rawat et al.	Applicant
US2002/0156929(A1)	2002-10-01	Hekmatpour	Applicant
US2002/0169752(A1)	2002-11-01	Kusama et al.	Applicant
US2002/0169789(A1)	2002-11-01	Kutay et al.	Applicant
US2002/0174147(A1)	2002-11-01	Wang et al.	Applicant
US2002/0174417(A1)	2002-11-01	Sijacic et al.	Applicant
US2002/0178380(A1)	2002-11-01	Wolf et al.	Applicant
US2002/0184219(A1)	2002-12-01	Preisig et al.	Applicant
US2002/0188597(A1)	2002-12-01	Kern et al.	Applicant
US2002/0188613(A1)	2002-12-01	Chakraborty et al.	Applicant
US2002/0194219(A1)	2002-12-01	Bradley et al.	Applicant
US2002/0196281(A1)	2002-12-01	Audleman et al.	Applicant
US2002/0196288(A1)	2002-12-01	Emrani	Applicant
US2002/0198891(A1)	2002-12-01	Li	Applicant
US2002/0198935(A1)	2002-12-01	Crandall, Sr. et al.	Applicant
US2003/0004951(A1)	2003-01-01	Chokshi	Applicant
US2003/0007000(A1)	2003-01-01	Carlson et al.	Applicant
US2003/0014397(A1)	2003-01-01	Chau et al.	Applicant
US2003/0018668(A1)	2003-01-01	Britton et al.	Applicant
US2003/0020746(A1)	2003-01-01	Chen et al.	Applicant
US2003/0023641(A1)	2003-01-01	Gorman et al.	Applicant
US2003/0025732(A1)	2003-02-01	Prichard	Applicant
US2003/0026507(A1)	2003-02-01	Zlotnick	Applicant
US2003/0028550(A1)	2003-02-01	Lee et al.	Applicant
US2003/0033037(A1)	2003-02-01	Yuen et al.	Applicant
US2003/0037303(A1)	2003-02-01	Bodlaender	Applicant
US2003/0043986(A1)	2003-03-01	Creamer	Applicant
US2003/0046665(A1)	2003-03-01	Ilin	Applicant
US2003/0048301(A1)	2003-03-01	Menninger	Applicant
US2003/0051243(A1)	2003-03-01	Lemmons et al.	Applicant
US2003/0055811(A1)	2003-03-01	Stork et al.	Applicant
US2003/0055828(A1)	2003-03-01	Koch et al.	Applicant
US2003/0056198(A1)	2003-03-01	Al-Azzawe	Applicant
US2003/0061386(A1)	2003-03-01	Brown	Applicant
US2003/0061567(A1)	2003-03-01	Brown et al.	Applicant
US2003/0074279(A1)	2003-04-01	Viswanath et al.	Applicant
US2003/0084424(A1)	2003-05-01	Reddy et al.	Applicant
US2003/0093755(A1)	2003-05-01	O'Carroll	Applicant
US2003/0110443(A1)	2003-06-01	Yankovich et al.	Applicant
US2003/0120578(A1)	2003-06-01	Newman	Applicant
US2003/0120651(A1)	2003-06-01	Bernstein et al.	Applicant
US2003/0120659(A1)	2003-06-01	Sridhar	Applicant
US2003/0120671(A1)	2003-06-01	Kim et al.	Applicant
US2003/0120686(A1)	2003-06-01	Kim et al.	Applicant
US2003/0126555(A1)	2003-07-01	Aggarwal et al.	Applicant
US2003/0128196(A1)	2003-07-01	Lapstun et al.	Applicant
US2003/0135825(A1)	2003-07-01	Gertner et al.	Applicant
US2003/0140132(A1)	2003-07-01	Champagne et al.	Applicant
US2003/0158897(A1)	2003-08-01	Ben-Natan	Applicant
US2003/0163285(A1)	2003-08-01	Nakamura et al.	Applicant
US2003/0167277(A1)	2003-09-01	Hejlsberg et al.	Applicant
US2003/0182268(A1)	2003-09-01	Lal	Applicant
US2003/0182327(A1)	2003-09-01	Ramanujam et al.	Applicant
US2003/0187756(A1)	2003-10-01	Klivington et al.	Applicant
US2003/0187930(A1)	2003-10-01	Ghaffar	Applicant
US2003/0188260(A1)	2003-10-01	Jensen et al.	Applicant
US2003/0189593(A1)	2003-10-01	Yarvin	Applicant
US2003/0192008(A1)	2003-10-01	Lee	Applicant
US2003/0200506(A1)	2003-10-01	Abe et al.	Applicant
US2003/0204511(A1)	2003-10-01	Brundage	Applicant
US2003/0204814(A1)	2003-10-01	Elo et al.	Applicant
US2003/0205615(A1)	2003-11-01	Marappan	Applicant
US2003/0212664(A1)	2003-11-01	Breining et al.	Applicant
US2003/0212902(A1)	2003-11-01	van der Made	Applicant
US2003/0217053(A1)	2003-11-01	Bachman et al.	Applicant
US2003/0220930(A1)	2003-11-01	Milleker et al.	Applicant
US2003/0225469(A1)	2003-12-01	DeRemer et al.	Applicant
US2003/0225768(A1)	2003-12-01	Chaudhuri	Applicant
US2003/0225829(A1)	2003-12-01	Pena et al.	Applicant
US2003/0226111(A1)	2003-12-01	Wirts et al.	Applicant
US2003/0226132(A1)	2003-12-01	Tondreau et al.	Applicant
US2003/0233374(A1)	2003-12-01	Spinola et al.	Applicant
US2003/0233644(A1)	2003-12-01	Cohen et al.	Applicant
US2003/0236859(A1)	2003-12-01	Vaschillo et al.	Applicant
US2003/0236903(A1)	2003-12-01	Piotrowski	Applicant
US2003/0237046(A1)	2003-12-01	Parker et al.	Applicant
US2003/0237047(A1)	2003-12-01	Borson	Applicant
US2004/0002939(A1)	2004-01-01	Arora	Applicant
US2004/0003031(A1)	2004-01-01	Brown et al.	Applicant
US2004/0003353(A1)	2004-01-01	Rivera et al.	Applicant
US2004/0003389(A1)	2004-01-01	Reynar et al.	Applicant
US2004/0010752(A1)	2004-01-01	Chan et al.	Applicant
US2004/0024842(A1)	2004-02-01	Witt	Applicant
US2004/0030991(A1)	2004-02-01	Hepworth et al.	Applicant
US2004/0039990(A1)	2004-02-01	Bakar et al.	Applicant
US2004/0039993(A1)	2004-02-01	Kougiouris et al.	Applicant
US2004/0044961(A1)	2004-03-01	Pesenson	Applicant
US2004/0044965(A1)	2004-03-01	Toyama et al.	Applicant
US2004/0054966(A1)	2004-03-01	Busch et al.	Applicant
US2004/0059754(A1)	2004-03-01	Barghout et al.	Applicant
US2004/0073565(A1)	2004-04-01	Kaufman et al.	Applicant
US2004/0073868(A1)	2004-04-01	Easter et al.	Applicant
US2004/0078756(A1)	2004-04-01	Napper et al.	Applicant
US2004/0083426(A1)	2004-04-01	Sahu	Applicant
US2004/0088647(A1)	2004-05-01	Miller et al.	Applicant
US2004/0088652(A1)	2004-05-01	Abe et al.	Applicant
US2004/0093596(A1)	2004-05-01	Koyano	Applicant
US2004/0107367(A1)	2004-06-01	Kisters	Applicant
US2004/0117769(A1)	2004-06-01	Lauzon et al.	Applicant
US2004/0123277(A1)	2004-06-01	Schrader et al.	Applicant
US2004/0146199(A1)	2004-07-01	Berkner et al.	Applicant
US2004/0163041(A1)	2004-08-01	Engel	Applicant
US2004/0172442(A1)	2004-09-01	Ripley	Applicant
US2004/0181711(A1)	2004-09-01	Johnson et al.	Applicant
US2004/0186762(A1)	2004-09-01	Beaven et al.	Applicant
US2004/0189716(A1)	2004-09-01	Paoli et al.	Applicant
US2004/0194035(A1)	2004-09-01	Chakraborty	Applicant
US2004/0205473(A1)	2004-10-01	Fisher et al.	Applicant
US2004/0205525(A1)	2004-10-01	Murren et al.	Applicant
US2004/0205534(A1)	2004-10-01	Koelle	Applicant
US2004/0205571(A1)	2004-10-01	Adler	Applicant
US2004/0205592(A1)	2004-10-01	Huang	Applicant
US2004/0205605(A1)	2004-10-01	Adler et al.	Applicant
US2004/0205653(A1)	2004-10-01	Hadfield et al.	Applicant
US2004/0205671(A1)	2004-10-01	Sukehiro et al.	Applicant
US2004/0210599(A1)	2004-10-01	Friedman et al.	Applicant
US2004/0221238(A1)	2004-11-01	Cifra et al.	Applicant
US2004/0221245(A1)	2004-11-01	Chickles et al.	Applicant
US2004/0237030(A1)	2004-11-01	Malkin	Applicant
US2004/0261019(A1)	2004-12-01	Imamura et al.	Applicant
US2004/0268229(A1)	2004-12-01	Paoli et al.	Applicant
US2004/0268259(A1)	2004-12-01	Rockey et al.	Applicant
US2004/0268260(A1)	2004-12-01	Rockey et al.	Applicant
US2005/0004893(A1)	2005-01-01	Sangroniz	Applicant
US2005/0005248(A1)	2005-01-01	Rockey et al.	Applicant
US2005/0015279(A1)	2005-01-01	Rucker et al.	Applicant
US2005/0015732(A1)	2005-01-01	Vedula et al.	Applicant
US2005/0022115(A1)	2005-01-01	Baumgartner et al.	Applicant
US2005/0027757(A1)	2005-02-01	Kiessig et al.	Applicant
US2005/0033728(A1)	2005-02-01	James	Applicant
US2005/0038711(A1)	2005-02-01	Marlelo	Applicant
US2005/0055627(A1)	2005-03-01	Lloyd et al.	Applicant
US2005/0060324(A1)	2005-03-01	Johnson et al.	Applicant
US2005/0060721(A1)	2005-03-01	Choudhary et al.	Applicant
US2005/0065933(A1)	2005-03-01	Goering	Applicant
US2005/0065936(A1)	2005-03-01	Goering	Applicant
US2005/0066287(A1)	2005-03-01	Tattrie et al.	Applicant
US2005/0071752(A1)	2005-03-01	Marlatt	Applicant
US2005/0076049(A1)	2005-04-01	Qubti et al.	Applicant
US2005/0091285(A1)	2005-04-01	Krishnan et al.	Applicant
US2005/0091305(A1)	2005-04-01	Lange et al.	Applicant
US2005/0102370(A1)	2005-05-01	Lin et al.	Applicant
US2005/0102612(A1)	2005-05-01	Allan et al.	Applicant
US2005/0108104(A1)	2005-05-01	Woo	Applicant
US2005/0108624(A1)	2005-05-01	Carrier	Applicant
US2005/0114757(A1)	2005-05-01	Sahota et al.	Applicant
US2005/0132196(A1)	2005-06-01	Dietl	Applicant
US2005/0138086(A1)	2005-06-01	Pecht-Seibert	Applicant
US2005/0138539(A1)	2005-06-01	Bravery et al.	Applicant
US2005/0171746(A1)	2005-08-01	Thalhammer-Reyero	Applicant
US2005/0198086(A1)	2005-09-01	Moore et al.	Applicant
US2005/0198125(A1)	2005-09-01	Beck et al.	Applicant
US2005/0198247(A1)	2005-09-01	Perry et al.	Applicant
US2005/0223063(A1)	2005-10-01	Chang et al.	Applicant
US2005/0223320(A1)	2005-10-01	Brintzenhofe et al.	Applicant
US2005/0240876(A1)	2005-10-01	Myers et al.	Applicant
US2005/0246304(A1)	2005-11-01	Knight et al.	Applicant
US2005/0268222(A1)	2005-12-01	Cheng	Applicant
US2006/0020586(A1)	2006-01-01	Prompt et al.	Applicant
US2006/0026534(A1)	2006-02-01	Ruthfield et al.	Applicant
US2006/0031757(A9)	2006-02-01	Vincent, III	Applicant
US2006/0036995(A1)	2006-02-01	Chickles et al.	Applicant
US2006/0041838(A1)	2006-02-01	Khan	Applicant
US2006/0059434(A1)	2006-03-01	Boss et al.	Applicant
US2006/0069605(A1)	2006-03-01	Hatoun	Applicant
US2006/0069985(A1)	2006-03-01	Friedman et al.	Applicant
US2006/0080657(A1)	2006-04-01	Goodman	Applicant
US2006/0085409(A1)	2006-04-01	Rys et al.	Applicant
US2006/0101037(A1)	2006-05-01	Brill et al.	Applicant
US2006/0101051(A1)	2006-05-01	Carr et al.	Applicant
US2006/0129978(A1)	2006-06-01	Abriani et al.	Applicant
US2006/0143220(A1)	2006-06-01	Spencer	Applicant
US2006/0161559(A1)	2006-07-01	Bordawekar et al.	Applicant
US2006/0200754(A1)	2006-09-01	Kablesh et al.	Applicant
US2007/0036433(A1)	2007-02-01	Teutsch et al.	Applicant
US2007/0050719(A1)	2007-03-01	Lui et al.	Applicant
US2007/0061467(A1)	2007-03-01	Essey et al.	Applicant
US2007/0061706(A1)	2007-03-01	Cupala	Applicant
US2007/0074106(A1)	2007-03-01	Ardeleanu	Applicant
US2007/0094589(A1)	2007-04-01	Paoli	Applicant
US2007/0100877(A1)	2007-05-01	Paoli et al.	Applicant
US2007/0101280(A1)	2007-05-01	Paoli et al.	Applicant
US2007/0118803(A1)	2007-05-01	Walker et al.	Applicant
US2007/0130504(A1)	2007-06-01	Betancourt et al.	Applicant
US2007/0186157(A1)	2007-08-01	Walker et al.	Applicant
US2007/0208606(A1)	2007-09-01	MacKay et al.	Applicant
US2007/0208769(A1)	2007-09-01	Boehm et al.	Applicant
US2008/0028340(A1)	2008-01-01	Davis	Applicant
EP841615(A2)	1998-05-01		Applicant
EP961197(A1)	1999-12-01		Applicant
EP1076290(A2)	2001-02-01		Applicant
EP1221661	2002-07-01		Applicant
JP3191429	1900-01-01		Applicant
JP63085960	1988-04-01		Applicant
JP401173140(A)	1989-07-01		Applicant
JP4225466	1992-08-01		Applicant
JP5314152	1993-11-01		Applicant
JP406014105	1994-01-01		Applicant
JP6139241	1994-05-01		Applicant
JP6180697	1994-06-01		Applicant
JP6180698	1994-06-01		Applicant
JP2000132436	2000-05-01		Applicant
JP2002183652	2002-06-01		Applicant
JP2003173288	2003-06-01		Applicant
WO99/24945	1999-05-01		Applicant
WO99/56207	1999-11-01		Applicant
WO1/44934(A1)	2001-06-01		Applicant
WO157720	2001-08-01		Applicant
WO157720	2006-09-01		Applicant

Non-Patent Literature (144)

Dayton, Linnea and Davis, Jack, Photo Shop 5/5.5 WOW! Book, Nov. 9, 1999, Peachpit Press, 8-17.Examiner
Microsoft Corporation, Microsoft Computer Dictionary, Microsoft Press, Fifth Edition, 149.Examiner
Richard Scott Hall, “Agent-based Software Configuration and Deployment,” Thesis of University of Colorado, Online, Dec. 31, 1999, retrieved from the Internet on Nov. 7, 2003: <http://www.cs.colorado.edu/users/rickhall/documents/ThesisFinal.pdf>, 169 pages.Applicant
Arthur Van Hoff et al., “The Open Software Description Format,” Online, Aug. 13, 1997, retrieved from the Internet on Nov. 7, 2003: <http://www.w3.org/TR/NOTE-OSD>, 11 pages.Applicant
Netscape Communications Corp., “SmartUpdate Developer's Guide,” Online, Mar. 11, 1999, retrieved from the Internet on Dec. 8, 2000: <http://developer.netscape.com:80/docs/manuals/communicator/jarman/index.htm>, 83 pages.Applicant
Sara Williams and Charlie Kindel, “The Component Object Model: A Technical Overview,” Oct. 1994, Microsoft Corp., pp. 1-14.Applicant
Varlamis et al., “Bridging XML-Schema and relational databases. A system for generating and manipulating relational databases using valid XML documents,” DocEng '01, Nov. 9-10, 2001, Copyright 2001, ACM 1-58113-432-0/01/0011, pp. 105-114.Applicant
Hardy et al., “Mapping and Displaying Structural Transformations between XML and PDF,” DocEng '02, Nov. 8-9, 2002, Copyright 2002, ACM 1-58113-594-7/02/0011, pp. 95-102.Applicant
Kim et al., “Immediate and Partial Validation Mechanism for the Conflict Resolution of Update Operations in XML Databases,” WAIM 2002, LNCS 2419, 2002, pp. 387-396, Springer-Verlag Berlin Heidelberg 2002.Applicant
Chuang, T., “Generic Validation of Structural Content with Parametric Modules,” ICFP '01, Sept. 3-5, 2001, Copyright 2001, ACM 1-58113-415-0/01/0009, pp. 98-109.Applicant
Chen et al., “Designing Valid XML Views,” ER 2002, LNCS 2503, 2002, Springer-Verlag Berlin Heidelberg 2002, pp. 463-477.Applicant
Chen et al., “XKvalidator: a Constraint Validator for XML,” CIKM '02, Nov. 4-9, 2002, Copyright 2002, ACM 1-58113-492-4/02/0011, pp. 446-452.Applicant
Rogge et al., “Validating MPEG-21 Encapsulated Functional Metadata,” IEEE 2002, pp. 209-212.Applicant
Nelson, “Validation with MSXML and XML Schema,” Windows Developer Magazine, Jan. 2002. pp. 35-38.Applicant
Chien et al., “XML Document Versioning,” SIGMOD Record, vol. 30, No. 3, Sep. 2001, pp. 46-53.Applicant
Wong et al., “Managing and Querying Multi-Version XML Data with Update Logging,” DocEng '02, Nov. 8-9, 2002, Copyright 2002, ACM 1-58113-594-7/02/0011, pp. 74-81.Applicant
Chien et al., “Efficient schemes for managing multiversionXML documents”, VLDB Journal (2002), pp. 332-353.Applicant
Chien et al., “Efficient Management of Multiversion Documents by Object Referencing,” Proceedings of the 27th VLDB Conference, 2001, pp. 291-300.Applicant
Chien at al., “Storing and Querying Multiversion XML Documents using Durable Node Numbers,” IEEE 2002, pp. 232-241.Applicant
Dyck, T., “XML Spy Tops as XML Editor,” http://www.eweek.com/article2/0,3959,724041,00.asp, Nov. 25, 2002,4 pages.Applicant
Supoj Sutanthavibul et al., “XFIG Version 3.2 Patchlevel 2 (Jul. 2, 1998, Users Manual (Edition 1.0).” Internet Document, [Online] Jul. 2, 1998, XP002229137 Retrieved from the Internet: <URL:http://www.ice.mtu.edu/online—docs/xfig332/> [retrievd on Jan. 28, 2003].Applicant
“Architecture for a Dynamic Information Area Control,” IBM Technical Disclosure Bulletin, IBM Corp. New York, US, vol. 37, No. 10, Jan. 10, 1994, pp. 245-246.Applicant
Irene Au & Shuang Li, “Netscape Communicator's Collapsible Toolbars,” CHI '98, Human Factors in Computing Systems, Conference Proceedings, Los Angeles, CA, Apr. 18-23, 1998, pp. 81-86.Applicant
W. Brogden, “Arbortext Adept 8 Editor Review,” O'Reilly XML.COM, 'Online! Sep. 22, 1999) XP002230080, retrieved from the Internet <URL:http://www.xml.com/pub/a/1999/09/adept/AdeptRvw.htm>, retrieved on Feb. 5, 2003.Applicant
L Alschuler, “A tour of XMetal” O'Reilly XML.COM, 'Online! Jul. 14, 1999, XP002230081, retrieved from the Internet: <URL:http://www.xml.com/pub/a/SeyboldReport/ip031102.html>, retrieved on Feb. 5, 2003.Applicant
A. Davidow, “XML Editors: Allegations of Functionality in search of reality,” INTERNET, 'Online! 1999, XP002230082, retrieved from the Internet, <URL:http://www.ivritype.com/xml/>.Applicant
Steven A. Battle, et al., “Flexible Information Presentation with XML”, 1998, The Institution of Electrical Engineers, 6 pages.Applicant
Paolo Ciancarini, et al., “Managing Complex Documents Over the WWW: A Case Study for XML”, IEEE Transactions on Knowledge and Data Engineering, vol. 11, No. 4, Jul./Aug. 1999, pp. 629-638.Applicant
Hirotaka Kanemoto, et al., “An Efficiently Updatable Index Scheme for Structured Documents”, 1998 IEEE, pp. 991-996.Applicant
Tommie Usdin, et al., “XML: Not a Silver Bullet, But a Great Pipe Wrench”, Standardview vol. 6, No. 3, Sep. 1998, pp. 125-132.Applicant
Netscape Communication Corporation: “Netscape Communicator 4.61 for OS/2 Warp” Software, 1999, The whole software release & “Netscape—Version 4.61 [en]—010615” Netscape Screenshot, Oct. 2, 2002.Applicant
“Netscape window” Netscape Screenshot, Oct. 2, 2002.Applicant
Jan-Henrick Haukeland: “Tsbiff—tildeslash biff—version 1.2.1” Internet Document, [Online] Jun. 1999, URL:http://web.archive.org/web/19990912001527/http://www.tildeslash.com/tsbiff/.Applicant
Clark, James, Ed.; “XSL Transformation (XSLT) Version 1.0”, Nov. 16, 1999, W3C (MIT, INRIA, Keio), pp. 1-156.Applicant
Clark, James and Steve Derose; “XML Path Language (XPath) Version 1.0”, Nov. 16, 1999, W3C (MIT, INRIA, Keio), pp. 1-49.Applicant
Musgrave, S., “Networking technology—impact and opportunities”, Survey and Statistical Computing 1996. Proceedings of the Second ASC International Conference. Sep. 1996. pp. 369-378. London, UK.Applicant
Rapaport, L., “Get more from SharePoint,” Transform Magazine, vol. 11, No. 3, Mar. 2002, pp. 13, 15.Applicant
McCright, J.S., “New Tool Kit to Link Groove with Microsoft SharePoint”, eWeek, Enterprise News & Reviews, Ziff Davis Media Inc., Jul. 29, 2002, 1 page.Applicant
U.S. Appl. No. 60/209,713, filed Jun. 5, 2000.Applicant
U.S. Appl. No. 60/191,662, filed Mar. 24, 2000, Moore et al.Applicant
U.S. Appl. No. 60/203,081, filed May 9, 2000, Ben-Natan.Applicant
“Store and Organize Related Project Files in a Binder,” Getting Results with Microsoft Office, 1990, pp. 109-112.Applicant
Berg A., “Naming and Binding: Monikers,” Inside Ole, 1995, Chapter 9, pp. 431-490.Applicant
Clapp D., “The NeXT Application Kit Part I: Non-Responsive Classes,” The NeXT Bible, 1990. Chapter 16, pp. 275-293.Applicant
DiLascia et al, “Sweeper,” Microsoft Interactive Developer vol. 1, No. 1, 1996, 27 pages.Applicant
Herzner et al., “CDAM—Compound Document Access and Management. An Object-Oriented Approach.” Multimedia Systems Interaction and Applications, 1992, Chapter 3, pp. 17-36.Applicant
Kobayashi et al., “An Update on BTRON-specification OS Development,” IEEE 1991, pp. 132-140.Applicant
Peterson B., “Unix Variants,” Unix Review vol. 10, No. 4, Apr. 1992 pp. 29-31.Applicant
Pike et al., “Plan 9 from Bell Labs,” UKUUG, Summer 1990, 10 pages.Applicant
Staneck, W., “Internal and External Media,” Electronic Publishing Unleashed, 1995, Chapter 22, pp. 510-542.Applicant
Whitehill, “Whitehill Composer” Whitehill Technologies Inc., 2 pages.Applicant
Pike et al., “The Use of Name Spaces in Plan 9,” Operating Systems Review, vol. 27, No. 2, Apr. 1993, pp. 72-76.Applicant
Trupin J., “The Visual Programmer,” Microsoft Systems Journal, Apr. 1996, pp. 103-105.Applicant
Zdonik, S., “Object Management System Concepts,” ACM 1984, pp. 13-19.Applicant
OMG XML Metadata Interchange (XMI) Specification Version 1.2 Jan. 2002.Applicant
Laura Acklen & Read Gilgen, “Using Corel Wordperfect 9”, 251-284, 424-434, 583-586 (1998).Applicant
Bruce Halberg et al, “Using Microsoft Excel 97”, Published 1997, Bestseller Edition, Pertinent pp. 1-9. 18- 25, 85-89, 98-101, 106-113, 124-127, 144-147, 190-201, 209-210, 218-227, 581-590, 632-633, 650-655, 712-714.Applicant
Leblond et al, “PC Magazine Guide to Quattro Pro for Windows”, pp. 9-11, 42-61, Ziff-Davis Press. Copyright 1993 by the LeBlond Group.Applicant
Mansfield, “Excel 97 for Busy People”, Published by Osborne/Mcgraw-Hill 1997 pp. 48-50.Applicant
“Microsoft Visual Basic 5.0 Programmer's Guide 1997”; pp. 578-579: Redmond WA 98052-6399.Applicant
Han et al., WebSplitter: A Unified XML Framework for Multi-Device Collaborative Web Browsing, 2000, ACM Conference on Cimputer Supported Cooperative Work, 10 pages.Applicant
IBM: Stack Algorithm for Extractin Subtree from Serialized Tree, Mar. 1, 1994, TDB-ACC-NONN94033. 3 pages.Applicant
Altova, Inc., “XML Spy 4.0 Manual,” Altova Inc. & Altova GmbH, coyright 1998-2001, Chapters 1, 2, and 6, encompassing pp. 1-17, 18-90, and 343-362.Applicant
Cybook, Inc.: “Copying the Search Form to Services-based Web Sites” INternet Article, (online) Jul. 26, 2004.*the whole document*.Applicant
Excel Developer Tip (hereinafter “Excel”), “Determining the Data Type of a Cell”, May 13, 1998, p. 1 (available at http://jwalk.com/ss//excel/tips/tip62.htm).Applicant
Macromedia, INC.: “Dreamweaver Technote, Changes in copying and pasting in Dreamweaver 4” Internet Article (online). *the whole document*.Applicant
Rado, Dave: “How to create a template that makes it easy for users to “fill in the blanks”, without doing any programming” Microsoft Word MVP FAQ Site, (online) Apr. 30, 2004, the whole document.Applicant
Atova, “User Reference manual Version 4.4, XML Spy suite 4.4,” Atova Ges.m.b.H and Altova, Inc., May 24, 2002, pages cover, copyright p. 1-565.Applicant
Altova et al. XML Spy, XML integrated Development Environments, Altova Inc., 2002, pp. 1-18.Applicant
Ben-Natan, U.S. Appl. No. 60/203,081, filed May 9, 2000, entitied “Internet platfonn for creating and supporting communities”.Applicant
Ixia Soft, “Steamlining content creation, retrieval, and publishing on the Web using TEXTML Server and SML Spy 4 Suite in an integrated, Web publishing environment,” (Partner's Whitepaper, published on the Web as of Jun. 6, 2002, downlowad pp. 1-16.Applicant
Kutay, U.S. Appl. No. 60/209,713, filed Jun. 5, 2000, entitled, “Methods and systems for accessing, organizing presenting and viewing data”.Applicant
Microsoft Word 2000 (see Screen Shot “About Microsoft Word”) Published 1983-1999 and Microsoft Excel 2000 (see Screen Shot “About Microsoft Excel”) Published 1988-1999, Three pages.Applicant
Moore, U.S. Appl. No. 60/191,662, filed Mar. 23, 2000, entitled “Collection-based presistent digital archives”.Applicant
Cover, XML Forms Architecture, retrieved at << http://xml.coverpages.org/xfa.html>> on Aug. 17, 2006, Coverpages, Jun. 16, 1999.Applicant
Raggett, “HTML Tables”, retrieved on Aug. 6, 2006, at <<http:www://is-edu.hcmuns.edu.vn/WebLib/books/Web/Tel/html3-tables.html>>, W3C Internet Draft, Jul. 7, 1995, pp. 1-12.Applicant
Brabrand et al., PowerForms: “Declarative Client Side Form Field Validation”, World Wide Web, Baltzer Science Publishers, Bussum, NL. vol. 3, No. 4, Dec. 2000, p. 1-20.Applicant
Beauchemin, “Using Infopath to Create Smart Forms”, Jan. 21, 2007, at <<http://www.microsoft.com/office/infopath/prodinfo/using.mspx>>, Microsoft Corporation, 2007, pp. 1-6.Applicant
Begun, et al., “Support and Troubleshooting for XML Schema In InfoPath 2003”, Jan. 21, 2007, at <<http://msdn2. microsoft.com/en-us/library/aa168241(office.11,d=printer).aspx>>, Microsoft Corporation, 2007, pp. 1-18.Applicant
Dubinko, et al., “XForms 1.0”, W3C, 2001 pp. 1-125.Applicant
Dubinko, “Xforms and Microsoft InfoPath”, Jan. 21, 2007, at <<http://www.xml.com/1pt/a/1311>>, O'Reilly Media, 1998-2006, pp. 1-6.Applicant
DuCharme, “InfoPath and Xforms”, Jan. 21, 2007, at <<http://weblog.infoworld.com/udell/2003/02/26.html>>, InfoWorld, 2007, pp. 1-3.Applicant
“Enter Key”, Retrieved on Dec. 20, 2006, at <<http://systems.webopedia.com/TERM/E/Enter—key.html>>, Sep. 1, 1996, pp. 1.Applicant
Hoffman, “Architecture of Microsoft Office infoPath 2003”, Jan. 21, 2007, at <<http://msdn2.microsoft.com/en-us/ilbrary/aa219024(office.11,d=printer).aspx>>, Microsoft Corporation, 2007, pp. 1-18.Applicant
Lehtonen, et al., “A Dynamic User Interface for Document Assembly”, ACM, 2002, pp. 134-141.Applicant
“Microsoft Visual Basic 5.0 Programmer's Guide 1997”; pp. 42-43,54-58; Redmond WA 98052-6399.Applicant
Nelson at al., “Client-Side Form Validation Using JavaScript”, Sep. 21, 2001, Retrived from the Internet on Dec. 6, 2004.Applicant
Rees, “Evolving the Browser Towards a Standard User Interface Architecture”, Third Australasian User Interfaces Conference, 2001, Australian Computer Society Inc, IEEE Computer Society, pp. 1-7.Applicant
Singh, “Microsoft Infopath 2003 by Example”, Jan. 21, 2007, at <<http://www.perfectxml.com/InfoPath.asp>>, PerfectXML.com, 2004, pp. 1-19.Applicant
Beauchemin, Dave “Using InfoPath to Create Smart Forms”, Retrieved from the Internet at http:/www.microsoft.com/office/infopath/prodinfo/using.mspx on Jan. 21, 2007, (Mar. 27, 2003),.Applicant
Begun, Andrew et al., “Support and Troubleshooting for XML Schemas in InfoPath 2003”, Microsoft Office InfoPath 2003 Technical Articles, Retrieved from the Internet at http://msdn2.microsoft.com/en-us/library/aa168241(office.11,d=printer).aspx on Jan. 21, 2007, (Aug. 2004).Applicant
Dubinko, Micah “XForms and Microsoft InfoPath”, Retrieved from the Internet at http://www.xml.com/Ipt/a/1311 on Jan. 21, 2007,(Oct. 29, 2003).Applicant
Udell, Jon “InfoPath and XForms”, Retrieved from the Internet at http://weblog.infoworld.com/udell/2003/02/26.html, (Feb. 26, 2003).Applicant
Hoffman, Michael “Architecture of Microsoft Office InfoPath 2003”, Microsoft Office InfoPath 2003 Technical Articles, Retrieved from the Internet at http://msdn2.microsoft.com/en-us/library/aa219024(office.11,d=printer).aspx on Jan. 21, 2007,(Jun. 2003).Applicant
Singh, Darshan “Microsoft InfoPath 2003 by Example”, Retrieved from the Internet at http://www.perfectxml.com/InfoPath.asp on Jan. 21, 2007,(Apr. 20, 2003).Applicant
Raman, T. V., et al., “XForms 1.0”, (Dec., 2001),Section 1-12.2.3 & Appendices A-G.Applicant
“Enter Key”, Retrieved from the Internet at http://systems.webopedia.com/TERM/Enter—key.html on Dec. 20, 2006.Applicant
Lehtonen, Miro et al., “A Dynamic User Interface for Document Assembly”, Department of Computer Science, University of Helsinki,(Nov. 2002).Applicant
Rees, Michael J., “Evolving the Browser Towards a Standard User Interface Architecture”, School of Information Technology, Bond University, Australia,(2001).Applicant
“Microsoft Visual Basic 5.0 Programmer's Guide”, Microsoft Press, (1997), pp. 42-43, 54-58.Applicant
Nelson, Joe “Client-side Form Validation Using JavaScript”, Developer Advisory, (Sep. 21, 2001).Applicant
Borland, Russo “Running Microsoft Word 97”, 314-315, 338, 361-362, 390, and 714-719.Applicant
“Microsoft Word 2000”, Screenshots,(1999),1-5.Applicant
Brabrand, et al., “Power Forms Declarative Client-side Form Field Validation”, (2002),1-20.Applicant
Anat, Eyal et al., “Integrating and Customizing Hererogeneous E-Commerce Applications”, The VLDB Journal-The International Journal on Very Large Data Bases, vol. 10, Issue 1,(Aug. 2001),16-38.Applicant
Adams, Susie et al., “BizTalk Unleashed”, Sams publishing, 2002, first printing Mar. 2001,(Mar. 2001),1-2, 31-138.Applicant
Vasters, Clemens F., “BizTalk Server 2000 A Beginner's Guide”, Osborne/McGraw-Hill,(2001),1-2, 359-402.Applicant
Halberg, Bruce et al., “Using Microsoft Excel 97”, (1997),191-201, 213-219.Applicant
Villard, et al., “An Incremental XSLT Transformation Processor for XML Document Manipulation”, http://www2002.org/CDROM/refereed/321, Printed on May 18, 2007,(May 2002),25 pages.Applicant
Grosso, et al., “XML Fragment Interchange”, W3C,(Feb. 2001),1-28.Applicant
Altova, et al., “User and Reference Manual Version 4.4”, www.xmlspy.com, (May 24, 2007), 1-565.Applicant
“XForm 1.0”, W3C,(Jul. 16, 2001).Applicant
“Microsoft Word 2000 Screenshots”, (2000),11-17.Applicant
XMLSPY, “XmlSpy 2004 Enterprise Edition Manual”, Altova,(May 17, 2004),1-25, 220-225.Applicant
StylusStudio, “StylusStudio: XPath Tools”, 2004-2007, StylusStudio,1-14.Applicant
Dodds, “Toward an XPath API”, xml.com,(May 7, 2001),1-3.Applicant
Altova, “Altova Tools for XPath 1.0/2.0”, Altova,1-12.Applicant
“Microsoft Word 2000 Screenshots”, Word,(2000),1-17.Applicant
Bradley, Neil, “The XML Companion, Third Edition,” published by Addison Wesley Professional, http://proquest.safaribooksonline.com0201770598, (Dec. 12, 2001), pp. 1-18.Applicant
Hu et al., “A Programmable Editor for Developing Structured Documents based on Bidirectional Transformations,” ACM, (Aug. 2004), pp. 178-189.Applicant
Klarlund, Nils et al., “DSD: A Schema Language for XML,” ACM, FSMP Portland, Oregon, (2000), pp. 101- 111.Applicant
U.S. Office Action mailed Sep. 6, 2007 cited in U.S. Appl. No. 10/897,647.Applicant
U.S. Final Office Action mailed Mar. 6, 2008 cited in U.S. Appl. No. 10/897,647.Applicant
U.S. Office Action mailed Jul. 18, 2007 cited in U.S. Appl. No. 10/898,657.Applicant
U.S. Final Office Action mailed Jan. 3, 2008 cited in U.S. Appl. No. 10/898,657.Applicant
U.S. Office Action mailed Sep. 8, 2008 cited in U.S. Appl. No. 10/898,657.Applicant
U.S. Office Action mailed Jul. 13, 2007 cited in U.S. Appl. No. 10/898,656.Applicant
U.S. Final Office Action mailed Nov. 15, 2007 cited in U.S. Appl. No. 10/898,656.Applicant
U.S. Office Action mailed Apr. 18, 2008 cited in U.S. Appl. No. 10/898,656.Applicant
Watt, Andrew, “Microsoft Office Infopath 2003 Kick Start,” (published by Sams) Print ISBN-10:0-672-32623-X, (Mar. 24, 2004), pp. 1-57.Applicant
U.S. Office Action mailed Nov. 14, 2008 cited in U.S. Appl. No. 10/897,647, 31 pages.Applicant
Clarke, P., “From small beginnings,” Knowledge Management, Nov. 2001, pp. 28-30.Applicant
Description of Whitehill Composer software product, produced by Whitehill Technologies, Inc., available at <http://www.xml.com/pub/p/221>, accessed on Apr. 8, 2004, two pages.Applicant
Sun, Q., et al., “A Robust and Secure Media Signature Scheme for JPEG Images,” Proceedings of 2002 IEEE Workshop on Multimedia Signal Processing, Dec. 2002, pp. 296-299.Applicant
Komatsu, N., et al., “A Proposal on Digital Watermark in Document Image Communication and Its Application to Realizing a Signature,” Electronics and Communications in Japan, Part I: Communications, vol. 73, No. 5, May 1990 , pp. 22-33.Applicant
Noore, A., “A Secure Conditional Access System using Digital Signature and Encryption,” International Conference on Consumer Electronics, Jun. 2003, pp. 220-221.Applicant
Pacheco, X., et al., “Delphi 5 Developer's Guide,” Sams Publishing 1999, Section: Data Streaming, 6 pages.Applicant
Hwang, Kai et al., “Micro-Firewalls for Dynamic Network Security with Distributed Intrustion Detection,” IEEE Int'l. Symposium on Network Computing and Applications, 2001 pp. 68-79.Applicant
Schmid, M. et al., “Protecting Data from Malicious Software,” 18th Annual Security Applications Conference, 2002, pp. 199-208.Applicant
Kaiya, Haruhiko et al., “Specifying Runtime Environments and Functionalities of Downloadable Components under the Sandbox Model,” Intl. Symposium on Principles of Software Evolution, 2000, pp. 138-142.Applicant
Tomimori, Hiroyuki et al., “An Efficient and Flexible Access Control Framework for Jav aPrograms in Mobile Terminals,” Proceedings of 22nd Int'l. Conference on Distributed Computing Systems Workshops, 2002, pp. 777-782.Applicant
Prevelakis, Vassilis et al., “Sandboxing Applications,” FREENIX Track: 2001 USENIX Annual Technical Conference, pp. 119-126.Applicant
“Webopedia Computer Dictionary” retrieved on May 9, 2006, at <<http://www.pewebopedia.com/TERM/O/OLE.html>>, Jupitermedia Corporation, 2006, pp. 1-7.Applicant
Final Office Action mailed Jul. 14, 2009 cited in U.S. Appl. No. 10/897,647, 37 pages.Applicant