XML-Based UI Gadget Rendering System

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current user interface development platforms for desktop applications lack efficiency in generating and rendering user interfaces, as they require manual coding and do not effectively utilize XML-based definitions for gadget elements, styles, and behaviors, leading to complex and time-consuming development processes.

Innovation Solution

A system that uses XML-based gadget definitions, style definitions, and scene files to generate an object model, with a parser to interpret these definitions, a layout engine to determine the interface layout, and a rendering engine to render the user interface, including features like event handling and animation, to streamline the development and rendering of user interfaces.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If manual coding is used for user interface development, then developers have full control over the code, but the development process becomes complex and time-consuming

Engineering Contradiction:
Improveease of UI developmentVSAvoiddevelopment time
Core Design Contradiction:
Ease of manufactureVSLoss of time

Solution Approach 1:

The patent uses XML-based gadget definitions as templates that define reusable UI components. These gadget definitions serve as copyable blueprints that can be instantiated multiple times with different parameters, eliminating the need to manually code each UI element from scratch and significantly reducing development time while maintaining control through the XML configuration

Inventive Principle:
Principle #26Copying

2Productivity

If XML-based gadget definitions are not utilized, then the development process remains simple to understand, but the efficiency of generating and rendering user interfaces is low

Engineering Contradiction:
ImproveUI generation efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the user interface into independent, reusable gadget components defined in separate XML files. Each gadget is a self-contained unit with its own definition, style, and behavior. This segmentation allows the system to process and render UI elements independently, improving generation efficiency while keeping each individual gadget definition simple and manageable

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary actions by pre-defining gadget definitions, styles, and behaviors in XML files before actual UI generation. The parser pre-processes these definitions into an object model that the rendering engine can efficiently use. This preliminary preparation work separates the complexity of definition creation from the speed-critical rendering phase, improving overall productivity

Inventive Principle:
Principle #10Preliminary action

3Productivity

If automated parsing and rendering processes are not implemented, then the system architecture remains simple, but developer productivity is reduced

Engineering Contradiction:
Improvedeveloper productivityVSAvoidsystem architecture complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary parser that translates XML-based gadget definitions into an internal object model, and a rendering engine that converts the object model into rendered UI. This intermediary layer automates the complex translation and rendering processes, significantly improving developer productivity by eliminating manual coding while keeping the architecture manageable through clear separation of concerns between the parser, object model, and renderer

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9910567B2Providing a user interface
Publication Date: 2018.03.06 VERIZON PATENT & LICENSING INC
  • US9910567B2 patent drawing
  • US9910567B2 patent drawing
  • US9910567B2 patent drawing

AI summary

A system for providing a user interface includes a gadget definition, a style definition, and a scene file. The gadget definition includes one or more XML-based gadget definition tags defining a gadget element and the style definition includes one or more XML-based style definition tags defining one or more style attributes to be applied to the gadget element. The scene file is an XML-based document that includes a gadget element tag that specifies the gadget element. The system further includes a parser to parse the scene file, the style definition, and the gadget definition, and to generate an object that includes a gadget object corresponding to the gadget element. The system also includes a layout engine to determine, based on the object model, a layout of the user interface, and a rendering engine to render, based on the determined layout, the user interface including the gadget element.