UI Framework Decoupling Rich Media Source Code

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional approaches to producing and modifying rich media content require collaborative effort between designers and programmers, necessitating repetitive changes to source code and recompilation, which is burdensome and limits flexibility, especially when adapting content for multiple graphics environments.

Innovation Solution

A user interface framework and method that allows dynamic updating of rich media content without modifying existing source code, using a content management system and UI layout feed to manage display assets across multiple platforms, decoupling designer and programmer contributions and enabling independent modifications by designers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional approaches are used to produce and modify rich media content, then collaborative effort between designers and programmers ensures comprehensive control, but the process requires repetitive source code changes and recompilation, increasing time and resource costs

Engineering Contradiction:
Improvecontrol over content productionVSAvoidtime for source code changes and recompilation
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system segments the content production process into distinct layers: the presentation layer (XSLT stylesheets and display asset definitions) is separated from the source code layer. This allows designers to modify display assets and styling without touching or recompiling the underlying source code, eliminating iterative recompilation cycles while maintaining control over the final output.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

An intermediary system comprising XSLT stylesheets and display asset definitions is introduced between the source code and the final rich media output. This intermediary layer allows designers to control the presentation and modification of content without requiring direct access to or modification of the source code, thereby avoiding recompilation requirements while preserving comprehensive control.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If designers anticipate full menu of display assets prior to coding, then source code can be generated efficiently, but flexibility to modify display assets later is reduced

Engineering Contradiction:
Improvesource code generation efficiencyVSAvoidflexibility to modify display assets
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The system implements dynamics by making display asset definitions mutable and separable from the source code. Display assets are defined in external files that can be modified at any time without regenerating source code. The XSLT transformation process dynamically adapts to these changes, allowing the system to maintain high productivity during initial generation while gaining flexibility for later modifications.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system performs preliminary action by generating source code once with anticipated display assets, but then enables subsequent modifications through the intermediary display asset definitions. This preliminary generation maintains productivity, while the decoupled asset definitions provide adaptability for future changes without requiring code regeneration.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If source code is edited to incorporate new display assets, then content modifications can be made, but recompilation is required, increasing resource costs

Engineering Contradiction:
Improveability to modify contentVSAvoidrecompilation process complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system extracts display asset definitions from the source code into separate, externally manageable files. This extraction allows content modifications to be made by editing these external asset definitions rather than modifying the source code itself, thereby enabling ease of operation while completely avoiding the complexity of recompilation processes.

Inventive Principle:
Principle #2Taking out (Extraction)

4Adaptability or versatility

If rich media content is provided across multiple graphics environments, then broader consumer access is achieved, but duplication of content production resources is required

Engineering Contradiction:
Improvecross-platform availabilityVSAvoidresource commitments for multiple versions
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The system implements universality by creating a single source code base that can be transformed into multiple graphics environments through the intermediary XSLT and display asset layer. This single source serves multiple functions across different platforms, eliminating the need to produce separate content versions for each environment while maintaining broad cross-platform availability.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS8185837B2User interface framework and method for utilizing same
Publication Date: 2012.05.22 DISNEY ENTERPRISES INC
  • US8185837B2 patent drawing
  • US8185837B2 patent drawing
  • US8185837B2 patent drawing

AI summary

There is presented a user interface (UI) framework and systems and methods for its use. Such a system comprises a content server and a rich media content generated by a compiling of a rich media source code, wherein the rich media content is hosted by the content server. The rich media content includes a first embedded graphics environment configured to present display assets of the rich media content, and a first UI framework ported to the first embedded graphics environment, the first UI framework configured to interact with the first embedded graphics environment to modify the display assets of the rich media content in response to data received from a UI layout feed. The first UI framework is configured to modify the display assets of the rich media content without requiring modifications to the rich media source code or recompiling of the rich media source code.