EXECUTING A COMPOSITED APPLICATION

• US 20130139072A1
• Filed: 11/28/2011
• Published: 05/30/2013
• Est. Priority Date: 11/28/2011
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Kaza, Akhilesh, Cseri, Istvan, Liu, Alan Chun Tung, Michail, Ashraf Ayman, Bleisch, Paul Lawrence
• Application Number:
  US13/305,333
• Publication Number:
  US 20130139072A1
• Time in Patent Office: Days
• US Class Current: 715/760
• CPC Class Codes: G06F 8/38 for implementing user interfaces
• CPC Class Codes: G06F 9/45508 Runtime interpretation or emulation, e g. emulator loops, bytecode interpretation

Abstract

The present invention extends to methods, systems, and computer program products for enabling the development and execution of applications that employ a composited application model. A composited application includes components that are to be executed in different runtimes. Accordingly, an application developer can leverage different runtimes within a single application. A managing runtime is used to manage the various runtimes used by a composited application. The managing runtime performs input redirection to route user input to the appropriate runtime and output compositing to composite each runtime'"'"'s user interface components into a single seamless scene.

Claims

1. At a computer system, the computer system having a plurality of runtimes, the plurality of runtimes including a managing runtime and one or more other runtimes, each runtime configured to execute a portion of an application that includes a different portion of executable code pertaining to each runtime, a method of directing user input to a user interface of the application to the appropriate runtime from among the plurality of runtimes during execution of the application, the method comprising:

executing an application that includes a plurality of portions of executable code that each pertain to a different runtime, wherein executing the application includes presenting a user interface for the application, wherein at least two of the plurality of runtimes each executes the corresponding portion of executable code to generate a different portion of the user interface;

receiving user input at one of the different portions of the user interface;

delivering the user input to the managing runtime;

the managing runtime identifying a runtime from among the different runtimes that is to receive the user input; and

routing the user input to the identified runtime.

2. The method of claim 1, wherein the different runtimes include two or more of an HTML runtime, an XNA runtime, and a Silverlight runtime.

3. The method of claim 2, wherein the managing runtime is a XAML runtime.

4. The method of claim 3, wherein the user interface is structured as a XAML tree that contains a portion generated by at least one of:

the XNA runtime, the HTML runtime, or the Silverlight runtime.

5. The method of claim 1, wherein the managing runtime includes an HTML framework, an XNA framework, or a Silverlight framework.

6. The method of claim 1, wherein the at least two of the plurality of runtimes each executing the corresponding portion of executable code to generate a different portion of the user interface comprises each of the at least two runtimes generating rendering instructions for rendering the corresponding different portion, and wherein presenting a user interface for the application comprises compositing the rendering instructions for rendering each of the corresponding different portions into a single output that defines the user interface.

7. The method of claim 1, wherein presenting a user interface for the application includes creating an indication of the location of each of the different portions of the user interface along with an identification of which runtime generated the different portion.

8. The method of claim 1, wherein the managing runtime indentifying a runtime from among the plurality of different runtimes that is to receive the user input comprises determining which runtime generated the portion of the user interface where the user input was received.

9. The method of claim 8, wherein the managing runtime identifying a runtime from among the plurality of different runtimes that is to receive the user input by determining which runtime generated the portion of the user interface where the user input was received comprises the managing runtime determining that the managing runtime generated the portion of the user interface where the user input was received.

10. The method of claim 1, wherein the managing runtime identifying a runtime from among the plurality of different runtimes that is to receive the user input comprises sending the user input to each runtime until a runtime acknowledges having the ability to respond to the user input.

11. The method of claim 1, wherein the managing runtime identifying a runtime from among the plurality of different runtimes that is to receive the user input comprises identifying two or more runtimes that are to receive the user input;

and wherein routing the user input to the identified runtime comprises routing the user input to each of the two or more identified runtimes.

12. The method of claim 1, further comprising:

the identified runtime modifying the corresponding portion of the user interface; and

displaying the modified portion within the user interface.

13. At a computer system, the computer system having a plurality of runtimes, the plurality of runtimes including a managing runtime and one or more other runtimes, each runtime configured to execute a portion of an application that includes a different portion of executable code pertaining to each runtime, a method of at least two runtimes interoperating to present a user interface for an application, the method comprising:

executing an application that includes a plurality of portions of executable code that each pertain to a different runtime, wherein executing the application includes presenting a user interface for the application, wherein at least two of the plurality of runtimes each execute the corresponding portion of executable code to generate a different portion of the user interface;

detecting a modification to a first portion of the user interface corresponding to a first runtime of the plurality of runtimes;

determining, by the managing runtime, that a second portion of the user interface corresponding to a second runtime of the plurality of runtimes is to be modified based on the modification to the first portion of the user interface; and

sending, by the managing runtime, a notification to the second runtime to indicate that the second portion of the user interface is to be modified in accordance with the modification to the first portion of the user interface.

14. The method of claim 13 wherein either the first or the second runtime is the managing runtime.

15. The method of claim 13 wherein the managing runtime is a XAML runtime, and wherein the first and second runtimes are each a different runtime from among an HTML runtime, an XNA runtime, and a Silverlight Runtime.

16. The method of claim 13, wherein the at least two of the plurality of runtimes each executing the corresponding portion of executable code to generate a different portion of the user interface comprises each of the at least two runtimes generating rendering instructions for rendering the corresponding different portion, and wherein presenting a user interface for the application comprises compositing the rendering instructions for rendering each of the corresponding different portions into a single output that defines the user interface.

17. The method of claim 13 wherein the second portion of the user interface is layered within the first portion of the user interface, and wherein the modification to the first portion of the user interface comprises the movement of an element within the first portion of the user interface.

18. The method of claim 13 wherein the notification comprises one or more of:

an identification of the modification to the first portion of the user interface;

or

instructions regarding how the second portion of the user interface is to be modified.

19. The method of claim 13 further comprising:

receiving, by the managing runtime, rendering instructions defining updated first and second portions from the first and second runtimes respectively; and

presenting the user interface with the updated first and second portions.

20. At a computer system, the computer system having a managing runtime comprising a XAML runtime and a plurality of managed runtimes comprising an HTML runtime, an XNA runtime, and a Silverlight runtime, each runtime configured to execute a portion of an application that includes a different portion of executable code pertaining to each runtime, a method of directing user input to a user interface of the application to the appropriate runtime from among the plurality of runtimes during execution of the application, the method comprising:

receiving an application that includes an HTML runtime, an XNA runtime, and a Silverlight runtime, the HTML, XNA, and Silverlight runtimes comprising HTML, XNA, and Silverlight code respectively that is executed by the HTML, XNA, and Silverlight runtimes respectively to each generate a portion of a user interface of the application;

executing the application including receiving, by the XAML runtime, rendering instructions from each runtime for generating a corresponding portion of the user interface of the application;

outputting, by the XAML runtime, a single output scene of the user interface, the single output scene including each of the portions generated by the HTML, XNA, and Silverlight runtimes;

receiving user input at one of the different portions of the user interface;

delivering the user input to the XAML runtime;

the XAML runtime identifying a runtime from among the different runtimes that is to receive the user input; and

routing the user input to the identified runtime.