Difference between revisions of "Extensions development"

From Apache OpenOffice Wiki
Jump to: navigation, search
(Books on OpenOffice.org Basic Programming: update last reference)
m
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.
+
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 {{AOo}} 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 [http://extensions.services.openoffice.org Extensions repository] and installed by end-users easily.
+
The principle is to create UNO packages that can be listed in the OpenOffice.org [https://extensions.services.openoffice.org Extensions repository] and installed by end-users easily.
  
 
This section gives newcomers as well as experienced developers some hints for developing Extensions in various languages and provides tools and frameworks to facilitate that development.
 
This section gives newcomers as well as experienced developers some hints for developing Extensions in various languages and provides tools and frameworks to facilitate that development.
  
Popular Extensions may be integrated into OpenOffice.org, so it is important to follow common policies from beginning to ease this merging.
+
Popular Extensions may be integrated into {{AOo}}, so it is important to follow common policies from beginning to ease this merging.
  
Finally, extension developers are invited to join our [http://openoffice.apache.org/mailing-lists.html#api-mailing-list-public API mailing list] to ask questions and share ideas.
+
Finally, extension developers are invited to join our [https://openoffice.apache.org/mailing-lists.html#api-mailing-list-public API mailing list] to ask questions and share ideas.
  
 
==== Starting in a language ====
 
==== Starting in a language ====
Addons can be written in various languages. Each section gives starting information to help you create your addon. 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 the UNO bridge language issues are at [http://udk.openoffice.org UDK project]. The [http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/OpenOffice.org_Developers_Guide OpenOffice.org Developer's Guide] is a valuable source of information as well.
+
Addons can be written in various languages. Each section gives starting information to help you create your addon. Each section is dedicated to a language. It deals with specific points concerning the Extensions aspect. Resources regarding the {{AOO}} API can be found on the [https://www.openoffice.org/api/ API project] and the UNO bridge language issues are at [https://www.openoffice.org/udk/ UDK project]. The [https://wiki.openoffice.org/wiki/Documentation/DevGuide/OpenOffice.org_Developers_Guide OpenOffice Developer's Guide] is a valuable source of information as well.
  
 
The translations of these pages are welcomed and [[Extensions#Translating_these_pages|guidelines are available]].
 
The translations of these pages are welcomed and [[Extensions#Translating_these_pages|guidelines are available]].

Revision as of 13:23, 10 January 2021

OOo Extensions project

Please view the wiki usage guidelines
before contributing.

Categories:

Pages:

Extensions on the main site

Extensions in other languages:
ES - FR - IT - JA - NL - OC -

Developing extensions is an efficient way to bring value to OpenOffice.org without diving into core sources. Obviously all developers willing to develop at Apache OpenOffice 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 gives newcomers as well as experienced developers some hints for developing Extensions in various languages and provides tools and frameworks to facilitate that development.

Popular Extensions may be integrated into Apache OpenOffice, so it is important to follow common policies from beginning to ease this merging.

Finally, extension developers are invited to join our API mailing list to ask questions and share ideas.

Starting in a language

Addons can be written in various languages. Each section gives starting information to help you create your addon. Each section is dedicated to a language. It deals with specific points concerning the Extensions aspect. Resources regarding the Apache OpenOffice API can be found on the API project and the UNO bridge language issues are at UDK project. The OpenOffice Developer's Guide is a valuable source of information as well.

The translations of these pages are welcomed and guidelines are available.

Articles, Tutorials & Reference Information

Books on OpenOffice.org Basic Programming

Tools & Frameworks

Best Practices

Project: Enhancing the Extensions Infrastructure of OpenOffice.org

Improving the Extension Manager

Personal tools