PRESERVING A COMPLETE HISTORY OF A SET OF APPLICATION ACTIONS WHEN NON-LINEAR INTERACTIONS ARE PERMITTED

• US 20090327973A1
• Filed: 04/29/2008
• Published: 12/31/2009
• Est. Priority Date: 04/29/2008
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: LIN, DINAH H., SHAH, PRATIK P., ZHANG, ZHENG, LEE, PUCCI
• Application Number:
  US12/111,560
• Publication Number:
  US 20090327973A1
• Time in Patent Office: Days
• US Class Current: 715/854
• CPC Class Codes: G06F 9/45512 Command shells

Abstract

An action history maintains a set of ordered application actions associated with a user. A user interface of a software application can include a back control and a forward control, which utilize the action history. Specifically, the back control revokes a most recent action and the forward control reapplies a previously revoked action. Thus, the forward and backward controls change which page is rendered in the software application. Unlike traditional implementations, the invention maintains a complete set of actions within the action history in a non-linear context. That is, when a new action is inserted into a history from a non-terminal state (i.e., actions able to be reapplied are available upon a selection of the forward control) then the new action is inserted immediately after the current action. The historic actions are maintained in order after the new action in the action history.

Claims

1. A system for preserving interactive actions comprising:

a software application comprising a user interface, said user interface comprising a back control and a forward control;

an interaction history object configured to maintain a plurality of ordered elements, each element representing a user interaction with the software application;

an interaction modification engine configured to automatically revoke a past interaction responsive to a user selection of the back control, wherein the revoked past interaction is an interaction denoted by an element ordered immediately before a current position reference maintained for the interaction history object, wherein each time the interaction modification engine revokes a past interaction the current position reference advances backward by one ordered element, wherein the interaction modification engine is configured to reapply a previously revoked interaction responsive to a user selection of the forward control, wherein the reapplied interaction is an interaction denoted by an element ordered immediately after the current position reference maintained for the interaction history object, wherein each time the interaction modification engine reapplies the previously revoked interaction the current position reference advances forward by one ordered element; and

an interaction recording engine configured to detect a user interaction with said software application and to responsively add an interaction element to the interaction history object for each detected user interaction, wherein when the interaction recording element adds a new element and when one or more ordered elements are positioned in the interaction history object after the current position reference, the interaction recording engine is configured to add the new element to the interaction history element at a point immediately after the current position reference, to order the one or more ordered elements to a position immediately following the added new element, and to advance the current position reference forward by one ordered element.

2. The system of claim 1, wherein the user interface comprises a graphical user interface (GUI), wherein the back interaction interface control is a previous page navigation control represented by a back arrow within the user interface, and wherein the forward interaction interface control is next page navigation control represented by a forward arrow within the user interface.

3. The system of claim 1, wherein the user interface comprises a voice user interface (VUI), wherein the back interaction interface control is a previous page navigation control selectable through a user provided speech input, and wherein the forward interaction interface control is next page navigation control selectable through a user provided speech input.

4. The system of claim 1, wherein the interaction history object is implemented as a stack of elements.

5. A method for utilizing an action history comprising:

performing an ActionA in a software application, which results in the software application being placed in an ApplicationStateA;

adding an ElementA to an action history corresponding to ActionA;

performing an ActionB in the software application, which results in the software application being placed in an ApplicationStateB;

adding an ElementB to an action history corresponding to ActionB;

receiving a selection of a back control;

revoking Action B so that the software application is placed in ApplicationStateA;

performing an ActionC so that the software application is placed in ApplicationStateC;

receiving a selection of a forward control;

determining ActionB is to be applied responsive to the selection of the forward control based upon elements in the action history; and

applying ActionB so that the software application is placed in ApplicationStateB.

6. The method of claim 5, wherein the wherein the software application comprises a graphical user interface (GUI), wherein the back control is a previous page navigation control represented by a back arrow within the graphical user interface, and wherein the forward control is next page navigation control represented by a forward arrow within the graphical user interface.

7. The method of claim 5, wherein the software application comprises a voice user interface (VUI), wherein the back control is a previous page navigation control selectable through a user provided speech input, and wherein the forward control is next page navigation control selectable through a user provided speech input.

8. The method of claim 5, wherein ActionA, ActionB, revocation of ActionB, ActionC, and an reapplication of ActionB is a sequence of temporally consecutive actions involving the software application and the action history, wherein no intervening actions involving the software application and the action history exist within the sequence of temporally consecutive actions.

9. The method of claim 5, wherein ActionA, ActionB, and ActionC are each different programmatic actions performed by the software application in response to at least one user interaction with a user interface of the software application, wherein ActionA, ActionB, and Action C are actions to navigate to a user designated page, and wherein the selection of the back control and the selection of the forward control are both user selections occurring within the user interface, and wherein ApplicationStateA, ApplicationStateB, and ApplicationStateC are each a state of the software application corresponding to a presentation of related page.

10. The method of claim 5, wherein the action history is an interaction history software object comprising an ordered set of elements, each element corresponding to a previously occurring action, wherein a current position reference is associated with the interaction history software object, wherein an element immediately advanced from the current position reference indicates an action that is to be applied upon a selection of the forward control, and wherein an element immediately before the current position reference indicates an action that is to be revoked upon a selection of the back control.

11. The method of claim 5, wherein said steps of claim 5 are performed by at least one machine in accordance with at least one computer program having a plurality of code sections that are executable by the at least one machine.

12. A method for utilizing action history comprising:

maintaining a history of user driven actions for a software application interface, wherein the software application interface comprises a back control and a forward control that change application state based upon the history of user driven actions;

receiving user input via the software application interface;

adjusting a state of a software application associated with the software application interface such that a selection of the forward control would result in an ActionA being applied by the software application;

performing an ActionB at the adjusted state of the software application; and

adding and element for ActionB to the history of user driven actions in a position immediately before an element for ActionA, while retaining the element for ActionA in the history of user driven actions.

13. The method of claim 12, wherein the wherein the software application interface comprises a graphical user interface (GUI), wherein the back control is a previous page navigation control represented by a back arrow within the graphical user interface, and wherein the forward control is next page navigation control represented by a forward arrow within the graphical user interface.

14. The method of claim 12, wherein the software application interface comprises a voice user interface (VUI), wherein the back control is a previous page navigation control selectable through a user provided speech input, and wherein the forward control is next page navigation control selectable through a user provided speech input.

15. The method of claim 12, further comprising:

immediately after ActionB is performed, receiving a user selection of the forward control; and

performing ActionA based upon the user selection of the forward control.

16. The method of claim 12, wherein ActionA and ActionB are each different programmatic actions performed by the software application in response to at least one user interaction with the software application interface, wherein ActionA and ActionB are actions to navigate to a user designated page.

17. The method of claim 14, wherein said steps of claim 14 are performed by at least one machine in accordance with at least one computer program having a plurality of code sections that are executable by the at least one machine.