Checklist for Writing Extensions
From Apache OpenOffice Wiki
< Documentation | DevGuide
- Checklist for Writing Extensions
- File Format
- Display Name
- Extension Description
- Extension Identifiers
- Extension Versions
- Target Platform
- Simple License
- Publisher Information
- System Integration
- Online Update of Extensions
This page gives a brief overview about what is important when developing an extension.
- Use the .oxt file extension and provide description.xml. Look here why you should use
- Provide an extension identifier. [go to XML description]
- Provide a version. [go to XML description]
- Provide a display name. [go to XML description]
- Provide an icon. [go to XML description]
- Provide a description. [go to XML description]
- Specify the target platforms. [go to XML description]
- You may provide dependencies. [go to XML description]. For example, if your extension requires a 'minimal version' of Apache OpenOffice then use the OpenOffice.org-minimal-version dependency.
- You may provide a license. [go to XML description]
- You may customize the 'online update' of your extension unless the update facility of the Apache OpenOffice extension repository does not fit your needs. [go to XML description].
- You may provide options pages in case the extension needs to be configured. [go to XML description].
- Provide publisher information. [go to XML description].
- Provide links to release notes (TODO: more documentation) in the description.xml. Currently, only used within the 'update dialog'. When using the Apache OpenOffice extension repository, then the link to the release notes is automatically generated from the information entered on the web site. That is, when using the repository, one does not need to provide this information in the description.xml.
- Provide content for help system if necessary.
|Content on this page is licensed under the Public Documentation License (PDL).|