Extensions

From The Document Foundation Wiki
Jump to: navigation, search

You can enhance the functionality of LibreOffice with Extensions.

How to install Extensions

Installing extensions is easy, and provides many useful features.

Developing Extensions

If you are an extension developer, you can use several languages to develop LibreOffice extensions. Supported programming languages are Basic, Python, JavaScript and Java. For the higher level of integrity and possibilities you can use C++, Python and Java languages to develop UNO complements based extensions.

As a UNO components you can provide new implementations of existing functionality or specialized components like Calc Add-Ins, Add-Ons, DataPilots, Chart Add-Ins, or linguistic components: Spellchecker, Hyphenator or Thesaurus (see Add-Ins documentation).

Also you can pack extensions for additional Templates, Gallery and Autotexts.

Finally, extensions are the preferred way for sysadmins to modify default settings. A guide for developing configuration extensions is available in PDF or ODT format. A sample OXT configuration extension accompanies the guide.

Please refer to Development/Extension Development for more detail on how to develop them.

Default Extensions

A handful of extensions are included in LibreOffice by default.

The list of default extensions includes: (Page not found for https://www.libreoffice.org/features/extensions/ )

  • PDF Import
  • Presentation Minimizer
  • Presenter Console
  • Report Builder
  • Non-linear Solver
  • Wiki Publisher

Questions:

  • Are these extensions fully-integrated, or can they be as-easily removed as other, non-default extensions?
  • Requirements for default extensions? (e.g. license, size, scope, etc..)
    • "We do not include any third-party extensions in the official builds." tdf#45200
  • How can one suggest a new default extension?
    • In general, there shouldnt be "default extensions". Either something is a of general unconditional use to the userbase of LibreOffice -- then it should be part of the LibreOffice core product -- or it is a valuable solution to a subaudience -- then it should be (and stay) an extension. If something originally developed as an extension becomes so popular and relevant to be considered to be included in LibreOffice itself, it should ideally have the code, scope, licensing and style acceptable to other core components (e.g. with rare exceptions: be written in C++11). Please keep this in mind if you aim for some functionality to be ultimately included in LibreOffice.

Extension Bugs

See Filing a bug report against an Extension.

More Information