Data-Driven Hierarchical Page Management via Model and Controller Files
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing methods for creating user interfaces in computer systems are labor-intensive and time-consuming, requiring developers to manually manage and link settings with UI controls, leading to inefficiencies in software development and maintenance.
Innovation Solution
A data-driven hierarchical page management system using model files and controller files, where data descriptions are formatted as collections of dictionaries, allowing for efficient presentation and management of settings across multiple hierarchical pages without the need for extensive code modifications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If developers manually manage and link settings with UI controls using traditional methods, then each setting can be individually maintained, but the process becomes labor-intensive and time-consuming
Solution Approach 1:
The patent segments the UI configuration into separate data files (XML or JSON) that contain setting definitions, UI control definitions, and their associations. This separation allows independent maintenance of data structures without modifying source code, resolving the contradiction by making the system easier to manufacture while reducing time loss through automated parsing and generation.
Solution Approach 2:
The patent creates template-based data files that can be copied and reused across different UI configurations. Once a setting or control template is defined, it can be referenced multiple times without recreating the same code structures, significantly reducing development time while maintaining ease of modification through template updates.
2Adaptability or versatility
If developers create new source code for each setting and UI control, then individual control is maintained, but code modification becomes necessary for every change
Solution Approach 1:
The patent extracts setting definitions and UI control configurations from source code into external data files (XML/JSON). This extraction allows the system to maintain high adaptability through easy data file modification while reducing source code complexity, as the core code only needs to parse and process the standardized data structures without containing specific setting logic.
Solution Approach 2:
The patent introduces data files (XML or JSON) as intermediaries between the settings definitions and the source code implementation. These intermediary files serve as a configuration layer that provides adaptability through editable content while keeping the source code simple and generic, resolving the contradiction between adaptability and code complexity.
3Reliability
If individual settings are maintained separately with dedicated code, then each setting can be independently managed, but the overall system becomes difficult to maintain
Solution Approach 1:
The patent merges the management of multiple individual settings into a unified data file structure (XML or JSON) that maintains hierarchical organization. This merging approach preserves the reliability of individual setting management through structured data elements while dramatically improving ease of repair, as all settings can be maintained and updated through a single standardized interface rather than scattered code modifications.
Data Source
AI summary
A method of managing data includes generating a model file containing descriptions of the data, wherein the descriptions of the data in the model file are formatted as a collection of dictionaries, wherein the descriptions of the data are divided into multiple groups that are associated with multiple hierarchical pages, and wherein the multiple groups associated with the multiple hierarchical pages are listed in the model file in a flat structure, and generating a controller file that, when executed by a processor, causes the processor to interpret the model file and present the data in the multiple hierarchical pages to a user, wherein the controller file refers to one of the multiple groups in the model file, wherein the controller file is re-used to interpret the multiple groups in the descriptions of the data and present the data in the multiple hierarchical pages.