The Mathworks, Inc.

Peter Webb

Charles Gary Nylander

John Micco

Anthony Paul Astolfi

Marc Ullman

Barry Simon

James Stewart

Loren P Dean

Jocelyn Martin

Todd Flanagan

Richard John Alcock

A device may store dependency information for a group of software components provided by a technical computing environment. The group of software components may include a first software component and a second software component and may identify the second software component as being a dependent software component of the first software component. The device may obtain an application generated via the technical computing environment and may determine that the application invokes the first software component. The device may access the dependency information based on the application invoking the first software component and may determine that the first software component invokes the second software component based on the dependency information. The device may generate a deployable form of the application that allows the application to run in another computing environment.

Functional dependency analysis

Exemplary embodiments provide adapted components that may be used by a computer program under different execution contexts. The adapted components may include platform independent source code which may be executed regardless of the execution context in which the component is deployed. Adaptation logic may wrap the execution context independent component in a wrapper. The wrapper may perform data marshaling between the execution context independent component and a computer program invoking the execution context independent component, or the host system on which the computer program is deployed. The execution context independent component may be adapted to a new execution context dynamically the first time that the execution context independent component is invoked in the execution context. Thereafter, the execution context independent component may be invoked statically without the need to re-adapt the component.

Adaptive interface for cross-platform component generation

Exemplary embodiments provide methods, mediums, and systems for generating a runtime environment that is customized to a particular computer program, particularly in terms of the function definitions that support function calls made in the computer program. The customized runtime environment may therefore be smaller in size than a conventional runtime environment. To create such a customized runtime environment, an analyzer may be provided which monitors test executions of the computer program and/or performs a structural analysis of the source code of the computer program. The analyzer may determine a list of probabilistically or deterministically required function definitions, and provide the list to a component reducer. The component reducer may eliminate any function definitions not deemed to be required from a runtime environment, thereby producing a customized runtime environment that is built to support a particular computer program.

Accurate static dependency analysis via execution-context type prediction

A method of ensuring the integrity of read-only components in deployed mixed-mode applications that includes generating a digital fingerprint prior to the deployment of a mixed-mode application is discussed. The digital fingerprint is based on a read-only component in the mixed-mode application and uniquely identifies the read-only component. The method also deploys the mixed-mode application and the digital fingerprint. Additionally, the method verifies, at execution time by using the digital fingerprint, that the read-only component in the mixed-mode deployed application that served as the basis for the digital fingerprint is identical to the same read-only component originally packaged with the mixed-mode application.

System and method for verifying the integrity of read-only components in deployed mixed-mode applications

An exemplary embodiment may provide tools for creating a graphical user interface (GUI) in a first or original environment and for embedding the GUI in a second or target environment. The GUI created in the first environment may be translated into a platform independent description. A proxy GUI may be generated from the platform independent description and incorporated in the second environment.

Proxy graphical user interface generation

The present invention is directed toward automatically integrating a late bound program language into an external environment. The external environment may be an early bound environment, a late bound environment or some combination thereof. Associated with the late bound program environment is a modular execution engine and an interface mechanism, wherein the interface mechanism is capable of expressing late bound semantics in a format compatible with the external environment.

Calling of late bound functions from an external program environment

A self-contained virtual file system is disclosed for deploying and distributing an application and/or software component. Executable files relating to the application are included in a distributable composite file. The composite file and a user front end application are deployed and distributed to an application user where the application is executed. An application provider can tag the composite file with the version information and other useful meta-data of the files for the application. The format of the composite file may support the storage of any kind of file types and associated meta-data. The composite file may contain the hierarchical directory structure of the files for the application so that the hierarchical directory structure is installed in the application user's electronic device.

Deploying and distributing of applications and software components

Embodiments of the present application may simplify an integration of statically typed and dynamically typed languages by automatically generating an implementation of a statically typed native interface for a given set of dynamically typed functions. In an embodiment, functions in a dynamically typed language are automatically interconnected with functions in a statically typed language. Code that bridges and/or connects a statically typed interface and a dynamically typed interface embodied in the dynamically typed source code may be automatically generated. The statically typed interface may be provided by a user. Further, an extensible set of runtime rules that determine how to convert between statically typed and dynamically typed data may be provided.

Dynamically generating statically-typed proxies for dynamically-typed functions

A distributed graphical presentation and manipulation application executes as a thin client application in a network. The networked graphical presentation and manipulation application can generally be used without requiring a user to install any specific software prior to using the application. In one embodiment, code may be received from a server via the network. A local environment may be generated based on the code, where the local environment may be configured to display a view of a graphical model. A request to manipulate the view may be received within the local environment. A request for a manipulated view may be transmitted to the server based on the received request. The manipulated view may be received from the server. The received manipulated view may be displayed within the local environment.

Thin client graphical presentation and manipulation application

A device receives a program that includes one of a parallel construct or a distributed construct, creates a target component from the program, and integrates the target component into a target environment to produce a client program that is executable on multiple heterogeneous server platforms.

Growing community of inventors

Newton, MA, United States of America

Peter Webb