Difference between revisions of "Extensions development"
Cedricbosdo (Talk | contribs) (→Starting in a language: typo) |
Cedricbosdo (Talk | contribs) (links changes and added a Development category) |
||
| Line 14: | Line 14: | ||
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. Ressources regarding the OpenOffice.org API can be found on the [http://api.openoffice.org API project] and UNO bridges languages issues on th [http://udk.openoffice.org UDK project] | 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. Ressources regarding the OpenOffice.org API can be found on the [http://api.openoffice.org API project] and UNO bridges languages issues on th [http://udk.openoffice.org UDK project] | ||
| − | The translations of these pages are welcommed and [ | + | The translations of these pages are welcommed and [[Extensions#Translating_these_pages|guidelines are available]]. |
| − | * [ | + | * [[Extensions_development_python|Starting in Python]] |
* Starting in Basic | * Starting in Basic | ||
| − | * [ | + | * [[Extensions_development_java|Starting in Java]] |
* Starting in C++ | * Starting in C++ | ||
* Non programatic Extensions | * Non programatic Extensions | ||
| Line 29: | Line 29: | ||
* Predefined wizards | * Predefined wizards | ||
* Introspection Tools : discover the API | * Introspection Tools : discover the API | ||
| + | |||
| + | [[Category:Development]] | ||
Revision as of 20:22, 19 March 2006
Developping extensions is an efficient way to bring value to OpenOffice.org without diving into core sources. Obviously all developpers willing to develop at OpenOffice.org sources level are welcommed
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 easilly
This section wants to give newcommers as well as experienced devloppers 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 begining 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. Ressources regarding the OpenOffice.org API can be found on the API project and UNO bridges languages issues on th UDK project
The translations of these pages are welcommed and guidelines are available.
- Starting in Python
- Starting in Basic
- Starting in Java
- Starting in C++
- Non programatic Extensions
- Extensions packaging
Tools & Frameworks
- Translation framework
- Extension Packager
- Predefined wizards
- Introspection Tools : discover the API
