Application History Manager for State Navigation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Computer applications lack a robust mechanism for recording and navigating user interactions, unlike browser experiences, which limits the ability to efficiently return to previous states or save interactions for future reference.
Innovation Solution
Implementing a system with a history manager that includes save and load state methods for objects within the application, allowing users to navigate back to specific user interactions by storing and restoring application states associated with those interactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If general computer applications use sequential code execution without address-based mechanisms, then the application can execute complex logic and processing, but the application cannot record and navigate user interactions like browser history
Solution Approach 1:
The patent segments the application into distinct navigable states, where each user interaction or view change creates a new state entry. This allows the application to function as multiple discrete navigation points rather than continuous sequential execution, enabling history navigation while maintaining logical processing flow.
Solution Approach 2:
The patent introduces a history manager as an intermediary component that mediates between the application's sequential execution and the user's navigation needs. The history manager intercepts state changes, records them in a data structure, and provides navigation capabilities without requiring fundamental changes to the application's core execution model.
2Ease of operation
If applications implement browser-like navigation tools, then users can easily return to previous interactions, but applications must store and manage state information which increases complexity
Solution Approach 1:
The patent implements self-service by having the history manager automatically capture and record application states without requiring manual intervention from developers or users. The system autonomously monitors state changes and maintains the navigation history, reducing the burden on both implementation and usage sides.
Solution Approach 2:
The patent creates copies of application states at each navigation point, storing snapshots of the application's condition rather than maintaining complex references to previous states. This copying approach simplifies state management by making each historical state independent and self-contained, enabling easy retrieval and restoration.
3Loss of information
If applications record detailed user interaction history, then users can return to specific previous states, but memory and storage requirements increase
Solution Approach 1:
The patent extracts only the essential state information needed for navigation purposes, separating critical navigation data from complete application state data. By taking out only the necessary elements (such as view identifiers, parameter values, and navigation context) rather than storing entire application states, the system reduces memory consumption while preserving navigation functionality.
Data Source
AI summary
A system and method are disclosed for history management a plurality of objects within an application, wherein each of the plurality includes at least a software method for saving the object's state and a software method for loading the object's state and a history manager function including a software method for recording an application interaction state for each user interaction with the application, wherein the application interaction state comprises the object's state for each of the plurality of objects at a time of the each user interaction with the application, wherein the user selects a desired one of the application interaction states to set the application to a desired one of the user interactions.