The following table displays helpful resources:
Resource | Description |
Programmer's Tutorial | This PDF document presents the basic concepts of the OpenOffice API, the document models (including some UML diagrams) and a bunch of examples in StarBASIC as well. (Version for StarOffice 5.2) |
UNO Development Kit Homepage | UNO (Universal Network Objects) is an interface based object model. UNO is a specification for a communication model among distributed objects. It allows these objects to be implemented in any language for which a binding exists. Currently there are language bindings for Java and different C++ compilers on different platforms. |
OpenOffice API Homepage | The OpenOffice.org API is based on the OpenOffice.org component technology and consists of a wide range of interfaces defined in a CORBA-like IDL. While the component technology determines how the components or applications communicate with each other, the OpenOffice.org API defines the interface for accessing office functionality from different programming languages. The OpenOffice API reference manual is available from the homepage. |
Developing components with UNO | The tutorial "Developing components with UNO" explains the fundamental concepts (ODK, UNO), shows how to access existing services in UNO, and how to write simple UNO components. The text is enhanced with Java and C++ code. |
Guideline for designing OpenOffice APIs | The guideline for designing OpenOffice APIs describes general design rules and the definition of API elements. |
Office Development Kit (ODK) | The ODK is a set of tools, libraries, jar files, header files and idl files which are necessary to develop components for the OpenOffice.org using the OpenOffice API and the OpenOffice.org component technology UNO (Universal Network Objects). |