Data-driven visualization transformation

• US 8,531,451 B2
• Filed: 06/19/2009
• Issued: 09/10/2013
• Est. Priority Date: 06/19/2009
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Mital, Vijay, Rubin, Darryl E., Green, David G.
• Primary Examiner(s): Nguyen, Kimbinh T
• Application Number:
  US12/488,247
• Publication Number:
  US 20100324867A1
• Time in Patent Office: 1,544 Days
• Field of Search: 345/418, 345/419, 345/630, 345/473, 463/31, 703/1, 706/45
• US Class Current: 345/419
• CPC Class Codes: G06F 30/00 Computer-aided design [CAD]

Abstract

The rendering of sequential data-driven scenes. Each data-driven scene is constructed using a plurality of view components, each receiving data into its input parameters, and using construction logic to formulate a rendering of corresponding visual item(s). When a transition even is detected, the data-driven scene changes from one scene to the next. For instance, the transition might occur by changing any one or more of the following: changing the data that is applied to the view components, 2) changing the set of view components, 3) changing the dimension set, or 4) changing one or more geometries used to construct the scene. Thus, data-driven scenes may be presented sequentially.

Claims

1. A method for rendering a plurality of sequential data-driven scenes on a display, each scene being rendered using a plurality of view components, each view component having corresponding rendering logic that uses data provided as input parameters to the view component to render a visual item in the scene, the method comprising:

an act of rendering a first data-driven scene on a display, the first data-driven scene being driven by first data being applied to a first plurality of data-driven view components;

an act of detecting a type of a transition event selected from among visuals transformation, data transformation, coordinate system transformation and target world transformation; and

based on the detected type of the transition event, an act of rendering a second data-driven scene on the display using visuals transformation, data transformation, coordinate system transformation, or target world transformation, the second data-driven scene being different from the first data-driven scene, including;

when the detected type of the transition event is visuals transformation, the second data-driven scene is driven by the first data also being applied to a second plurality of data-driven view components, wherein the first plurality of data-driven view components used to render the first data-driven scene are different than the second plurality of data-driven view components used to render the second data-driven scene, but the first data applied to the first plurality of data-driven view components for the first data-driven scene is the same as the first data applied to the second plurality of data-driven view components for the second data-driven scene;

when the detected type of the transition event is data transformation, the second data-driven scene is driven by second data being applied to the first plurality of data-driven view components, wherein the second data differs from the first data in one or more of variable identity, variable value, or variable to view component binding;

when the detected type of the transition event is coordinate system transformation, the second data-driven scene is driven by the first data being applied to the first plurality of data-driven view components, but using a different coordinate system as compared to the act of rendering the first data-driven scene; and

when the detected type of the transition event is target world transformation, the second data-driven scene is driven by the first data being applied to the first plurality of data-driven view components, but using a different geometry as compared to the act of rendering the first data-driven scene.

2. The method in accordance with claim 1, wherein the act of rendering the second data-driven scene is performed using a different set of dimensions as compared to the act of rendering the first data-driven scene.

3. The method in accordance with claim 1, wherein the act of detecting a transition event comprises an act of detecting user interaction with the first data-driven scene.

4. The method in accordance with claim 1, wherein the transition event is a first transition event, the method further comprising:

an act of detecting a second transition event; and

in response to detecting the second transition event, an act of rendering a third data-driven scene on a display, the third data-driven scene being driven by the first data being applied to a third plurality of data-driven view components.

5. The method in accordance with claim 4, the method further comprising:

an act of detecting a third transition event; and

in response to detecting the third transition event, an act of rendering a fourth data-driven scene on a display, the fourth data-driven scene being driven by the first data being applied to a fourth plurality of data-driven view components.

10. The method in accordance with claim 1, wherein the detected type of the transition event is visuals transformation.

11. The method in accordance with claim 1, wherein the detected type of the transition event is data transformation.

12. The method in accordance with claim 1, wherein the detected type of the transition event is coordinate system transformation.

13. The method in accordance with claim 1, wherein the detected type of the transition event is target world transformation.

6. A physical computer program product comprising one or more physical storage devices having stored thereon computer-executable instructions that, when executed by one or more processors of a computing system, cause the computing system to perform a method for rendering a plurality of sequential data-driven scenes on a display, each scene being rendered using a plurality of view components, each view component having corresponding rendering logic that uses data provided as input parameters to the view component to render a visual item in the scene, the method comprising:

an act of providing first data to a first plurality of view components;

an act of executing logic corresponding to the first plurality of view component and using the data to thereby render a first data-driven scene;

an act of detecting a type of a transition event selected from among visuals transformation, data transformation, coordinate system transformation and target world transformation;

based on the detected type of the transition event, an act of rendering a second data-driven scene on the display using visuals transformation, data transformation, coordinate system transformation, or target world transformation, the second data-driven scene being different from the first data-driven scene, including;

when the detected type of the transition event is visuals transformation;

an act of providing the first data to a second plurality of view components; and

an act of executing logic corresponding to the second plurality of view components and using the first data to thereby render the second data-driven scene, wherein the first plurality of data-driven view components used to render the first data-driven scene are different than the second plurality of data-driven view components used to render the second data-driven scene

when the detected type of the transition event is data transformation;

an act of providing second data to the first plurality of data-driven view components, wherein the second data differs from the first data in one or more of variable identity, variable value, or variable to view component binding; and

an act of executing logic corresponding to the first plurality of view components and using the second data to thereby render the second data-driven scene;

when the detected type of the transition event is coordinate system transformation;

an act of providing the first data to the first plurality of view components; and

an act of executing logic corresponding to the first plurality of view components and using the first data to thereby render the second data-driven scene, but using a different coordinate system as compared to the act of rendering the first data-driven scene; and

when the detected type of the transition event is target world transformation;

an act of providing the first data to the first plurality of view components; and

an act of executing logic corresponding to the first plurality of view components and using the first data to thereby render the second data-driven scene, but using a different geometry as compared to the act of rendering the first data-driven scene.

7. The physical computer program product in accordance with claim 6, wherein a portion of the first plurality of view components is the same as the second plurality of view components.

8. A computer system, comprising:

one or more processors; and

one or more computer-readable media storing computer-executable instructions that, when executed by the one or more processors, cause the computer system render a plurality of sequential data-driven scenes on a display, each scene being rendered using a plurality of view components, each view component having corresponding rendering logic that uses data provided as input parameters to the view component to render a visual item in the scene, including the following;

render a first data-driven scene on a display, the first data-driven scene being driven by corresponding first data being applied to a first plurality of data-driven view components;

detect a type of a transition event selected from among visuals transformation, data transformation, coordinate system transformation and target world transformation; and

based on the detected type of the first transition event, render a second data-driven scene on the display using visuals transformation, data transformation, coordinate system transformation, or target world transformation, the second data-driven scene being different from the first data-driven scene, including;

when the detected type of the transition event is visuals transformation, the second data-driven scene is driven by the first data being applied to a second plurality of data-driven view components, wherein the second plurality of data-driven view components used to render the second data-driven scene is different than the first plurality of data-driven components used to render the first data-driven scene, but the first data used to render the second data-driven scene is the same as the first data used to render the first data-driven scene;

when the detected type of the transition event is data transformation, the second data-driven scene is driven by second data being applied to the first plurality of data-driven view components, wherein the second data differs from the first data in one or more of variable identity, variable value, or variable to view component binding;

when the detected type of the transition event is coordinate system transformation, the second data-driven scene is driven by the first data being applied to the first plurality of data-driven view components, but using a different coordinate system as compared to the act of rendering the first data-driven scene; and

when the detected type of the transition event is target world transformation, the second data-driven scene is driven by the first data being applied to the first plurality of data-driven view components, but using a different geometry as compared to the act of rendering the first data-driven scene.

9. A computer system in accordance with claim 8, further comprising computer-executable instructions that, when executed by the one or more processors, cause the computer system to:

detect a second transition event after the second data-driven scene is rendered; and

in response to detecting the second transition event, render a third data-driven scene on a display, the third data-driven scene being driven by corresponding data being applied to a third plurality of data-driven view components, wherein either the third plurality of data-driven view components used to render the third data-driven scene is different than the second plurality of data-driven components used to render the second data-driven scene, or the corresponding data used to render the third data-driven scene is different than the corresponding data used to render the second data-driven scene.