Abstract: A method and system for automatically retrieving and integrating one or more supplemental software programs into at least one of an existing software program may include receiving a request to open a document via the existing software program, retrieving a list of supplemental software programs for the document, the list of supplemental software programs including an identification for each of the supplemental software programs and an application source from which the supplemental software programs can be retrieved, embedding the list of supplemental software programs into a data structure for the document, embedding a program for processing the list of supplemental software programs into a data structure for the document, and transmitting the data structure to a component for processing. The program is configured to retrieve the supplemental software programs from the application source and automatically integrate the supplemental software programs into the data structure.

Abstract: A method and system for automatically retrieving and integrating one or more supplemental software programs into at least one of an existing software program may include receiving a request to open a document via the existing software program, retrieving a list of supplemental software programs for the document, the list of supplemental software programs including an identification for each of the supplemental software programs and an application source from which the supplemental software programs can be retrieved, embedding the list of supplemental software programs into a data structure for the document, embedding a program for processing the list of supplemental software programs into a data structure for the document, and transmitting the data structure to a component for processing. The program is configured to retrieve the supplemental software programs from the application source and automatically integrate the supplemental software programs into the data structure.

Abstract: A computer implemented method for updating a host application with an individual feature includes operations for pinging a server via an installer associated with the host application on a client device to obtain information regarding one or more available features, downloading a feature from one or more available features from the server to the client device, and updating, via the installer, the host application with the feature.

Abstract: A computer implemented method for updating a host application with an individual feature includes operations for pinging a server via an installer associated with the host application on a client device to obtain information regarding one or more available features, downloading a feature from one or more available features from the server to the client device, and updating, via the installer, the host application with the feature.

Abstract: Mechanisms are described herein for propagating a theme definition from a host application to a host extension so that the host application and the host extension are visually consistent. A theme definition may be updated after a theme change event occurs as a result of a user interacting with the host application. The theme definition may then be utilized by the host extension to update one or more UI elements presented by the host extension to enable visual consistency.

Abstract: Mechanisms are described herein for propagating a theme definition from a host application to a host extension so that the host application and the host extension are visually consistent. A theme definition may be updated after a theme change event occurs as a result of a user interacting with the host application. The theme definition may then be utilized by the host extension to update one or more UI elements presented by the host extension to enable visual consistency.

Abstract: A software application written for a server environment is transformed into one which runs in a rich client environment. An entity model defines data sources as they are accessed from the server and as they are accessed from the clients. An application programming interface defines stereotyped interfaces which provide the same functionality on the server and the clients. A metadata model describes the components which make up the application and defines the differences in structure between the server and clients. The metadata model also defines mappings between components used on the server and clients. Settings and context information which tailor the activation and functionality of the components is also captured in the metadata model. Automated transformation is performed by using the mappings to identify the component set to use for the clients, selecting the client version of the application programming interfaces, and selecting the appropriate settings and context information.

Abstract: A set of protocols support a common script object model for document interaction that crosses document types and runtime environments. A cross frame browser-based protocol may provide a secure, scalable, and asynchronous mechanism for transmitting script object model requests to document hosts and managing responses to developer code in standards-compliant browsers. A hostable runtime Application Programming Interface (API) may provide a secure, scalable, and asynchronous protocol to transmit script object model requests across process boundaries to document hosts back to developer code with minimum performance impact on the document host.

Abstract: Technologies are described herein for deploying a solution artifact to a client-side application. In one method, an instruction to deploy the solution artifact to the client-side application program is received. Upon receiving the instruction, a determination is made whether a package associated with the solution artifact and the client-side application program was generated. Upon determining that the package was generated, a determination is made whether the package is current. Upon determining that the package is not current or that the package was not generated, the package is generated based on the solution artifact and the client-side application program. Upon determining that the package is current or upon generating the package, the package is deployed to the client-side application program.

Abstract: Technologies are described herein for deploying a solution artifact to a client-side application. In one method, an instruction to deploy the solution artifact to the client-side application program is received. Upon receiving the instruction, a determination is made whether a package associated with the solution artifact and the client-side application program was generated. Upon determining that the package was generated, a determination is made whether the package is current. Upon determining that the package is not current or that the package was not generated, the package is generated based on the solution artifact and the client-side application program. Upon determining that the package is current or upon generating the package, the package is deployed to the client-side application program.

Abstract: Object model based mapping may be provided. First, backend data may be received defining data constructs in a backend system. Then entity data may be received defining data constructs in an entity model. User selectable elements may then be received defining a process associating the backend data with the entity data. Next, code may be produced, based on the received user selectable elements, configured to implement the process.

Abstract: A set of protocols support a common script object model for document interaction that crosses document types and runtime environments. A cross frame browser-based protocol may provide a secure, scalable, and asynchronous mechanism for transmitting script object model requests to document hosts and managing responses to developer code in standards-compliant browsers. A hostable runtime Application Programming Interface (API) may provide a secure, scalable, and asynchronous protocol to transmit script object model requests across process boundaries to document hosts back to developer code with minimum performance impact on the document host.

Abstract: A system and method for enabling supplementary deployment actions to be performed in conjunction with a deployment of an application version. A deployment manager may download one or more supplementary deployment action (SDA) components to a user application cache. In conjunction with performing deployment actions, SDA components may be invoked from the user application cache or from a global application cache. The SDA components may perform actions specific to the application or version of the application, including actions not preconfigured in the deployment manager. An SDA component may be invoked prior to or after the deployment manager performs deployment actions. If an SDA component fails, SDA components that succeeded may be automatically invoked to roll back their actions. SDA components may be used to perform a first install, an update, a roll back, or an uninstall. SDA components may have the privileges of the application and the user corresponding to the user application cache.

Abstract: Technologies are described herein for deploying a solution artifact to a client-side application. In one method, an instruction to deploy the solution artifact to the client-side application program is received. Upon receiving the instruction, a determination is made whether a package associated with the solution artifact and the client-side application program was generated. Upon determining that the package was generated, a determination is made whether the package is current. Upon determining that the package is not current or that the package was not generated, the package is generated based on the solution artifact and the client-side application program. Upon determining that the package is current or upon generating the package, the package is deployed to the client-side application program.

Abstract: A software application written for a server environment is transformed into one which runs in a rich client environment. An entity model defines data sources as they are accessed from the server and as they are accessed from the clients. An application programming interface defines stereotyped interfaces which provide the same functionality on the server and the clients. A metadata model describes the components which make up the application and defines the differences in structure between the server and clients. The metadata model also defines mappings between components used on the server and clients. Settings and context information which tailor the activation and functionality of the components is also captured in the metadata model. Automated transformation is performed by using the mappings to identify the component set to use for the clients, selecting the client version of the application programming interfaces, and selecting the appropriate settings and context information.

Abstract: Object model based mapping may be provided. First, backend data may be received defining data constructs in a backend system. Then entity data may be received defining data constructs in an entity model. User selectable elements may then be received defining a process associating the backend data with the entity data. Next, code may be produced, based on the received user selectable elements, configured to implement the process.