Dynamically Stylable Open Graphics Library for Real-Time GUI Customization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing graphical user interface (GUI) systems require significant recompilation and recertification whenever changes are made to the user interface, limiting real-time customization and independent development of functional and interface code.
Innovation Solution
A dynamically stylable open graphics library system that allows for real-time changes to GUI elements by modifying configuration files, such as view, layout, and style configuration files, and actuating an actuation control to reload these files during runtime, enabling independent development of functional and interface code without impacting each other.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If GUI changes are made by modifying source code, then functionality can be implemented, but recompilation and recertification are required which limits real-time customization
Solution Approach 1:
The system divides the GUI into separate configuration files (view configuration, layout configuration, style configuration) that are independent from the backend software code. This segmentation allows the GUI to be modified without affecting the backend, eliminating the need for recompilation and recertification when making changes.
Solution Approach 2:
The system uses configuration files as copies or representations of the GUI structure, layout, and styles. Instead of modifying the actual software code, the configuration files serve as data representations that can be changed independently, allowing real-time customization without recertification.
2Adaptability or versatility
If functional code and interface code are developed together, then integration is ensured, but independent development is limited
Solution Approach 1:
The system separates functional code (backend software) from interface code (configuration files). The view configuration file, layout configuration file, and style configuration file independently define the GUI interface, while the backend code handles functionality. This allows both teams to work independently without integration conflicts.
Solution Approach 2:
The configuration files act as an intermediary layer between the backend functional code and the front-end interface. This intermediary allows the interface to be customized without modifying the backend, and the backend to function independently, enabling true independent development while maintaining integration through the configuration interface.
3Productivity
If extensive testing is performed for each GUI change, then reliability is ensured, but development efficiency is reduced
Solution Approach 1:
By segmenting the GUI into configuration files that are independent of the backend code, changes to the interface do not affect the functional code. This eliminates the need for extensive testing of the backend, reducing development time while maintaining reliability through the modular architecture.
Data Source
AI summary
A system to implement a dynamically stylable open graphics library is disclosed. The system includes a memory configured to store machine readable instructions and data and a processing unit. The machine readable instructions and data include a view configuration file that defines view format areas of a graphical user interface where the elements of the graphical user interface are placeable, a layout configuration file that defines a layout of the elements within an area described by the view configuration file on a screen display, a style configuration file that defines a style of the elements, a graphical user interface engine configured to process the style configuration file, the layout configuration file, and the view configuration file and render the elements onto the screen display, and an interface that allows changes to be made to the configuration files by editing a language representative of the format of the configuration files.