|Publication number||US7536672 B1|
|Application number||US 10/794,173|
|Publication date||May 19, 2009|
|Filing date||Mar 5, 2004|
|Priority date||Mar 5, 2004|
|Also published as||US8281285, US20090228805|
|Publication number||10794173, 794173, US 7536672 B1, US 7536672B1, US-B1-7536672, US7536672 B1, US7536672B1|
|Inventors||Glenn Warren Ruehle|
|Original Assignee||Adobe Systems Incorporated|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (4), Referenced by (26), Classifications (6), Legal Events (3)|
|External Links: USPTO, USPTO Assignment, Espacenet|
The present invention relates, in general, to software application functionality, and, more specifically, to managing the history of user interactions with a software application.
The growth of the Internet has spawned a variety of industries and applications. Browser technology, the computer applications used to navigate the Internet and the World Wide Web (WWW), have become a nearly universal computer application paradigm. The ease with which users are able to navigate between various Web pages resulted in a new generation of browser-centric users. Web pages are typically formatted in hypertext markup language (HTML). HTML is a format-descriptive meta language that describes the visual formatting and layout of the Internet documents. These documents are generally delivered to users over the Internet using hypertext transfer protocol (HTTP). HTTP is an address-oriented transport protocol that utilizes uniform resource locators (URLs) to identify the locations of specific Web pages. Web browsers use these URLs to navigate between the various HTML pages that a user desires to see.
In comparison, most general computer applications, whether on the desktop or Web-based, utilize a direct and application-specific interface with the user. Therefore, users interact with various general computer applications using navigation means that are generally different from their browser experience. With the increased popularity and usability of browsers, however, many software manufacturers have modified various user interface (UI) elements of general applications to mimic the ease and familiarity of the browser experience.
One shortcoming to general computer applications that has generally escaped a browser-like UI feature is the “Back” button. Browser users are familiar with the standard browser navigation tools, such as Back, Forward, Home, Favorites, and the like. Without these tools, it is likely that users would not have as good an experience in navigating the Web as they currently enjoy. The WWW is typically well-suited to such navigation tools because of the address-oriented nature of the URL-based transport protocol, HTTP. As a user “surfs” or hypertext jumps from one page to the next, a history of the user's interactions is easily recorded and managed. The URL of each page may simply be stored in some kind of storage register or memory location. As the user desires to return to a particular Web page, he or she may either sequentially click the Back button, until the desired page is reached, or, if the user goes past the desired page, he or she may click the Forward button to return through the address list. In some browser embodiments, the user may be shown several historical URLs, or the Web page title associated with that URL, at once, allowing for random navigation by directly selecting the particular address the user desires to jump to. Similarly, if a user desires to save a particular Web page address for future direct reference, the URL for that page may be stored in a Favorites list.
For example. MICROSOFT CORPORATION'S OUTLOOK™ email program allows interaction with email, whether incoming, outgoing, saved, sorted, and the like. While any one particular box, such as the inbox, may have a Back and Forward button to traverse the various emails in that box, those navigational tools typically work within the context of that box. Moreover, those interface elements usually work in the context of location. Therefore, if a user begins looking at the first email, then selects to view the tenth email, using the back button would only get the user to the ninth email, even though the user had yet to actually view the ninth email. Similarly, if a user views emails that have been sorted in a specific folder and then moves to view emails in the inbox, pressing the back button will not return the user to viewing the email in the specific folder.
Wizards are computer applications that are developed to step a user through a particular process. The Wizard, somewhat like a browser, displays a view screen to a user for providing some information or to request a particular action. Once the action is taken, it moves to the next view screen in the Wizard sequence. Wizards will typically have a Back button, but this Back button works only in a sequential method. Therefore, in view screen five, if the user selects the Back button, the user is “backed up” to view screen four. These navigation features in a Wizard do not necessarily operate on the basis of the user's interaction history, but merely operate on the sequence of the Wizard itself. A user desiring to go completely back to the beginning of the Wizard would need to repeatedly select the Back button in order to get there. Moreover, if, during operation of the Wizard, the user accessed another application running on the user's computer, the Wizard Back button would not take the user back to this separate application.
Another example of an attempt by computer software manufacturers to implement Browser-like navigation are large form-type applications. One example of a form-type application would be INTUIT CORPORATION's TURBOTAX™. The function of the TURBOTAX™ software is to step a user through a series of fill-in form pages in order to complete various federal income tax return forms. Recent versions of TURBOTAX™ have included not only a Wizard-like Back button, which works sequentially, but also a hypertext-coded outline of the various major steps allowing the user to hypertext jump to any portion of the fill-in form process. Again, while this navigation allows the user to jump to various places in the application, it is implemented purely through mapping of the application. The various user interactions with TURBOTAX™ are not recorded for purposes of navigation. Therefore, if a user selected to return to the deductions section, he or she would be taken to the first page of the deductions section regardless of whether or not the user had even been to that page before. While this navigation feature allows the user more flexibility in navigating the application, there is still no way to directly track the user's interactions.
Recently, computer applications have been made available to users to access over the Internet. These Web-based or on-line applications are generally accessed by the user through the container of the Web browser. The Web browser displays an HTML page, however, the HTML page contains a player or other type of application container that runs the visual representation of the Web-based application to the user. In these types of applications, if the user were operating the Web-based application, the browser Back button would not necessarily take the user back to the preceding step of the application, but may, in fact, take the user back to the Web page that preceded the user's activation of the Web-based application. Thus, the Back button would exit the user from the application altogether.
In order to compensate for this problem with on-line applications, techniques have been developed to communicate with the browser that the user is interacting with an on-line application that is being displayed within the browser. Such features are typically implemented using a hidden Web page, referred to as an invisible frame or i-frame. When a user calls an on-line application, an HTML shell is loaded with the container on which the on-line application will be displayed. One example of such a container may be MACROMEDIA INC.'s MACROMEDIA FLASH™ PLAYER. Along with the MACROMEDIA FLASH™ PLAYER will be the i-frame. An i-frame is a browser element which is a floating frame, sub-navigational element within the browser window. Navigation that occurs within the i-frame is remembered in the browser's history mechanism. Therefore, when a user selects Back or Forward, the history information from the i-frame is used.
In the example of a MACROMEDIA FLASH™ PLAYER container, the i-frame will also includes a Small Web Format (SWF) file. SWF files are the native file format in MACROMEDIA FLASH™. The SWF file within the I-frame will be used to communicate with the main SWF file running in the MACROMEDIA FLASH™ PLAYER container. In these applications, the developer has generated state book marks which mark places in the application for use with a navigational feature. For example, a developer may place code in the application that state A is an entry screen, while state B is a processing screen, and state C is a confirmation screen. When the application is running and a user moves from the entry screen to the processing screen, the i-frame notes the change from state A to state B in a URL having query information concerning the actual state of the application. The browser history feature remembers the new URL of the processing screen, which is state B for the application. If the user were to select the Back button on the browser, the browser pulls the previous URL from its history, passes it to the i-frame, which, in turn, uses the query information from the previous URL to communicate to the main SWF file running on the MACROMEDIA FLASH™ PLAYER container and reload state A to the main SWF file. Therefore, the user is taken back to state A or the entry screen of the on-line application. While this method allows for history navigation within an on-line application, the application developers hard codes each state identifier into the application, adding a substantial amount of work and expense to the development of the application.
Representative embodiments of the present invention are related to a system and method for managing user interaction with computer applications. Computer applications typically comprise a number of objects that operate or are displayed within the application. Computer applications that are configured according to the teachings of the present invention include objects that may have at least two computer methods: a save state method and a load state method. To interact with these objects, a history manager is also used that includes, at least, a method for saving the application state. In calling this save application state method from the history manager, the history manager calls the save state method for each of the objects in the application. The collection of each of the objects' saved states is then stored, associated with the particular user interaction that caused each of the states. If a user desires to go back to one of the previous points in the application, he or she may select the particular application state that is stored associated with that particular user interaction or application state.
In response to this Back feature being selected, the history manager calls the load state method for each of the objects, which then reload the state that was originally stored for that particular application state or that particular user interaction. By causing each object to restore the specific state, the application returns to the exact state for that particular user interaction. Maintaining a list of the state objects, state objects are each of the objects' states saved for a particular user interaction, the user may select to go back to previous interactions and then go forward to current interactions. With the ability to save these state objects, a user may also more permanently save an interaction state in a favorites-like data structure.
The foregoing has outlined rather broadly the features and technical advantages of the present invention in order that the detailed description of the invention that follows may be better understood. Additional features and advantages of the invention will be described hereinafter which form the subject of the claims of the invention. It should be appreciated that the conception and specific embodiment disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present invention. It should also be realized that such equivalent constructions do not depart from the invention as set forth in the appended claims. The novel features which are believed to be characteristic of the invention, both as to its organization and method of operation, together with further objects and advantages will be better understood from the following description when considered in connection with the accompanying figures. It is to be expressly understood, however, that each of the figures is provided for the purpose of illustration and description only and is not intended as a definition of the limits of the present invention.
For a more complete understanding of the present invention, reference is now made to the following descriptions taken in conjunction with the accompanying drawing, in which:
In the example described in
In the embodiment of the present invention depicted in
When the user interacts with the application, history manager 40 calls save state objects method 401, which, in turn, calls save state method 402 of object-1 41. History manager 40 will then cycle through object list 409 calling the save state method for each of the other objects that have registered with history manager 40. In response to save state method 402, object-1 41 stores its current state in object registry 42 associated with the user's current interaction as a state object, such as state objects 406-408.
As the user continues to interact with the application, state objects continue to be saved in object registry 42. If the user desires to return to any one of those previous interactions, he or she may invoke the history management feature, which presents all of the state objects in object registry 42 for random selection by the user. When the user selects anyone of these state objects, such as state object 407, object-1 41 calls load state method 403 to retrieve and load into its “current” state, the state that had been saved and associated with the user interaction associated with state object 407. When re-loading the previous “current” state, object depth 405 is used to determine which state objects to restore first. State objects are restored in hierarchical order starting with the outer most object or a parent relationship and ending with the inner most object level or the child or sibling relationship. Upon the loading of the previous state, the application again displays to the user the exact state that the application was in when the user interacted with the application at the user-selected previous point. The user may then randomly return to any of the subsequent states in the same manner, by selecting state object 408, for example.
It should be noted that the specifics described with respect to
It should further be noted that in additional or alternative embodiments to the present invention, certain objects may be designated in various development environments as objects that use history management by default. Such objects may be navigational elements such as a tab navigator or an accordion navigator. An example of such a development environment in which selected objects are registered with the history manager by default is MACROMEDIA, INC.'s FLEX™. FLEX™ is a development environment utilizing server-side code that assists in developing rich Internet applications. The FLEX™ server delivers a standards-based, declarative programming methodology and workflow along with runtime services for developing and deploying the presentation tier of rich client applications. FLEX™ utilizes MACROMEDIA FLASH™ as a container for delivering rich media applications to a client.
When the user selects button 508 in application 500, the state of button 508 is changed, along with possible changes in other objects of application. For purposes of the example illustrated in
If the user subsequently desires to return to the interaction described above, the application states are loaded in a top-down sequence from the highest level to the lowest. For example, the application view page for application 50 is loaded. Next, the state of tab 501 was a “viewable” state. Therefore, the visible page is displayed corresponding to tab 501. Tabs 502 and 503 were each in a “hidden” state, for which the hidden view is displayed corresponding to tabs 502 and 503. Proceeding down the hierarchical levels, tab 504 was in a “viewable” state, such that its visible page is displayed. Tabs 505 and 506 were “hidden,” such that their states are reloaded in the “hidden” states. Finally, buttons 507-509 are each rendered onto the visible page of tab 504. Button 508 had been selected by the user. Therefore, its state was restored in the “selection” state.
As the user interacts with Web application 60, a state object is created using each of the present states of the objects within Web application 60. A single state object is created for each user interaction and stored in state object memory 608. The functions of Web application 60 operate to convert the single state object into a properly formatted query information string, which is then used to compiled state object URL 607. I-frame 604 communicates state object URL 607 to the browser, which stores it in browser history memory 610.
If the user desires to return to one of his or her previous interactions, he or she selects the specific URL from the browser's history feature. In response to this selection, the appropriate state object URL is retrieved from browser history memory 610, such as state object URL 607. State object URL 607 is communicated to i-frame 604, in which the state information contained within the query information string of state object URL 607 is used by SWF 609 to load the previous state into Web application 60. The display of Web application 60 is, thus, restored to the desired interaction that the user selected.
Although the present invention and its advantages have been described in detail, it should be understood that various changes, substitutions and alterations can be made herein without departing from the invention as defined by the appended claims. Moreover, the scope of the present application is not intended to be limited to the particular embodiments of the process, machine, manufacture, composition of matter, means, methods and steps described in the specification. As one will readily appreciate from the disclosure, processes, machines, manufacture, compositions of matter, means, methods, or steps, presently existing or later to be developed that perform substantially the same function or achieve substantially the same result as the corresponding embodiments described herein may be utilized. Accordingly, the appended claims are intended to include within their scope such processes, machines, manufacture, compositions of matter, means, methods, or steps.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US6527812 *||Dec 17, 1998||Mar 4, 2003||Microsoft Corporation||Method and system for undoing multiple editing operations|
|US6532472 *||Sep 29, 1998||Mar 11, 2003||Apple Computer, Inc.||Persistent state database for operating system services|
|US7143392 *||Feb 11, 2002||Nov 28, 2006||Hewlett-Packard Development Company, L.P.||Hyperbolic tree space display of computer system monitoring and analysis data|
|US20020143861 *||Apr 2, 2001||Oct 3, 2002||International Business Machines Corporation||Method and apparatus for managing state information in a network data processing system|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7802262||Sep 21, 2010||Adobe Systems Incorporated||System and method for communicating state and title information between a browser and a rich internet application with browser forward and back button support|
|US7882447||Feb 1, 2011||Ebay Inc.||Method and system to determine area on a user interface|
|US8001458||Nov 15, 2005||Aug 16, 2011||Adobe Systems Incorporated||System and method for communicating state and title information between a browser and a rich Internet application|
|US8234657||Sep 16, 2010||Jul 31, 2012||Adobe Systems Incorporated||System and method for communicating state and title information between a browser and a rich internet application with browser forward and back button support|
|US8250059||Sep 14, 2009||Aug 21, 2012||International Business Machines Corporation||Crawling browser-accessible applications|
|US8281285||May 18, 2009||Oct 2, 2012||Adobe Systems Incorporated||Management of user interaction history with software applications|
|US8402068||Dec 7, 2000||Mar 19, 2013||Half.Com, Inc.||System and method for collecting, associating, normalizing and presenting product and vendor information on a distributed network|
|US8555160 *||Mar 21, 2008||Oct 8, 2013||Canon Kabushiki Kaisha||Apparatus and methods for creating and/or editing color-image processing files|
|US8606768 *||Dec 20, 2007||Dec 10, 2013||Accenture Global Services Limited||System for providing a configurable adaptor for mediating systems|
|US8655865 *||May 27, 2011||Feb 18, 2014||Adobe Systems Incorporated||Method and apparatus for indexing rich internet content using contextual information|
|US8756214||Jun 18, 2012||Jun 17, 2014||International Business Machines Corporation||Crawling browser-accessible applications|
|US8768937||Mar 11, 2013||Jul 1, 2014||Ebay Inc.||System and method for retrieving and normalizing product information|
|US8863002||Oct 4, 2010||Oct 14, 2014||Ebay Inc.||Method and system to dynamically browse data items|
|US9134884 *||Sep 29, 2005||Sep 15, 2015||Ebay Inc.||Methods and systems to process a selection of a browser back button|
|US9171056||Jun 16, 2014||Oct 27, 2015||Paypal, Inc.||System and method for retrieving and normalizing product information|
|US9262056||Sep 29, 2005||Feb 16, 2016||Ebay Inc.||Methods and systems to browse data items|
|US20020107861 *||Dec 7, 2000||Aug 8, 2002||Kerry Clendinning||System and method for collecting, associating, normalizing and presenting product and vendor information on a distributed network|
|US20060224406 *||Sep 29, 2005||Oct 5, 2006||Jean-Michel Leon||Methods and systems to browse data items|
|US20060224571 *||Sep 29, 2005||Oct 5, 2006||Jean-Michel Leon||Methods and systems to facilitate searching a data resource|
|US20060224954 *||Sep 29, 2005||Oct 5, 2006||Corey Chandler||Method and system to determine area on a user interface|
|US20060224960 *||Sep 29, 2005||Oct 5, 2006||Baird-Smith Anselm P||Methods and systems to process a selection of a browser back button|
|US20080244374 *||Mar 21, 2008||Oct 2, 2008||Canon Kabushiki Kaisha||File processing apparatus, file processing method and color-image processing file|
|US20090164500 *||Dec 20, 2007||Jun 25, 2009||Ankur Mathur||System for providing a configurable adaptor for mediating systems|
|US20090228805 *||May 18, 2009||Sep 10, 2009||Adobe Systems Incorporated||Management of User Interaction History with Software Applications|
|US20110066609 *||Sep 14, 2009||Mar 17, 2011||International Business Machines Corporation||Crawling Browser-Accessible Applications|
|US20110093494 *||Oct 4, 2010||Apr 21, 2011||Ebay Inc.||Method and system to dynamically browse data items|
|U.S. Classification||717/101, 717/102, 717/103|
|Jun 28, 2004||AS||Assignment|
Owner name: MACROMEDIA, INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:RUEHLE, GLENN WARREN;REEL/FRAME:015502/0553
Effective date: 20040611
|Jan 19, 2006||AS||Assignment|
Owner name: ADOBE SYSTEMS INCORPORATED,CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MACROMEDIA, INC.;REEL/FRAME:017034/0263
Effective date: 20051207
Owner name: ADOBE SYSTEMS INCORPORATED, CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MACROMEDIA, INC.;REEL/FRAME:017034/0263
Effective date: 20051207
|Sep 28, 2012||FPAY||Fee payment|
Year of fee payment: 4