Skip to content

You are not logged in. Register orLog In

start:

ODF Toolkit: Transition Steps

Below a possible transition path from the current situation to an OpenOffice.org system based on an ODF Toolkit is illustrated. The individual transition steps are presented in a sequential order for convenience only. In practice, most transition steps are independent of each other and therefor may be executed in parrallel.

Current Situation

Currently, OpenOffice.org consists of

  • an URE,

  • an OpenOffice.org installation, which includes an URE, but does not re-use an already installed URE.

  • Many projects that are based on OpenOffice.org or the OpenOffice.org code.

Currently, there is no solution

  • for customer that believe OpenOffice.org has to much overhead for their solution, and

  • for (OpenOffice.org or external) projects that require “some” OpenOffice.org functionality.

This situation is illustrated below.

Stage 1: Repackaging

In a first stage, OpenOffice.org gets spitted into the URE, the ODF Toolkit, and the OpenOffice.org applications. The three parts optionally can be downloaded separately, but in any case can be installed separately. The ODF Toolkit reuses an already installed URE, and the OpenOffice.org desktop application reuses the ODF Toolkit. Other project may be based on the ODF Toolkit, but also on the URE only.

This situation is illustrated below.

Stage 2: OpenDocument Toolkit API

In a second stage or in parallel to stage 1, the OpenOffice.org API is extended by an “ODF API” that is better aligned with OpenDocument than the existing API, but also considers new UNO features and the experience that was made with the existing APIs.

Stage 3: Further Modularization

After the repackaging phase, the ODF Toolkit may be further modularized by separating individual services from the toolkit. These services actually would remain part of the ODF Toolkit, but could be instantiated or installed separately. In addition, new components may be added to the toolkit.

This situation is illustrated below.

Stage 4: Additional Layers

In this stage, a couple of low-level APIs will be defined and implemented (for instance a ODF package API). The implementations will become part of ODF Toolkit.

This situation is illustrated below.

Next: Case Studies

Previous: Detailed ODF Toolkit Proposal

Back to main page.