Context-Sensitive User Interface Composition via Graphic Objects
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing user interfaces are monolithic and non-reusable, making it difficult to provide different or modified UIs for various applications, users, and systems, as they require extensive knowledge of the application and preexisting UI code, and extensive revisions are often necessary.
Innovation Solution
A context-sensitive user interface is generated by associating data objects with attributes, using a declarative and compositional approach that allows for customizable UIs, where UI models and management models are used to define user interactions and transitions, enabling flexible and extensible user interface frameworks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If user interfaces are hard-coded with specific graphic objects and transitions, then the UI is stable and reliable, but it becomes monolithic and non-reusable across different applications and systems
Solution Approach 1:
The patent segments the monolithic UI into reusable components called graphic objects with associated transitions and actions. Each graphic object is an independent, self-contained unit that can be selectively assembled into different UIs. This segmentation allows the same graphic objects to be reused across multiple applications and systems while maintaining stability through their predefined behaviors.
Solution Approach 2:
The patent creates universal graphic objects that can serve multiple functions across different applications and systems. These graphic objects are designed to be context-independent and can be instantiated in various UI scenarios, enabling a single graphic object to fulfill multiple roles and reducing the need for application-specific UI code.
2Adaptability or versatility
If different or modified UIs are created to support different applications and users, then adaptability is improved, but extensive knowledge of application and preexisting UI code is required
Solution Approach 1:
The patent performs preliminary action by pre-defining graphic objects with their transitions, actions, and associations before they are needed in specific applications. This upfront preparation allows developers to simply select and assemble pre-built graphic objects rather than creating UI code from scratch, significantly reducing the knowledge and effort required to create customized UIs.
Solution Approach 2:
The patent enables copying of graphic objects from existing UIs to new applications. Once a graphic object is defined with its behavior and associations, it can be instantiated and reused across multiple contexts without requiring extensive modification or deep understanding of the underlying code, lowering the barrier to UI customization.
3Adaptability or versatility
If preexisting UI code is extensively revised to provide different UIs, then adaptability is improved, but development time and effort increase significantly
Solution Approach 1:
The patent introduces dynamics by allowing UIs to be assembled and configured at runtime through data-driven associations rather than being fixed at compile time. Graphic objects can be dynamically selected, instantiated, and configured based on application context and user requirements, enabling UI flexibility without the need for extensive code revision and recompilation cycles.
Solution Approach 2:
The patent uses parameter changes to adapt UIs by modifying data associations and configurations rather than changing the underlying code structure. By changing parameters such as which graphic objects are associated with which data objects and transitions, the system can provide different UIs for different applications and users without requiring code revision, significantly reducing development time.
Data Source
AI summary
A user interface is composed using methods and systems that allow modifying or re-using existing user interfaces, or creating new user interfaces. In providing for such interfaces, context-sensitive or context specific attributes that are associated with a particular user, user groups, and/or application(s) are used as the basis of composition. This allows for the dynamic creation of user interfaces based upon the situation.