|OOo Extensions project
Please view the wiki usage guidelines
|Extensions on the main site|
Developing extensions is an efficient way to bring value to OpenOffice.org without diving into core sources. Obviously all developers willing to develop at OpenOffice.org sources level are welcomed.
OpenOffice.org enables third party tools creation through UNO bridges, allowing using many languages.
The principle is to create UNO packages that can be listed in the OpenOffice.org Extensions repository and installed by end-users easily.
This section wants to give newcomers as well as experienced developers some hints to develop Extensions in their desired languages and provide them with tools and frameworks that ease and homogenize the development.
Finally, popular Extensions may be integrated into OpenOffice.org so it is important to follow common policies from beginning to ease this merging.
Starting in a language
Addons can be written in various languages. Each section is here to give starting informations that let you create your addons. Each section is dedicated to a language. It deals with specific points concerning the Extensions aspect. Resources regarding the OpenOffice.org API can be found on the API project and UNO bridges languages issues on the UDK project
The translations of these pages are welcomed and guidelines are available.
- Starting in Python
- Starting in Basic
- Starting in Java
- Starting in C++
- Non programmatic Extensions
- Extensions packaging
- Extensions Integration into Installation Set
Tools & Frameworks
- Code snippets available in many languages
- Translation framework
- Extensions Packager
- Predefined wizards
- Introspection Tools: discover the API
- OpenOffice_Eclipse_Integration - OpenOffice.org development with Eclipse
- OpenOffice.org NetBeans Integration - plug-in for NetBeans providing some nice features to simplify the development with and for OpenOffice.org (highlevel wizards, UNOIDL and xcu syntax highlighting, code completion, integrated API reference, ...)
Project: Enhancing the Extensions Infrastructure of OpenOffice.org
Improving the Extension Manager
- What about an extension that offered automatic dual-format saving, i.e. automatically saving in both *.odt and *.doc?
For example I prefer to use the OpenOffice format, but often I need to send the file to a person who doesn't have OpenOffice... just an idea.
(Sorry about editing your page, but there was no other way I could find to give my ideas where lots of people would see them. Delete it if you want, but I think an ideas section might be worthwhile.)
--Seanlano 09:02, 24 July 2007 (CEST)