Decoupling GUI Models from Runtime Environments
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing graphical user interface (GUI) models are tightly coupled with runtime environments, making it difficult to evolve models without affecting the runtime environment and requiring designers to consider runtime environment dependencies during the design phase.
Innovation Solution
A declarative and executable representation for GUIs is provided, independent of any particular runtime platform, GUI framework, or programming language, using a generic, declarative, and executable GUI language (XGL) that generates abstract representations decoupled from runtime environments, allowing for device-independent and programming-language-independent GUI generation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If model representations are tightly coupled to runtime environments using specialized runtime tools, then transformation to executable form is achieved, but model evolution becomes difficult and runtime environment dependencies must be considered during design
Solution Approach 1:
The patent introduces an intermediary representation layer between the design-time model and the runtime environment. This intermediary serves as a mediator that enables transformation to multiple runtime forms without tight coupling, allowing model evolution while maintaining transformation accuracy through structured intermediate representations.
Solution Approach 2:
The transformation process is segmented into distinct stages: design-time model creation, intermediary representation generation, and runtime environment-specific code generation. This segmentation allows independent evolution of models without affecting runtime dependencies, as each stage operates with defined interfaces.
2Reliability
If designers consider runtime environment dependencies during the design phase, then correct transformation is ensured, but design flexibility and portability are reduced
Solution Approach 1:
The patent separates design-time operations from runtime environment considerations by introducing an intermediary representation. Designers work with platform-independent models during design, and runtime-specific transformations are handled automatically by code generators, ensuring transformation correctness without reducing design flexibility.
Solution Approach 2:
The intermediary representation acts as a mediator that preserves transformation correctness while abstracting away runtime environment dependencies during design. This allows designers to create portable models that can be transformed to multiple runtime environments without considering specific platform details during the design phase.
3Adaptability or versatility
If specialized runtime tools are used for each target device, then device-specific GUI generation is achieved, but system complexity and maintenance difficulty increase
Solution Approach 1:
The patent creates a universal intermediary representation that can be transformed to multiple device-specific GUIs through a common code generation framework. This multi-functional approach allows a single design-time model to support various target devices without requiring separate specialized tools for each, reducing system complexity while maintaining device-specific customization.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Techniques for decoupling models created during design-time from the runtime environment. A declarative and executable representation for GUIs for applications is provided that is independent of any particular runtime platform, GUI framework, device, or programming language and which acts as an interface between the design environment and the runtime environment.