DATA-DRIVEN VISUALIZATION TRANSFORMATION

• US 20100324867A1
• Filed: 06/19/2009
• Published: 12/23/2010
• Est. Priority Date: 06/19/2009
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Rubin, Darryl E., Mital, Vijay, Green, David G.
• Granted Patent: US 8,531,451 B2
• Time in Patent Office: Days
• US Class Current: 703/1
• 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 rendering using a plurality of view components, each having corresponding rendering logic that uses data provided as input parameters to the view components, the method comprising:

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

an act of detecting a transition event; and

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

2. The method in accordance with claim 1, wherein the corresponding plurality of data-driven view components used to render the first data-driven scene are the same as the data-driven view components used to render the second data-driven scene, but the corresponding data applied to the corresponding plurality of data-driven view components for the first data-driven scene is different than the corresponding data applied to the corresponding plurality of data-driven view components for the second data-driven scene.

3. The method in accordance with claim 1, wherein the corresponding plurality of data-driven view components used to render the first data-driven scene are different than the data-driven view components used to render the second data-driven scene, but the corresponding data applied to the corresponding plurality of data-driven view components for the first data-driven scene is the same as the corresponding data applied to the corresponding plurality of data-driven view components for the second data-driven scene.

4. The method in accordance with claim 1, wherein the corresponding plurality of data-driven view components used to render the first data-driven scene are different than the data-driven view components used to render the second data-driven scene, and the corresponding data applied to the corresponding plurality of data-driven view components for the first data-driven scene is different than the corresponding data applied to the corresponding plurality of data-driven view components for the second data-driven scene.

5. 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 act of rendering the first data-driven scene.

6. The method in accordance with claim 5, wherein the corresponding data applied to the corresponding plurality of data-driven view components for the first data-driven scene is different than the corresponding data applied to the corresponding plurality of data-driven view components for the second data-driven scene.

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

8. The method in accordance with claim 7, wherein the corresponding data applied to the corresponding plurality of data-driven view components for the first data-driven scene is different than the corresponding data applied to the corresponding plurality of data-driven view components for the second data-driven scene.

9. 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.

10. The method in accordance with claim 1, wherein the first 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 corresponding data being applied to a corresponding plurality of data-driven view components.

11. The method in accordance with claim 10, wherein the first transition event is a first transition event, 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 corresponding data being applied to a corresponding plurality of data-driven view components.

12. A physical computer program product comprising one or more physical computer-readable media having 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 rendering using a plurality of view components, each having corresponding rendering logic that uses data provided as input parameters to the view components, the method comprising:

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

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

an act of detecting a transition event;

an act of providing a second set of data to a second plurality of view components;

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

13. The physical computer program product in accordance with claim 12, wherein the first set of data is the same as the second set of data.

14. The physical computer program product in accordance with claim 12, wherein the first set of data is completely different than the second set of data.

15. The physical computer program product in accordance with claim 12, wherein only a portion of the first set of data is the same as the portion of the second set of data.

16. The physical computer program product in accordance with claim 12, wherein the first plurality of view components is the same as the second plurality of view components.

17. The physical computer program product in accordance with claim 12, wherein the first plurality of view components is different than the second plurality of view components.

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

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

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

an act of detecting a first transition event;

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

an act of detecting a second transition event after the second data-driven scene is rendered; 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 corresponding data being applied to a corresponding plurality of data-driven view components, wherein either the corresponding plurality of data-driven view components used to render the third data-driven scene is different than the corresponding 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 second data-driven scene.

20. A method in accordance with claim 19, further comprising:

an act of detecting a third transition event after the third data-driven scene is rendered; 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 corresponding data being applied to a corresponding plurality of data-driven view components, wherein either the corresponding plurality of data-driven view components used to render the fourth data-driven scene is different than the corresponding plurality of data-driven components used to render the third data-driven scene, or the corresponding data used to render the fourth data-driven scene is different than the third data-driven scene.