Vector Graphics Engine Template Data Binding

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current technologies for dynamically generating vector graphics are cumbersome and costly due to their granular nature, requiring low-level API calls and specific programming skills, limiting their use in creating complex graphics without the need for time-intensive development processes.

Innovation Solution

A vector graphics engine that processes graphic and data templates to generate dynamic vector graphics using scalable vector graphic (SVG) standards, incorporating complex compound primitives and high-level layout constructs, allowing for programmatic manipulation and data binding without requiring low-level API calls.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If low-level API calls are used for vector graphics generation, then manufacturing precision is improved, but device complexity increases

Engineering Contradiction:
Improvegraphics generation precisionVSAvoidAPI complexity
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer (the vector graphics generation system with template engine and data binding mechanisms) between the user/high-level interface and the low-level drawing APIs. This intermediary automatically translates high-level template definitions into low-level API calls, maintaining graphics precision while shielding users from API complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces manual mechanical programming of low-level drawing operations with an automated system that uses templates, data binding, and declarative definitions. Instead of manually coding each drawing operation, the system automatically generates the necessary API calls based on template definitions and data sources.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Manufacturing precision

If low-level API calls are used for vector graphics generation, then manufacturing precision is improved, but loss of time increases

Engineering Contradiction:
Improvegraphics generation precisionVSAvoiddevelopment time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The patent implements preliminary action through template pre-definition and compilation. Templates are defined once, compiled into executable forms, and then reused multiple times with different data bindings. This eliminates the need to repeatedly write and debug low-level drawing code for similar graphics, significantly reducing development time while maintaining precision through the compiled template logic.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent enables copying and reusing of template definitions across multiple graphics generation tasks. Once a template is created and validated, it can be instantiated multiple times with different data bindings, allowing rapid generation of consistent graphics without re-implementing the underlying drawing logic each time.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If programmatic manipulation of XML is used for vector graphics, then adaptability is improved, but device complexity increases

Engineering Contradiction:
Improvegraphics manipulation flexibilityVSAvoidprogramming complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent replaces manual XML manipulation mechanics with an automated data binding system. Instead of requiring programmers to manually parse, modify, and regenerate XML vectors graphics, the system automatically binds data to template definitions and generates the necessary XML output, maintaining adaptability while reducing programming complexity.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The patent introduces a data binding intermediary layer that sits between data sources and XML vector graphics output. This intermediary automatically handles the complexity of XML manipulation by translating data bindings into appropriate XML structure changes, allowing developers to work with high-level data concepts rather than low-level XML syntax.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Manufacturing precision

If manual low-level API implementation is used, then manufacturing precision is improved, but ease of manufacture deteriorates

Engineering Contradiction:
Improvegraphics generation precisionVSAvoiddevelopment ease
Core Design Contradiction:
Manufacturing precisionVSEase of manufacture

Solution Approach 1:

The patent replaces manual low-level API implementation with an automated template-driven system. The system automatically generates precise drawing operations from template definitions and data bindings, eliminating the need for manual API coding while maintaining the precision that comes from carefully crafted drawing logic embedded in the templates.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The patent introduces an intermediary template system that translates high-level design intentions into precise low-level drawing operations. This intermediary maintains manufacturing precision by preserving the detailed drawing logic in templates while making the development process easier through declarative template definitions and automatic data binding.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10008009B1Method for generating dynamic vector graphics
Publication Date: 2018.06.26 EMC IP HLDG CO LLC
  • US10008009B1 patent drawing
  • US10008009B1 patent drawing
  • US10008009B1 patent drawing

AI summary

A method of dynamically generating a graphic includes receiving, at a vector graphics engine loaded on a server system, graphic template input; receiving, at the vector graphics engine loaded on the server system, data template input; and generating, at the server system, code in a standard format representative of a vector graphic. The generating includes identifying a special tag associated with the vector graphics engine, converting code associated with this tag from a first format associated with the vector graphics engine to a second standardized format, and binding data content based on the received data template input to graphic content based on the received graphic template input.