Declarative Wizard Framework for User Interface Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

As applications become larger and more complex, managing and designing numerous user interface mechanisms becomes unwieldy, requiring a more efficient approach to create and maintain user interfaces.

Innovation Solution

A declarative 'story' is used to define user interfaces, which is processed by a wizard engine to create interactive interfaces using user interface containers and styles, allowing for the creation of complex interfaces with minimal programming effort and consistent 'look and feel' across multiple interfaces.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If individual user interface mechanisms are designed and programmed for each function, then the user interface can be customized to specific needs, but the number of mechanisms becomes unwieldy to design and manage as applications grow larger

Engineering Contradiction:
Improveuser interface customizationVSAvoidnumber of user interface mechanisms
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the user interface into reusable components: templates define the structure and layout, styles define the appearance, and data sources provide the content. This segmentation allows complex interfaces to be built from modular pieces without creating unwieldy custom mechanisms for each function.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a universal framework where templates, styles, and data sources can be reused across multiple user interface mechanisms. A single template can serve multiple functions by combining different styles and data sources, eliminating the need to design separate mechanisms for each purpose.

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

2Adaptability or versatility

If numerous user interface mechanisms are created for different functions, then specific functionality can be achieved, but the mechanisms become difficult to maintain and update

Engineering Contradiction:
Improvefunctional capabilityVSAvoidmaintenance and updates
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

By separating interfaces into independent templates, styles, and data sources, the patent enables maintenance of individual components without affecting the entire system. Updates to a style or template automatically propagate to all using mechanisms, simplifying maintenance compared to modifying numerous separate mechanisms.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent uses templates as reusable copies that can be instantiated multiple times with different styles and data sources. This allows maintenance of a single template definition while it automatically updates all instances, eliminating the need to maintain multiple separate mechanisms.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If custom user interface mechanisms are programmed for each function, then specific functionality is achieved, but programming effort and time increase significantly

Engineering Contradiction:
Improvefunctional specificityVSAvoidprogramming effort
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent performs preliminary work by defining reusable templates, styles, and data source connections before creating specific user interface mechanisms. This preliminary structuring eliminates the need to program similar interface patterns repeatedly, reducing programming effort while maintaining functional specificity through composition.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent merges common functionality into shared templates and styles, then combines them in different configurations for specific functions. This merging eliminates redundant programming work while preserving functional specificity through flexible composition of reusable components.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS8869048B2Declarative and multi-mode wizard framework
Publication Date: 2014.10.21 MICROSOFT TECHNOLOGY LICENSING LLC
  • US8869048B2 patent drawing
  • US8869048B2 patent drawing
  • US8869048B2 patent drawing

AI summary

A user interface mechanism may be defined by a story from which a wizard engine may create a user interface. The engine may present the story using various user interface containers that define a layout and general functions of a user interface, along with styles that may define the ‘look and feel’ of the user interface. The story may define an action performed once data are collected from the user. The story may also define data passed to the action, as well as the data collected from a user. The story may further define translation routines or other actions that may be launched in response to receiving user action and used to generate data that may be passed to the action.