Compiled Language Code Integration in Markup Files

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current user interface frameworks face inefficiencies due to runtime interpretation of interpreted script languages, which increases processing overhead and memory usage, and require developers to manage separate native compiled code files, leading to complexity in updating or changing UI elements.

Innovation Solution

Integrating compiled language code directly with markup language code, using a parsing component to extract and compile the compiled language code into binary form, which is then run alongside the markup language code within a unified runtime system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If interpreted script language is used at runtime, then code can be specified in line with markup language, but processing overhead and memory usage increase

Engineering Contradiction:

Improvecode integrationVSAvoidprocessing overhead

Core Design Contradiction:

Ease of operationVSUse of energy by moving object

Solution Approach 1:

The patent applies preliminary action by compiling the script language code into native code during the build process before runtime. This pre-compilation eliminates the need for runtime interpretation, thereby reducing processing overhead and memory usage while maintaining the integrated code specification advantage.

Inventive Principle:

Principle #10Preliminary action

2Use of energy by moving object

If native compiled language code is used, then processing efficiency improves, but code management complexity increases due to separate files

Engineering Contradiction:

Improveprocessing efficiencyVSAvoidcode management

Core Design Contradiction:

Use of energy by moving objectVSDevice complexity

Solution Approach 1:

The patent merges the script language code with the markup language code into a single file structure. The parsing component extracts the script code from within the markup file, allowing developers to specify and maintain both types of code together in one location, thereby reducing code management complexity while preserving processing efficiency.

Inventive Principle:

Principle #5Merging (Combining)

3Adaptability or versatility

If script language is interpreted at runtime, then code flexibility improves, but memory usage increases

Engineering Contradiction:

Improvecode flexibilityVSAvoidmemory usage

Core Design Contradiction:

Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

By pre-compiling script language code into native code during the build process, the patent eliminates the need to load and interpret script code at runtime. This reduces memory usage significantly while maintaining code flexibility through the integrated file structure that allows easy modification of script code within the markup file.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS9158505B2Specifying compiled language code in line with markup language code

Publication Date: 2015.10.13 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

Compiled language code is specified in line with markup language code. A parsing component parses the code to extract the compiled language code and a compiler compiles it into binary form. The compiled code and the markup language code are provided to a runtime system.