CROSS-PROCESS INTERFACE FOR NON-COMPATIBLE FRAMEWORKS

• US 20190310866A1
• Filed: 04/10/2018
• Published: 10/10/2019
• Est. Priority Date: 04/10/2018
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: CHINNATHAMBI, Kirupa, SEKSENOV, Kiril Nikolov, PETERS, Bradley James, DALTON, John-David Lewis
• Granted Patent: US 10,572,279 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 8/38 for implementing user interfaces
• CPC Class Codes: G06F 8/76 Adapting program code to run in a different environment; Porting
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications

Abstract

A computer device is provided that includes a processor configured to execute a first application configured for a first user interface framework, instantiate a host window of the first application using the first user interface framework, and execute a second application, that is out of process with the first application. The second application is configured for a second user interface framework that is incompatible with the first user interface framework. The processor is further configured to instantiate a hosted window of the second application using the second user interface framework, establish a cross-process interface between the first application and the second application configured to exchange rendering information between the hosted window and the host window, and cause the host window to display the rendering information from the hosted window within the host window on a display of the computer device.

Claims

1. A computer device comprising:

a processor configured to;

execute a first application configured for a first user interface framework;

instantiate a host window of the first application using the first user interface framework;

execute a second application, that is out of process with the first application, the second application configured for a second user interface framework that is incompatible with the first user interface framework;

instantiate a hosted window of the second application using the second user interface framework;

establish a cross-process interface between the first application and the second application configured to exchange rendering information between the hosted window and the host window; and

cause the host window to display the rendering information from the hosted window within the host window on a display of the computer device.

2. The computer device of claim 1, wherein the cross-process interface includes an out of process webview control configured to route navigation controls from the first application to the second application.

3. The computer device of claim 2, wherein the navigation controls are web application programming interfaces selected from the group consisting of navigation functions, script invoking functions, and navigation event callbacks.

4. The computer device of claim 1, wherein the processor is further configured to route user inputs from the area of the display associated with the hosted window to the second application directly.

5. The computer device of claim 1, wherein the second user interface framework is incompatible with the first user interface framework by having no native control in the first user interface framework to host an application of the second user interface framework.

6. The computer device of claim 1, wherein the first user interface framework is based on a first programming language and the second user interface framework is based on a second programming language, the first programming language being incompatible with the second programming language.

7. The computer device of claim 1, wherein to establish the cross-process interface, the processor is configured to establish a cross-process parenting between the host window and the hosted window.

8. The computer device of claim 7, wherein to establish the cross-process parenting, the host window is established as a parent of a bridge window and the bridge window is established as a parent of the hosted window, wherein the bridge window is controlled by a system process of an operating system executed by the processor.

9. The computer device of claim 1, wherein the first application is a stand-alone executable and the second application is an add-in.

10. The computer device of claim 1, wherein the first user interface framework is WIN32, and the second user interface framework is UNIVERSAL WINDOWS PLATFORM.

11. A method comprising:

at a computer device including a processor;

executing a first application configured for a first user interface framework;

instantiating a host window of the first application using the first user interface framework;

executing a second application, that is out of process with the first application, the second application configured for a second user interface framework that is incompatible with the first user interface framework;

instantiating a hosted window of the second application using the second user interface framework;

establishing a cross-process interface between the first application and the second application configured to exchange rendering information between the hosted window and the host window; and

causing the host window to display the rendering information from the hosted window within the host window on a display of the computer device.

12. The method of claim 11, wherein the cross-process interface includes an out of process webview control configured for routing navigation controls from the first application to the second application.

13. The method of claim 12, wherein the navigation controls are web application programming interfaces selected from the group consisting of navigation functions, script invoking functions, and navigation event callbacks.

14. The method of claim 11, the method further comprises routing user inputs from the area of the display associated with the hosted window to the second application directly.

15. The method of claim 11, wherein the second user interface framework is incompatible with the first user interface framework by having no native control in the first user interface framework to host an application of the second user interface framework.

16. The method of claim 11, wherein the first user interface framework is based on a first programming language and the second user interface framework is based on a second programming language, the first programming language being incompatible with the second programming language.

17. The method of claim 11, wherein establishing the cross-process interface includes establishing a cross-process parenting between the host window and the hosted window.

18. The method of claim 17, wherein establishing the cross-process parenting includes establishing the host window as a parent of a bridge window and establishing the bridge window as a parent of the hosted window, wherein the bridge window is controlled by a system process of an operating system executed by the processor.

19. The method of claim 11, wherein the first user interface framework is WIN32, and the second user interface framework is UNIVERSAL WINDOWS PLATFORM.

20. A computer device comprising:

a processor configured to;

execute a first application configured for a first user interface framework;

instantiate a host window of the first application using the first user interface framework;

execute a system hosting application that is configured to launch an out of process webview for a second application, the second application being configured for a second user interface framework that is incompatible with the first user interface framework;

instantiate a system bridge window of the system hosting application;

instantiate a hosted window of the second application using the second user interface framework;

establish a cross-process interface between a process of the first application and the out of process webview for the second application by establishing a cross-process parenting between the host window, the system bridge window, and the hosted window that is configured to exchange rendering information between the hosted window and the host window; and

cause the host window to display the rendering information from the hosted window within the host window on a display of the computer device.