Abstract: Systems and methods are disclosed for exporting a document in multiple formats. The disclosed systems and methods may include creating a metafile including content associated with the document and injecting comments into the metafile. The comments may comprise semantic information corresponding to the document. Also, the metafile may be parsed to create at least one call. The at least one call may be configured to enable an export engine to render the document. Furthermore, the at least one call may be sent to the export engine configured to render the document in an output format associated with the export engine. In addition, the export engine maybe selected from a plurality of export engines based upon user input indicating the output format associated with the selected export engine.

Abstract: An electronic paper file is generated from an enhanced metafile such that data may be converted from multiple applications with different data descriptions to a single electronic paper format having a particular data description. The enhanced metafile includes a series of individual records that provide a sequence of graphic instructions to render properties associated with objects in the document in an output format. The enhanced metafile is parsed into a series of state independent objects to generate an intermediary representation of the document. The objects and corresponding identifying information are temporarily stored in an object storage structure before using the objects to generate the electronic paper file. The object storage structure provides a stateless model of the enhanced metafile such that the objects may be randomly accessed and applied to any output format.

Abstract: Described is managing the changing of software implementations such as applications deployed to enterprise client users or machines. Precedence relationships between deployed applications are specified. To determine which applications to install for a given client, the precedence is applied to the subset of applications assigned or published to the client. At logon or machine reboot, an upgrade process evaluates the deployed applications and any upgrade relationships, setting applications for removal or installation. A user may also install an application that has been designated as optional. Also described is an application lifecycle model for replacing applications. For example, administrators can phase in upgrades as a pilot to a small group of users, roll out upgrades to a larger group, and then provide the application to all users. Upgrades may be mandatory or optional, and replaced programs may be removed and then replaced, or overlaid during installation.