Difference between revisions of "Extensions development"
(→Starting in a language) |
Timarandras (Talk | contribs) m (typo fixes) |
||
| Line 1: | Line 1: | ||
{{Extensions}} | {{Extensions}} | ||
| − | + | Developing extensions is an efficient way to bring value to OpenOffice.org without diving into core sources. Obviously all developers willing to [[Main_Page|develop at OpenOffice.org sources level]] are welcomed. | |
| − | OpenOffice.org enables third party tools creation through UNO bridges, allowing using many languages | + | 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|Extensions repository]] and installed by end-users | + | The principle is to create UNO packages that can be listed in the OpenOffice.org [[Extensions_repository|Extensions repository]] and installed by end-users easily. |
| − | This section wants to give | + | 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 | + | 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 ==== | ==== 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. | + | 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 [http://api.openoffice.org API project] and UNO bridges languages issues on the [http://udk.openoffice.org UDK project] |
| − | The translations of these pages are | + | The translations of these pages are welcomed and [[Extensions#Translating_these_pages|guidelines are available]]. |
* [[Extensions_development_python|Starting in Python]] | * [[Extensions_development_python|Starting in Python]] | ||
Revision as of 21:02, 31 March 2006
| OOo Extensions project
Please view the wiki usage guidelines
|
|---|
|
Categories: Pages:
|
| Extensions on the main site |
|
Extensions in other languages: |
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 programatic Extensions
- Extensions packaging
Tools & Frameworks
- Translation framework
- Extension Packager
- Predefined wizards
- Introspection Tools : discover the API
