Getting Updates from the Extensions Repository

If you are interested in extensions, then you may have found out already about http://extensions.services.openoffice.org and certainly tried some of the extensions. Chances are that you have grown fond of a particular extension and like to keep up with its latest version. Now, you can regularly check the web site – which is, by the way, always a good idea to learn about new arrivals – but there is also a simpler way. The Extension Manager (Tools->Extension Manager) is able to obtain new versions automatically. Just click the updates button and the next dialog will show you new versions for your currently installed extensions, if there are any available.

The update feature is actually nothing new and exists since OOo 2.2 (see http://blogs.sun.com/GullFOSS/entry/extensions_infrastructure_what_s_new). But there was no extension repository around at that time. This changed a couple of month ago and eased the way for providing updates through the Extension Manager, which is probable interesting for many developers. If you are an extension developer, then you may know about providing an "update URL" in the description.xml file. This is not necessary anymore. When you upload a new version of your extension then the web site automatically creates the necessary information and the Extension Manager will get them as an XML feed from the repository, when the user presses the updates button. In other words, extensions need not contain special "update" data, instead the repository will create the necessary information automatically.

Just a small side note. If you look closer at the previous image then you may notice that the dialog shows display names rather then the actual file names. This is also done in the main dialog. These display name can be localized, that is, there can be different names depending on the locale used by OOo.

Additional Information for Updates

Many people like myself like to have always the latest stuff on the computer which includes extensions as well. Because I am sort of lazy when it comes to determine what updates I actually need, I usually hit some 'get them all' button and be done with it. However at times, I start to get curious and would like to get more information. And here the extension updates dialog provides a new way of doing so: it can show a link to the publisher of the extension and to the release notes. These links appear when the user selects an extension and when the extension supports them.

 
The publisher name and the links to the web pages can be "localized". Provided the extension supports this localization the Extension Manager will choose a language which is used by OOo. That is, when clicking on the link, then the web browser opens a page which uses the same language as used by OOo.

As indicated, an extension need to have some build-in support for this feature (that is, a couple of additional entries in the description.xml). However, we are working on making it simpler by leaving the actual work to the repository. When developers upload an extension, then they typically provide a publisher title, a publisher URL and release notes. These information are then displayed on the web page for that extension. And these information can actually be reused by the Extension Manager. Except for the publisher name (this will come later), this already works quite well. That is, when a user clicks on the link, then the browser shows the release notes from the repository. Later when the web site supports different languages, then there will also be localized release-notes.

Better Support for Browser-based Updates

The extension repository can also be used as kind of advertising platform for extensions while the extensions are kept in a different place. This could be interesting for companies which want to to sell their extensions. Because the repository does not support a payment system, they need to direct the user to a different web site where the extension can be obtained. New versions may also be exclusivly available at that place. To get these extension it may be necessary to register, enter credentials, submit credit card information etc. So it is clear that the Extension Manager cannot automatically download these extension. However, it can now make users aware of an update and direct them to the proper place. So how does it work in particular? First, the update shows up in the list of available updates and is marked as "browser based update". When the user keeps it selected and presses the install button, then a web browser is started that navigates to the web site where the new version can be obtained. If the user also wants to install updates which can be automatically downloaded, then these are installed first. On closing the "Download and Install dialog“ the web browser will be started.

Once an extension has been downloaded, one can install it, for example by simply double-clicking its icon within a file browser.

That's for now. I hope these small improvements make using extensions an even better experience for you.

tags: extensions