Diagram Style Extensibility via Text File Editing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional systems for applying styles to complex diagrams in applications like word processing and presentation software do not allow developers to add style descriptions dynamically, limiting the ability to customize future layouts that do not exist at the time of creation.

Innovation Solution

The implementation of style extensibility in diagrams through editing text files, using a structured data model to render items and their relationships, where style properties are assigned to key shapes via style labels, and layout definitions are employed to create a presentation model from a semantic model, allowing for consistent look-and-feel across different layouts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional style application systems are used, then style consistency is maintained, but developers cannot add style descriptions dynamically for future layouts

Engineering Contradiction:
ImproveAbility to add style descriptions dynamicallyVSAvoidSystem complexity for managing styles
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the style management system into separate style definition files that can be independently created, edited, and maintained. This allows developers to add style descriptions for future layouts without modifying the core application code, thereby improving adaptability while keeping the system manageable through file-based organization.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent enables preliminary definition of styles in text files before the actual layouts are created. Developers can prepare style descriptions in advance, and when future layouts are needed, these pre-defined styles can be automatically applied, eliminating the need for dynamic additions during runtime and maintaining system simplicity.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If styles are tied to specific layouts during setup, then layout-specific customization is achieved, but styles cannot be applied to future layouts that do not exist yet

Engineering Contradiction:
ImproveStyle applicability to future layoutsVSAvoidTime to recreate styles for new layouts
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent creates universal style definitions in text files that are not bound to any specific layout. These style definitions can be applied to any layout that matches the defined criteria, including future layouts that do not yet exist. This multi-functional approach eliminates the need to recreate styles for each new layout, saving time and improving adaptability.

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

3Adaptability or versatility

If style properties are hardcoded in the application, then consistent rendering is achieved, but customization flexibility is limited

Engineering Contradiction:
ImproveCustomization flexibilityVSAvoidConfiguration management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces text files as an intermediary layer between the application code and style definitions. This intermediary allows style properties to be customized by editing text files rather than modifying the application code, providing flexibility while maintaining consistent rendering through the structured format of the text files and automated parsing by the application.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11301635B2Style extensibility applied to a group of shapes by editing text files
Publication Date: 2022.04.12 MICROSOFT TECHNOLOGY LICENSING LLC
  • US11301635B2 patent drawing
  • US11301635B2 patent drawing
  • US11301635B2 patent drawing

AI summary

Style extensibility is provided to shapes in a diagram by editing text files. A structured data model is used to render the diagram representing items provided by the user in a text-based format such as a bulleted list. A style engine determines style properties for style labels assigned to key shapes of the diagram. Style properties include features associated with the shapes and their content that preserve an overall look-and-feel of the diagram. Color scheme(s) are also provided through the style labels. A layout engine uses layout definitions based on user input and default parameters along with style label assignments to render a presentation model. Style properties may be modified and new styles added after the diagram is rendered.