Disclosed are systems and methods for providing a hybrid mobile application. The method may include: receiving specification of at least one feature of a mobile application. The mobile application may be specific to a first programming platform. The method may further include generating the at least one feature based on the specification. The at least one feature may be written in a programming language specific to a second programming platform, and the second programming platform may be different from the first programming platform. The method may also include compiling a programming wrapper based on the at least one feature of the mobile application, combining the at least one feature and the programming wrapper into a programming component, packaging the programming component into the mobile application, and distributing the mobile application in a repository of the first programming platform.

A method and an apparatus that schedule a plurality of executables in a schedule queue for execution in one or more physical compute devices such as CPUs or GPUs concurrently are described. One or more executables are compiled online from a source having an existing executable for a type of physical compute devices different from the one or more physical compute devices. Dependency relations among elements corresponding to scheduled executables are determined to select an executable to be executed by a plurality of threads concurrently in more than one of the physical compute devices. A thread initialized for executing an executable in a GPU of the physical compute devices are initialized for execution in another CPU of the physical compute devices if the GPU is busy with graphics processing threads. Sources and existing executables for an API function are stored in an API library to execute a plurality of executables in a plurality of physical compute devices, including the existing executables and online compiled executables from the sources.

Disclosed are systems and methods for providing a hybrid mobile application. The method may include: receiving specification of at least one feature of a mobile application. The mobile application may be specific to a first programming platform. The method may further include generating the at least one feature based on the specification. The at least one feature may be written in a programming language specific to a second programming platform, and the second programming platform may be different from the first programming platform. The method may also include compiling a programming wrapper based on the at least one feature of the mobile application, combining the at least one feature and the programming wrapper into a programming component, packaging the programming component into the mobile application, and distributing the mobile application in a repository of the first programming platform.

A method for loading multiple versions of the same native library in a native runtime environment. In one embodiment, the method comprises cloning a native library workspace with a first version number as a cloned native library; applying a namespace across the cloned native library; injecting a macro into source code associated with the cloned native library; adding a dependency to the cloned native library in source code associated with the native runtime environment; and registering the first version number in a project configuration of the native runtime environment.

In accordance with one or more aspects, a request to run an application is received. The application has an associated tune manifest that identifies one or more resources that the application may use. The tune manifest is compared to a device resource record, and a check is made, based at least in part on the comparing, whether the one or more resources identified in the tune manifest can be satisfied by the device. If the one or more resources identified in the tune manifest can be satisfied by the device, then the application is run; otherwise, a notification of a conflict between the application and the device is presented. Additionally, when the application exits, a device tune state that identifies a content source to which the device was tuned prior to running the application can be retrieved and the device restored to this device tune state.

A method of providing a control software configuration for a module of a modular plant, the method including, in a module engineering phase: receiving a user definition for the module; and automatically generating the control software configuration for the module based on the user definition, the automatically generating including: specifying parameters for the module that are not specific to any target system; and providing the control software configuration as a controller-agnostic configuration file for subsequent binding of controller software instantiated according to the controller-agnostic configuration file to a hardware controller of the module when the module is integrated into a target system during a plant engineering phase.

Described is a system for providing variants of a digital asset based on specific device capabilities of target devices. A developer may compress a digital asset that is part of a universal application to be installed on a set of target devices by selecting from a set of intent-based compression options. The compression options may include hardware-accelerated compression formats that utilize a graphics processing unit (GPU) during rendering. Despite the compression option selected, the application package includes a variant of the digital asset renderable on each type of target device including devices without a GPU. This allows a developer to freely choose any option without the concern of whether the option is compatible or supported by each type of device. A distribution server may then map attributes of a specific target to particular feature classes, and accordingly, distribute an appropriate variant of the digital asset to the target device.

A method and an apparatus that schedule a plurality of executables in a schedule queue for execution in one or more physical compute devices such as CPUs or GPUs concurrently are described. One or more executables are compiled online from a source having an existing executable for a type of physical compute devices different from the one or more physical compute devices. Dependency relations among elements corresponding to scheduled executables are determined to select an executable to be executed by a plurality of threads concurrently in more than one of the physical compute devices. A thread initialized for executing an executable in a GPU of the physical compute devices are initialized for execution in another CPU of the physical compute devices if the GPU is busy with graphics processing threads. Sources and existing executables for an API function are stored in an API library to execute a plurality of executables in a plurality of physical compute devices, including the existing executables and online compiled executables from the sources.

Disclosed are systems and methods for providing a hybrid mobile application. The method may include: receiving specification of at least one feature of a mobile application. The mobile application may be specific to a first programming platform. The method may further include generating the at least one feature based on the specification. The at least one feature may be written in a programming language specific to a second programming platform, and the second programming platform may be different from the first programming platform. The method may also include compiling a programming wrapper based on the at least one feature of the mobile application, combining the at least one feature and the programming wrapper into a programming component, packaging the programming component into the mobile application, and distributing the mobile application in a repository of the first programming platform.

A client server environment having a server with a Web service in communication with a local client application which is tightly integrated with its local operating environment residing on a platform remote from the server; the local client application tightly integrated by way of integrating data structures requested and received from the server; the integrating data structures defining the attributes and parameters needed by the local client application to define an interface between the local client application and the Web service. The integrating data structures enable tight/close integration between the hosted application and the devices and the operating system features of the platform upon which the local client application resides. Also disclosed is an abstracted environment which can run on any one of the supported platform's devices as a native application, all based on the passing of the same page commands and receipt of corresponding client data objects between the server and the client applications; the data objects being identical irrespective of the platform. In a preferred form, the device application interface for each local platform is tightly integrated with the client application whereby the abstracted environment appears to run as a native application on the platform.