Language Selection

English French German Italian Portuguese Spanish

Extend OpenOffice.org

Filed under
OOo
HowTos

If you have a nifty macro or a nice Writer template you want to share with other OpenOffice.org users, publishing them on the Web along with detailed installation instructions is probably not the best way to go. Fortunately, OpenOffice.org supports extensions-small installable packages that provide added functionality. You easily can turn your templates, autotext entries, gallery art and macros into extensions that can be installed with a couple of clicks. Better yet, OpenOffice.org's extensions have an easy-to-understand and well-defined architecture, and you can start building your own extensions in no time.

Extending OpenOffice.org's functionality using extensions is nothing new. From the very beginning, users could add new features to the office suite by installing so-called UNO packages. Usually, these packages contained OOo Basic code, and they offered a more straightforward way of integrating macros into OpenOffice.org applications. With the release of OpenOffice.org 2.0.4, the idea of adding new features via installable packages has been rethought thoroughly and aligned with a concept that is more familiar to end users-namely the extension architecture of the Mozilla Firefox browser.

The technical implementation of the extension system in OpenOffice.org also has been reworked. Most notably, the new version of OpenOffice.org can handle so-called non-code extensions that can contain document templates, gallery items, autotext snippets and so on. The new version of OpenOffice.org also introduces the new .oxt file extension that allows users to identify installable extension packages easily.

How Extensions Work

More in Tux Machines

today's leftovers

  • The Linux Migration: April 2017 Progress Report
    In December 2016, I kicked off a migration to Linux (from OS X) as my primary laptop OS. In the nearly 4 months since the initial progress report, I’ve published a series of articles providing updates on things like which Linux distribution I selected, how I’m handling running VMs on my Linux laptop, and integration with corporate collaboration systems (here, here, and here). I thought that these “along the way” posts would be sufficient to keep readers informed, but I’ve had a couple of requests in the last week about how the migration is going. This post will help answer that question by summarizing what’s happened so far. Let me start by saying that I am actively using a Linux-powered laptop as my primary laptop right now, and I have been doing so since early February. All the posts I’ve published so far have been updates of how things are going “in production,” so to speak. The following sections describe my current, active environment.
  • Galago Pro: Look Inside
    Look inside the Galago Pro and see how easy it is to upgrade!
  • Direct3D 9 Over Vulkan Continues Progressing
  • Nouveau 1.0.15 X.Org Driver Released With Pascal Support
  • Arch Linux running natively on Pixel C
  • openSUSE Conference 2017 Schedule Posted

Making GNU/Linux Look Nice

Lumina Desktop Gets lumina-mediaplayer

  • 1.3.0 Development Preview: lumina-mediaplayer
  • Lumina Desktop Gets Its Own Media Player
    There's now yet another open-source media player, but this time focused on the BSD-focused Qt-powered Lumina Desktop Environment. Lumina Media Player is one of the new additions for the upcoming Lumina 1.3. Lumina Media Player's UI is quite simple so far and allows playing of local audio/video files along with basic audio streaming -- currently implemented for Pandora.

today's howtos