RO128167A2 - Method and systems for supporting a rendering api by using a runtime environment - Google Patents

Abstract

The invention relates to a method and system for supporting a video rendering application programming interface (API) by using a runtime environment. The claimed system comprises a computing device () comprising an I/O interface () and a processing element connected to the I/O interface (), the processing element implementing a runtime environment () and applying a program component that causes the processing element to expose a rendering API not natively supported by the runtime environment (), the rendering API being invoked by a code comprised in a markup document and exposed by causing the runtime environment () to respond to and to update a proxy object () that mirrors the properties, methods and behaviour defined by the rendering API. The claimed method consists in determining, by means of a processing device, a state of a proxy object, said state being stored in a computer readable medium, the proxy object mirroring attributes of a video rendering API, and in response to determining the state of the proxy object and based on the state of the proxy object, in invoking, by the processing device, a method supported by a runtime environment.

Description

State-of-the-art in the field Qj -0 ^ · · Internet users are enthusiastically consuming video content and other types of multimedia content. Such content is often distrubbed using codes, such as HTML or another mark-up code, configured to invoke an application's ability to retrieve content and render content according to an application programming interface. video rendering (API) exposed by the application. As an example, a runtime environment such as Adobe® Flash® player or AIR® runtime environment (both available from Adobe Systems Incorporated of San Jose, California) can be used to render video. However, some users may not have access to a device that supports such a runtime environment.

Recently, the HTML standard has been extended to include the mentioned video rendering APIs by including <video> and other elements in the HTML code through which a browser can be used to render native video. Despite the recent expansions of ARI to add video and other browsers, there is still room for improvement in both user experience and developer experience working to deliver content to users.

Abstract A computing device may have an input-output (l / E) interface and a processing element connected to the l / E interface and which implements a runtime environment. The processing element can implement a program component that causes the processing element to expose a rendering API that is not natively supported by the runtime environment, the code-invoked rendering API contained in a markup document accessed by processor via the l / E interface. The rendering API can be exposed by provoking the runtime environment's response to and updating a proxy object that mirrors the properties, methods, and behaviors defined by the rendering API.

For example, by using the proxy object, the runtime environment can be made to respond to the code that invokes the specified commands according to the <video> HTML API. In this way, developers can write code using the <video> API with the confidence that the same code can be used with or without the runtime environment. In addition, developers can write code that still uses the benefits of the runtime environment capabilities that extend beyond the capabilities of the browser or other rendering application.

These illustrative embodiments are discussed not to limit the present subject, but only to provide a brief introduction. Further embodiments include computer-readable media for exposing and using the rendering API functionality through the use of proxy objects, along with methods implemented on computers that do the same. These and other embodiments are described in the following in the Detailed Description. Objects and advantages of this subject may be determined after reviewing the specification and / or practical application of an embodiment configured according to one or more aspects disclosed herein.

BRIEF DESCRIPTION OF THE DRAWINGS A complete and accessible detailed disclosure is accessible in the remaining portion of this patent description. The patent description refers to the following accompanying figures.

Figure 1 is a diagram of the data flow that illustrates how one or more proxy objects can be used to illustrate API functionality through a runtime environment.

Figure 2 is a diagram showing an illustrative system configured to use a proxy object to illustrate API functionality through a runtime environment.

ιΆΊ 0 1 1 - 0 0 3 2 5 -O 7 -04- 2011 Figure 3 shows the steps of a logical program schematic of an illustrative method that illustrates the functionality of the API through a proxy object and using such functionality.

Figure 4 shows the steps of a logical program diagram of an illustrative method of selective use of the runtime environment to illustrate a video rendering APi that is not natively supported by the runtime environment.

Detailed Description The embodiments discussed below include computer systems, methods, computer readable media that incorporate code. For example, a rendering API such as the "HTML5" video API may be provided at the beginning of a runtime such as the Flash® player plug-in so that web developers can use a standardized, compatible API without being need to negotiate with Flash® player or another runtime-specific API. Additionally, resources can be consolidated (for example, you do not need to have separate libraries for both native HTML video player and Flash video player) when a web page has both Flash player and native HTML video for content. video for use by different client devices. In some of the implementations, script-based getters and setters are used to map Runtime Apl calls to runtime calls and to provide rendering API responses that are based on runtime changes / events and setting mirror properties of the <video> API.

Turning to Figure 1, for example, a data flow chart shows how one or more proxy elements can be used to illustrate API functionality that is not natively supported by a runtime environment.

In particular, the code 102 includes one or more elements 104 that use the rendering API together with one or more elements 106 that call a scripting API to set proxy objects. Code 102 also includes a reference 108 to a runtime application 129. In this example, as shown in 110, calls to the rendering API and calls to the scripting API shown to

Λ-l 01 1-00323-0 7 -Μ- 2011

112 are at least processed through a rendering application 114, which is a browser or other application that parses code 102. The rendering application 114 also has the appropriate functionality to recognize scripting API calls; for example, rendering application 114 may include a JavaScript ™ or other engine that supports scripting calls.

The rendering application 114 may include the functionality to natively support at least part of the rendering API calls defined by the elements 104. Thus, as shown in 116, the rendering application provides at least a certain portion or certain portions of a graphical user interface 117 which comprises (in this example) a video element 118 and the control button 120, which may be used to handle input events that control the playback of video content 122 (e.g., for play / pause in response to the entry directed to the triangle button "play" presented here) and provides updates as the content 122 changes. As another example of a control element, a controlbar 121 with a scrub bar may be used during playback, and the scrub bar may be moved from left to right as the video advances.

In accordance with the present subject matter, however, the rendering application 114 configures one or more proxy objects 126 so that, as shown in 124, one or more calls to the rendering API can be handled via a medium. runtime 128 that runs / interprets the runtime application 129 so that effectively, runtime environment 128 exposes the rendering API. For example, the proxy object 126 may be configured to have the same property names, method names, and behavior defined by the rendering API, so that the proxy object 126 distributes the same events based on the status changes in the video or other rendered content. as expected from a native implementation.

The proxy object 126 monitors events, such as user input or other events that use the rendering API to change a property associated with the rendering APi. As shown in at 127, in response 4 l \ -2 0 1 1 - 0 0 3 2 3 -0 7-04-2011 at ο change of ownership, the proxy object 126 uses the corresponding functionality of the runtime player via the API of the external call provided by the runtime. As also shown at 127, the proxy object also responds to a change in the state of the runtime environment 128 by propagating the change of state to one or more of its properties and by sending an appropriate event or events as defined in the render API.

For example, as shown in 130, the runtime environment 128 may be used to provide some or all of the elements of the graphical user interface 117. As a particular example, the code 102 may specify that the runtime environment 128 must provide the video element 118 while the native API capabilities of the browser 114 are used to render the control button 120 and another "chrome", as well as by using a controlbar 121 defined using HTML and CSS. This may allow the same platform controls to be used regardless of whether those platforms support all of the runtime 128 environment and / or to enable the use of the runtime 128 environment capabilities as a support for multicasting, content protection (e.g. content coded streaming). In this way, events directed to the UI elements of the controlbar provided by the browser may be propagated to proxy objects 126 which thus use the functionality of the runtime environment 128. For example, the video may be specified as a SWF or another. file that was played by the runtime environment where it was available.

In response to an input event directed to the control button 120, the status of the proxy object 126 may be updated. In response to the change in its state, the proxy object 126 can resort to the functionality of the runtime environment 128, such as by providing a play () or pause () command exposed by the runtime environment 128 as part of the API of external control of the runtime environment. Similarly, as the state of the runtime environment 128, for example as the video time index increases, the time index may be propagated to the proxy object 126 which distributes the corresponding events to make the control button visible or invisible . In addition to or instead of storing status changes by proxy object 126, one or more of ^ -2011-00325-0 7-04-2011 properties may be mirrored by proxy object 126 by using the values of property for objects associated with the rendering API to trigger runtime environment commands 128 through the usual getter methods and / or by updating property values for objects associated with the rendering API in response to the activity of runtime environment 128 by methods ordinary setter.

As another example, the code 102 may use a video rendering API to provide the video element 118 and the control button 120. However, to advantageously use the reporting capabilities of a runtime application (e.g., to detect if users are skipping ads and / or the advanced graphics capabilities of a runtime environment, code 102 can be configured with handheld scripting elements 106 so that a proper runtime application is used to secure the controlbar. For example, code 102 may include an element that refers to a SWF or a routine file aslt that provides the controlbar.

To the extent that the input events are directed to the elements made available by the rendering application 114, the proxy object (s) 126 may (may) be updated and used to send the corresponding events in accordance with the APIs video rendering. For example, a "play" or "pause" entry to the runtime application may cause updates to the status of the proxy object 126, which sends a proper command to the rendering components of the video browser to start playback or pause it respectively.

Other events can be used to use the video rendering API. For example, a page may include logic that indicates that a video should be paused while an ad is being sent, such as by sending a pause command () when the video reaches a specific point in time. if, for example, the runtime environment is used for video playback, then the pause command () sent by the page logic can be mapped to a corresponding pause command for the runtime.

-20 1 1 - 0 0 3 2 5 -0 7 -Ο ¹ »- 2011

The above examples are presented for illustrative purposes only. In the following detailed description, numerous specific details are presented to ensure in this way a thorough knowledge of the subject. However, it should be understood by those skilled in the art that the subject may be skeptical without these specific details. In other circumstances, methods, apparatus, or systems that would be known to one of ordinary skill in the art have not been described in detail so as not to overshadow the subject.

Figure 2 is a diagram showing an illustrative computing device 202 which is used to provide video content 122 as shown in Figure 1 through the use of rendering application 114, proxy object 126 and runtime environment 128. Alternatively, the computing device 202 may be referred to as a data processing system, a computer device, or simply a "computer". The computing device 202 represents a desktop, laptop, tablet or any other computing system. Other examples of computing systems 202 include, but are not limited to, mobile devices (PDAs, smartphones, media players, game systems, etc.), game devices, televisions, and set-top speakers for televisions, as well as embedded systems (for example, in vehicles, home appliances, or other devices).

Generally speaking, the computing device 202 represents one or more data processing hardware elements that implement the rendering application 114 and the runtime environment 128. The rendering application 114 causes the computing device 202 to parse code 102 in Figure 1 and to set proxy objects 126 and, in case the runtime environment 128 is not used, to answer the rendering API calls specified in code 102. Of course, code 102 can be provided as one or more files. In this example, the rendering API is a video rendering API, but it is understood that the principles discussed here can be applied to other rendering APIs for which a runtime environment would be desirable.

The proxy object (s) 126 may be implemented in a non-transient computer readable environment in a manner that ensures the updating of the attributes of the proxy object (s) 126 and allows methods defined by the proxy object (s) 126

0 \ -2 0 1 1 - 0 0 3 2 3 "

7-0 ^ -2011

to be implemented through appropriate processing hardware. For example, rendering application 114 may include a Javascript ™ or other scripting engine whose functionality is used to provide proxy object (s) 126 based on scripting API calls formulated in code 102.

Runtime environment 128 provides a runtime environment for one or more runtime applications 129 referred to by code 102. For example, runtime application 129 may have a cross-byte code. -platform that provides runtime environment 128. In some embodiments, runtime environment 128 comprises an environment such as Adobe® Flash® or AIR®, mentioned above, Microsoft® Silverlight® (available from Microsoft Corporation in Redmond Washington ), a Java® Virtual Machine (available from Oracle Corporation in Redwood Shores, California), or another runtime. The runtime application 129 may be downloaded from a network connection or may be accessed from memory in response to reference 108 in code 102, or it may be accessed directly with code 102 when code 102 is initially accessed. The runtime environment 128 can run within an operating system that also supports rendering application 114. However, the runtime environment 128 may itself have the operating system in some of the implementations. When implemented as a software, the runtime environment 128 can itself be downloaded if it is not already resident on the device 202, and the runtime environment 128 and the application 129 can even be distributed as an integrated unit, when desired.

The rendering application 114 and / or the runtime environment 128 may be implemented in the accessible hardware through or as part of the data processing element (for example, as an application-specific integrated circuit, (ASIC) , as a programmable logic device (for example, Pl_As, FPGAs, etc.)). As another example, the rendering application 114 and / or the runtime environment 128 can be implemented using software or firmware that configures the operation of a processor or processors.

In the example shown in Figure 2, the computing device 202 represents a data processing hardware component comprising one or more processors 204 and a computer readable environment (1-2011-0 0 3 2 3 - 0 7-0 ^ -2011 (memory 206) interconnected via an interconnector 208, representing internal buses, connections and the like, Interconnector 208 is also connected to components l / E 210, such as universal serial bus (USB), VGA , HDMI, serial and other l / E connections to other computing system hardware. The hardware also includes one or more displays 212. It is understood that the computing device 202 may include other components, such as storage devices, communication devices (eg, Ethernet, radio components) and other I / O components such as speakers, microphones and the like.

Generally speaking, the interconnector 208 is used to receive the code 102 and the content to be rendered, to store the code 102 and the content data as required, such as on a local hard drive, a memory. cache, network storage, etc. and retransmitting the rendered content to the l / E 210 interface for display on the display device 122. The input is provided via input devices such as the mouse, keyboard, touch screen interface, etc.

The computer readable environment 206 may have RAM, ROM or other memory and in this example incorporate the rendering application code 114, the proxy object 126, the runtime environment 128, and the runtime application 129. It is from it is understood that the code 102 may also be stored in a computer readable environment 206 or in another environment.

Figure 3 is a logical program schematic showing us the steps of an illustrative method 300 for highlighting API functionality via a proxy object and using such functionality. Block 302 represents the parsing code of a markup or other document that uses a rendering API. For example, block 302 may be executed by a browser or other rendering application 114 in Figures 1-2.

Block 304 represents the installation of one or more proxy objects 126. For example, the markup document may be configured with code that uses a scripting API supported by the rendering application 114 so that the proxy objects can be instantiated. so as to render the properties, methods and

Α-2 Ο 1 1 - Ο 0 3 2 3 - 0 7-04-2011 the behaviors defined by the rendering API. In some embodiments, the proxy object (s) 126 provides each and every property, method, and behavior of the rendering API (or APIs) to be exposed to ensure that the expected capabilities of the rendering API are available.

In addition, the markup document may define getter and setter methods that are supported by the scripting API to map events and runtime states to the rendering API and to resort to runtime functionality / setting runtime states in response. on rendering API calls. A getter is a method that gets the value of a specific property. A setter is a method that determines the value of a specific property. Thus, in block 304 when the proxy object is installed, appropriate getters and setters can be initialized to make the connection between the rendering API and the external interface calls of the runtime environment.

In some implementations, a JavaScript proxy object may be provided that mirrors the HTMLVideoElement element, HTMLAudioElement, and HTMLMediaElement APIs as defined in the HTML standard (see, for example, http: // www. whatwQ.org/specs/webapps/current- work / multipaqe / video.html # video, which was incorporated here, by reference, in its entirety). The object may have exactly the same property names, exactly the same method names, and exactly the same behavior as described in the specifications (for example, for the APIs above, the proxy object sends exactly the same VideoElement / Media Element events specified in the specification which reflects changes in basic implementation status). Implementations that mirror the API at the property level can advantageously allow the written code to use the rendering API to be reused with minimal or even no modifications to accommodate proxy / ruritime usage since the API specification is fully complied with. Of course, APIs other than the above can be mirrored. Additional examples include, but are not limited to, HTMLFormElement, HTMLCanvasElement, HTMLTableElement, etc.

Block 306 represents the installation of the UI and other elements (for example, the video element 118) that must be provided by the rendering application, in cx-2 0 1 1 - 0 0 3 2 3 -0 7 -04- 2011 while block 308 represents the use of the runtime application. Block 306 may include setting additional UI elements by another specific application. Setup operations may include instantiating objects and other program components to render UI elements and to perform other functionality. The particular balance between which functions are used by the rendering application and the runtime application may vary according to the particular implementations. The runtime application may be downloaded or otherwise accessed by the runtime environment for execution as needed in response to input or input events.

For example, the markup document will typically use functionality to be used natively by the rendering application, such as various web page elements such as text and images. Depending on a particular implementation, the rendering application can be used to render video content, video controls and the like, with the runtime application playing a "background" role to monitor and report playback. As another example, the runtime application can be used to trigger video playback while the native capabilities of the rendering application are utilized to provide controls and chrome for a consistent appearance. As an additional example, the runtime application can be used for "chrome" and for controls while the rendering application deals with the video rendering of today.

In any case, for those rendering API invocations to be used by the runtime application, the UI (or other elements) are set such that the user or other rendering API events cause an update of the object's status. (s) proxy and / or are related to the getter and setter methods so that changes in statuses and events are passed directly to the runtime without storing the status in the proxy object.

In this example, as shown in block 310, in response to a rendering API call, the status of the proxy object may be updated. Then, in block 312, a runtime command is used based on the status of the proxy object. However, if the getter / setter methods are supported, then an API call

Λ-2 Ο 1 1 - 0 0 3 2 3 0 7 -04-2011 the rendering can be mapped directly on a call to one or more runtime methods to make the runtime respond.

For example, in some implementations, JavaScript method calls are proxied (via a proxy object) to methods exposed by the runtime environment. For example, the Flash® runtime environment provides External Interface calls that the proxy object can invoke in response to the UI or other events that invoke the rendering API. In this way, changing the status of the proxy object can simply be receiving the API call, which then leads directly to a corresponding call to the runtime.

Additionally or alternatively, the render API call may be of a type that changes an attribute defined by the render API, that attribute being maintained as a write attribute of the proxy object. Changes to the write attributes of the proxy object can be used in various ways depending on the capabilities of the rendering application 114. For example, the scripting engines of the latest browser versions allow the getter and setter to be defined. via calls to the scripting API as noted above. For those browsers, getters and setters can be defined so that changing the attribute that can be written causes the proxy object to call a method exposed by the runtime environment. For example, if an entry or other event calls "current Time = 30" in JavaScript, the proxy object may call "setCurrent Time (30)" to the Flash® runtime (via the External Interface) Not all. browsers support common settings and getters. To resolve such situations, the scripting code may include scripting API calls to keep a first copy of the proxy object and a second copy of the proxy object, the first and second copies being identical when they are first initialized. For example, the proxy object may be initialized together with an object that functions as an indigo copy of the runtime state. The proxy object can regularly probe the copy to indigo, and when the copy to indigo and the proxy object no longer matches, the proxy object can determine whether the rendering API

U-2 01 1-00323-0 7-04-2011 was invoked and make an appropriate call to the runtime (for example, for Flash® runtime, using the External Interface).

Block 314 represents the propagation of a state change from a runtime environment to a proxy object, while block 316 represents the updating of the UI elements or another action that is taken in the rendering application that is based on the propagated state change. These blocks are presented after blocks 310 312, although it is possible that they are located in front of blocks 310-312 or even in parallel with them. Generally speaking, the runtime environment may call upon the scripting API to update the status of the proxy object and / or to invoke a method defined by the proxy object, the proxy object being subsequently forwarded to the appropriate API. rendering.

For example, if Flash® runtime is used, the External Interface may make a call to JavaScript to update one or more of the properties of the JavaScript proxy object. In some of the implementations, the update takes place without further processing unless there is already a change of attribute that can be written, in which case the conflict is resolved in favor of the existing proxy object change. In response to the change, a JavaScript event is sent that matches the event (s) specified in the rendering API (for example, events as defined in the <video> HTML API).

As noted above, not all browsers can support enough getters and setters to identify when changes to the proxy object have been made. Thus, the copy-to-idigo approach can also be used to determine when a runtime propagates a state change.

As shown in block 318, the method can be looped through blocks 310-316 until the rendering is complete. For example, rendering may be complete when video or other content is finished or if a user exits early. Of course, other exit conditions can be defined.

Α-2 01 1 -00325-Ο 7 -0V 2011 Figure 4 is a ο logic program diagram showing the steps of an illustrative method 400 for selective use of the runtime environment for the purpose of exposing a video rendering API that is not supported in natively by the runtime environment. For example, the code 102 of Figure 1 may cause the computing devices (such as the computing device 202) to perform the flow shown at 400.

Block 402 represents the receipt and parsing, by a browser, of an HTML file with a <video> element and scripting elements configured as discussed above. For example, HTML may use at least some of the <video> HTML rendering functionality. Block 404 is the determination of whether the computing device supports a runtime environment required to use a runtime application to which the HTML file refers. For example, a JavaScript code or other code can be used to identify a type of device and / or if Flash® runtime or other runtime environment is installed.

If the runtime environment is unavailable, the flow continues to block 406, which represents the video rendering API as natively supported by the browser. However, if the runtime environment is found in block 404, then the flow continues to block 408. Block 408 represents the establishment of one or more proxy objects with setters and getters, or a proxy object and a copy to indigo, while block 410 represents use proxy object (s) to propagate commands to the runtime environment and to forward runtime status changes to the UI elements provided by the browser or other elements. For example, these steps may be performed in accordance with those discussed above in Figure 3.

Content developers and distributors, by configuring markup or other code 102 to make a computing device work as discussed here, may be exempt from the problem of preparing multiple versions of the code for different platforms. instead, the content developer / distributor can generate the code according to a routinely supported rendering API (for example, <video> HTML API) but without losing the benefits of using a runtime environment (e.g., runtime Flash® or AIR® runtime) for those devices that support the runtime environment.

U-2011-00323-0 7 -04- Ζϋιί

For example, as noted above, the runtime environment may be used to provide capabilities, such as multicasting, protected content distribution, usage tracking, and the like that are not supported by the rendering API. In this way, the same HTML file or other file can be distributed, for example, to set-top boxes for runtime television, mobile devices that support runtime, but also to mobile devices, tablets, etc. which may not support runtime.

The API parsing and exposing operations discussed above can be performed on a client device that also displays rendered content. However, in alternative implementations, API parsing and exposures can be performed on a server that then sends the data that represents the content that needs to be rendered to other devices than the one currently rendering the content.

The example in Figure 4 and other examples that have been discussed above in a browser and HTML rendering <video> API. Of course, other applications can support rendering APIs, and other rendering APIs can be used. Additionally, the rendering application has been described as the application for exposing the scripting API. Further embodiments may use a separate application or separate process to expose the scripting API, with inter-process communication between that separate application and the rendering application used as necessary to coordinate the input to and output from the elements provided with the application rendering. still further, several examples above have referred to the markup code, but another code (for example, the binary code) that invokes the rendering and scripting APIs and invokes the runtime environment instead can be used. of the markup code (for example, for code 102).

Development tools can use the principles mentioned above to give developers the ability to implement code that uses a rendering API and also uses a runtime environment when available. For example, a web development application may include a user interface, a code manager, and other components that are used to define HTML or other web page code. In an implementation, <λ-2 0 1 1 - 0 0 3 2 3 -0 7 -04- 2011 the web development application can be configured to identify <video> phage, for example or another syntax that invokes a Rendering API. The page may be updated to use a runtime environment (for example, by referring to a Flash® or other plugin) and to include JavaScript to map API calls to the Flash®player, while maintaining calls Original rendering APIs that do not use Flash® (or other runtime environment). In some implementations, the <video> phage is replaced with a <div> to avoid controversy that occurs on some devices if the <video> tag itself is replaced entirely with runtime playback.

General Considerations General Considerations Some portions of the detailed description have been presented in terms of symbolic or algorithmic representation of operations on data bits or digital signals stored within the memory of a computer system, such as computer memory. These descriptions or algorithmic representations are examples of a technique used by specialists in the field of data processing to convey the substance of their work to other specialists in the field. An algorithm is considered here and generally to be a sequence of self-sufficient operations or processing similar to this which leads to a desired result. In this context, operations and processing involve physical manipulation and physical size.

Typically, although not required, such sizes may take the form of electrical or magnetic signals that can be stored, transferred, combined, compared or otherwise used. It has sometimes been found convenient, mainly for reasons of common use, to refer to such signals as bits, data, values, elements, symbols, letters, terms, numbers, numerals or the like. However, it should be understood that all these and similar terms must be associated with appropriate physical sizes and are simply convenient labels.

Unless stated otherwise, as is apparent from the foregoing discussion, it is considered that throughout this specification discussions using terms such as "processing", "calculating", "calculating", "determining" or <V2 O 1 1 - 0 0 3 2 3 -O 7 -04-2011 others also refer to actions or processes of a computing platform, such as one or more computers and / or a computing device or devices similar electronic devices, which use or transform data represented as electronic or magnetic physical quantities from the memory, registers or other information storage devices, transmission devices, or computing platform display devices.

Although several examples have presented mobile devices, the various systems discussed herein are not limited to any particular hardware architecture or configuration. A computing device may include any appropriate arrangement of components that provide a result conditioned by one or more inputs. Suitable computing devices include microprocessor-based multifunctional computer systems that access stored software, which program or configure the computing system from a general purpose computing device into a specialized computing device by implementing one or more many ways to accomplish this topic. Any appropriate programming language, scripting or other language or language combination may be used to implement the science contained herein in the software to be used for programming or configuring a computing device.

A computing device may access one or more computer-readable non-transparent media that incorporates computer-readable instructions that, when executed by at least one computer, cause that at least one computer to implement one or more many of the ways of accomplishing this topic. When the software is used, the software may have one or more components, processes and / or applications included. In addition or alternatively to the software, the computing device (s) may have circuits that make the device (s) functional to implement one or more methods of the present subject.

Examples of computing devices include, but are not limited to, servers, personal computers, mobile devices (for example, tablets, smartphones, personal digital assistants (PDAs) etc.), televisions, set-top speakers for

Ă-2 0 1 1 - 0 0 3 2 3 -07 -04--2011 TVs, portable music players and electronic devices for amateurs such as cameras, cameras and mobile devices. The devices to be calculated can be integrated into other devices, for example "smart" appliances, cars, kiosks and the like.

Methods for carrying out the methods described herein may be realized in the operations of the computing devices. The order of the blocks presented in the examples above may be different - for example, the blocks may be re-ordered, combined, and / or decomposed into sub-blocks.

Certain blocks or processes may run in parallel.

Any suitable non-transient media or computer readable media may be used to implement or apply in practice the subject described herein, including, but not limited to, floppy disks, drives, magnetic media storage media. , optical storage media (for example, CD-ROMs, DVD-ROMs and variants thereof), flash memory devices, RAM, ROMs and others.

The use here of the terms "adapted to" or "configured for" is understood as open and inclusive language that does not exclude devices adapted for or configured to perform additional tasks and steps. in addition, the use of "on the basis" is understood to be open and inclusive, in that a process, step, calculation or other action that "is based on one or more of the conditions or values related can, in practice , be based on additional conditions or values to those that were stated. The titles, lists and numbering included here are for ease of explanation only and are not intended to be limiting.

Although the present subject has been described in detail with reference to certain embodiments thereof, it is self-evident to those skilled in the art, after passing through and understanding the foregoing that they can easily make changes to, variations to, and equivalent to these embodiments. Accordingly, it is understood that this description was presented for exemplification purposes only and not for limitation purposes, and does not preclude the inclusion of such modifications, variations and / or additions to this subject as is evident to those skilled in the art. .

Claims (20)

claims 1. Computer that has: an I / O interface; and a processing element connected to the l / E interface and which implements a runtime environment, the processing element also implementing a rendering application that makes the processing element provide a proxy object used to expose a Rendering API that is not natively supported by the runtime environment, the rendering API being invocable by the code contained in a markup document accessed by the processor via the l / E interface, the rendering API being exposed as it does for the runtime environment to respond to the properties, methods, and behaviors defined by the rendering API and mirrored by the proxy object. The computer according to claim 1, wherein the rendering API comprises a video rendering API. The computer according to claim 1, wherein the markup document invokes the functionality of a scripting API that causes the processing element to maintain the proxy object in a non-custodial storage environment. The computer according to claim 3, wherein the markup document invokes 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, invokes a command of the mirror property. the runtime environment, and where the markup document invokes a scripting API setter method that causes the processor to set a value of a property mirrored by the proxy object in response to an event or runtime change -his. The computer according to claim 3, wherein the runtime environment causes the processing element to propagate state changes from the runtime to the proxy object by invoking the scripting API to change a state of the proxy object. ι) ₍ -2 011-00323-- Ά 0 7 -04- 2011 A computer according to claim 3, wherein the proxy object causes the processor to send a scripting event that matches an event format of a rendering API. The computer according to claim 1, wherein the markup document invokes the scripting API to cause the processor to keep a first copy of the proxy object and a second copy of the poroxy object, the first copy and the second copy being identical when they are first initialized, and in which the runtime environment is configured, after the first copy and second copy are initialized first, to determine whether the rendering APi was invoked by determining whether one of the first and second copies of the proxy object they have changed. A computer according to claim 1, wherein the proxy object causes the processing element to respond to the input by changing an attribute that can be written defined by the rendering API by changing an attribute of the proxy object. The computer according to claim 1, wherein the processing element comprises a processor interfaced to a memory, the runtime environment being implemented by executing the program instructions that are stored in memory. 10. The computer according to claim 1, wherein the markup document comprises an HTML document, the scripting functionality comprises JavaScript, and the scripting functionality is invoked in accordance with a JavaScript file referred to in the HTML document. . 11. The computer according to claim 2, wherein the markup document refers to the video to be played using the runtime environment with at least one control element rendered by a browser and configured to invoke the video rendering API. 12. Computer program product that comprises the code embedded in a non-transient computer readable environment, the code comprising: 42 / Α-2 01 1-00323-0 7 -04- 2011 the code for invoking the functionality of a runtime application; and the code for invoking a scripting API to maintain a proxy object, the mirror attributes of the proxy object defined through a video rendering API and configured to invoke a method that is supported by the runtime application in response to receiving a commands to invoke a call supported by the video rendering API. The computer program product of claim 12, wherein the code for invoking the scripting API consists of the scripting functionality that invokes the markup code of a browser application. A computer program product according to claim 13, wherein the proxy object mirrors the property name, method name, and behaviors defined by the HTMLVideoElement, HTMLAudioElement, and HTMLMediaElement APIs. 15. The computer program product according to claim 12, wherein the code for invoking the functionality of the runtime application comprises a first markup element that refers to a runtime application that is to be executed in the runtime environment to play a video. A computer program product according to claim 15, further comprising: the code for generating an interface element, the code for generating the interface element comprising a second markup element that defines how the interface element should be rendered; and the code for providing the command to invoke a call supported by the video rendering API in response to an input event generated by the interface element. The computer program product according to 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 video playback via runtime environment. --2011-05323-0 7 -Μ- 2011 18. Ο method implemented on the computer, which consists of: determining, through a processing device, a state of the proxy object stored in a computer readable environment, the proxy object mirroring attributes of the supported video rendering API by a browser application In response to determining the status of the proxy object and based on the status of the proxy object, the processing device invokes a method supported by a runtime environment. The method according to claim 18, further comprising: In response to determining the status of the proxy object and based on the status of the proxy object, sending an event defined by the video rendering API. 20. The method according to claim 19, further comprising: updating a proxy object attribute in response to a change in the state of the runtime environment, before determining the status of the proxy object, wherein the event that is subsequently forwarded is defined by to the proxy object to match the attribute in the updated form.