Methods and systems for supporting a rendering API using a runtime environment

• US 9,286,142 B2
• Filed: 04/07/2011
• Issued: 03/15/2016
• Est. Priority Date: 04/07/2011
• Status: Active Grant

• Current Assignee: Adobe Systems Incorporated (Adobe Inc.)
• Original Assignee: Adobe Systems Incorporated (Adobe Inc.)
• Inventors: Cucu, Andrian, Tanase, Adrian
• Primary Examiner(s): Anya, Charles E
• Assistant Examiner(s): HOANG, PHUONG N
• Application Number:
  US13/081,728
• Publication Number:
  US 20120260267A1
• Time in Patent Office: 1,804 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications

Abstract

A computing device can comprise an I/O interface and a processing element connected to the I/O interface and implementing a runtime environment. The processing element can implement a program component that causes the processing element to expose a rendering API not natively supported by the runtime environment, the rendering API invocable by code comprised in a markup document accessed by the processor over the I/O interface. The rendering API can be exposed by causing the runtime environment to respond to and update a proxy object that mirrors properties, methods, and behaviors defined by the rendering API.

Claims

1. A computer, comprising:

a processor; and

a non-transitory computer readable medium comprising instructions that, when executed by the processor, cause the computer to perform operations comprising;

parsing code of a markup document using a browser, the code using calls to an application programing interface (API) to specify content to be rendered and the code further specifying a proxy object;

creating the proxy object by interpreting the code of the markup document;

invoking a runtime environment by interpreting the code of the markup document;

updating a state of the proxy object based on a call to the API, the call initiated based on the browser using the code of the markup document, the call to the API native to the browser and non-native to the runtime environment;

determining that the state of the proxy object has changed; and

based on determining that the state of the proxy object has changed, invoking a command of the runtime environment to provide an additional graphical element or additional functionality in content rendered by the browser, wherein updating the state of the proxy object by interpreting the code of the markup document and then invoking the command based on the change in the state of the proxy object enables the runtime environment to respond to the code in the markup document that uses a property, method, or behavior that is native to the browser but non-native to the runtime environment.

2. The computer of claim 1, wherein the API comprises a video rendering API.

3. The computer of claim 2, wherein the markup document references a video to be played back using the runtime environment with at least one control element rendered by the browser and configured to invoke the API.

4. The computer of claim 1, wherein the markup document is configured to invoke functionality of a scripting API that causes the processor to maintain the proxy object in the non-transitory computer readable medium.

5. The computer of claim 4, wherein the markup document is configured to invoke a getter method of the scripting API that causes the processor to obtain a value of a mirrored property and, based on the value of the mirrored property, invoke the command of the runtime environment, and

wherein the markup document invokes a setter method of the scripting API that causes the processor to set a value of a property mirrored by the proxy object in response to an event or state change of the runtime.

6. The computer of claim 4, wherein the runtime environment causes the processor to propagate state changes from the runtime environment to the proxy object by invoking the scripting API to change the state of the proxy object.

7. The computer of claim 4, wherein the proxy object causes the processor to dispatch a scripting event matching an event format of the API.

8. The computer of claim 1, wherein the markup document is configured to invoke a scripting API to cause the processor to maintain a first copy of the proxy object and a second copy of the proxy object, the first and second copies identical when first initialized, and

wherein the runtime environment is configured to, after the first and second copies are first initialized, determine if the API has been invoked by determining if one of the first and second copies of the proxy object has changed.

9. The computer of claim 1, wherein the proxy object causes the processor to respond to input changing a writable attribute defined by the API by changing an attribute of the proxy object.

10. The computer of claim 1, wherein the runtime environment is implemented by executing the instructions stored in the non-transitory computer readable medium.

11. The computer of claim 1, wherein the markup document comprises an HTML document, wherein the HTML document references a JavaScript file, and wherein the JavaScript file invokes a scripting functionality that comprises JavaScript.

21. The method of claim 1, wherein the code comprises human-readable source code and the runtime executes the code directly using just-in-time compilation.

22. The method of claim 1, wherein the API comprises at least one class defining an object including a plurality of methods for rendering graphical elements.

23. The computer of claim 1, wherein the browser is configured to:

determine, based on parsing the code of the markup document, that a first call to the API is to be handled by the runtime environment and that a second call to the API is to be handled by the browser, the first call and the second call associated with rendering the content of the markup document,

handle the second call to the API, and

cause the proxy object to enable the runtime environment to handle the first call to the API.

24. The computer of claim 1, wherein a change to a state of the runtime environment is propagated to the proxy object, and wherein the proxy object is configured to dispatch an event in the browser in response to the propagated change in state of the runtime environment.

12. A non-transitory computer-readable medium comprising instructions that, upon execution with a processor, cause a system to perform operations comprising:

parsing code of a markup document using a browser application, the code using calls to an application programing interface (API) to specify content to be rendered and the code further specifying a proxy object;

creating the proxy object by interpreting the code of the markup document;

a runtime application by interpreting the code of the markup document; and

updating a state of the proxy object based on a call to the API, the call initiated based on the browser application using the code of the markup document, the call to the API native to the browser application and non-native to the runtime application;

determining that the state of the proxy object has changed; and

based on determining that the state of the proxy object has changed, invoking a command of the runtime application to provide an additional graphical element or additional functionality in content rendered by the browser application, wherein updating the state of the proxy object and then invoking the command based on the change in the state of the proxy object enables the runtime application to respond to the code in the markup document that uses a property, method, or behavior that is native to the browser application but non-native to the runtime application.

13. The non-transitory computer-readable medium of claim 12, wherein the proxy object is maintained by a scripting API, wherein the scripting API is invoked based on code invoking scripting functionality of the browser application.

14. The non-transitory computer-readable medium of claim 13, wherein the proxy object mirrors the property names, method names, and behaviors defined by HTMLVideoElement, HTMLAudioElement, and HTMLMediaElement APIs.

15. The non-transitory computer-readable medium of claim 12, wherein the code of the markup document comprises a first markup element referencing a runtime application to be executed in a runtime environment to play a video.

16. The non-transitory computer-readable medium of claim 15, wherein the operations further comprise:

generating an interface element based on-a second markup element defining how the interface element is to be rendered; and

providing the command to invoke the call supported by the video rendering API in response to an input event generated by the interface element.

17. The non-transitory computer-readable medium of claim 16, wherein the call supported by the video rendering API comprises a playback control command and the method invoked by the proxy object comprises a corresponding method that controls playback of the video by the runtime environment.

18. A computer-implemented method, comprising:

parsing code of a markup document using a browser, the code using calls to an application programing interface (API) to specify content to be rendered and the code further specifying a proxy object;

creating the proxy object by interpreting the code of the markup document;

invoking a runtime environment by interpreting the code of the markup document;

updating a state of the proxy object based on a call to the API, the call initiated based on the browser using the code of the markup document, the call to the API native to the browser and non-native to the runtime environment;

determining that the state of the proxy object has changed; and

based on determining that the state of the proxy object has changed, invoking a command of the runtime environment to provide an additional graphical element or additional functionality in content rendered by the browser, wherein updating the state of the proxy object by interpreting the code of the markup document and then invoking the command based on the change in the state of the proxy object enables the runtime environment to respond to the code in the markup document that uses a property, method, or behavior that is native to the browser but non-native to the runtime environment.

19. The method of claim 18, further comprising:

in response to determining the state of the proxy object has changed and based on the state of the proxy object, dispatching an event defined by the video rendering API.

20. The method of claim 19, further comprising:

prior to determining the state of the proxy object has changed, updating an attribute of the proxy object in response to a change of state of the runtime environment,

wherein the event that is subsequently dispatched is defined by the proxy object to correspond to the attribute as updated.