Launchy 3.7.0 released - JSLib dropped
I've just released version 3.7.0 of Launchy. Launchy is a Mozilla, Mozilla Firefox, Mozilla Thunderbird, Netscape and Nvu extension that will enable you to open current page, links, mailto, images and view source with external applications. Download
I had to replace JSLib, since JSLib has a problem with the global namespace. Basically this problem occurs when multiple extensions are including JSLib. So if extension A is including a version of JSLib and then extension B also is including a JSLib version, it's only the first loaded extension that works. Some people using Launchy found themself having this problem if Launchy was loaded after the StumbleUpon extension. Loading order is the way the extensions are listed in the extension manager.
To eliminate this problem the extensions have to rely on JSLib being installed on it's own and not included inside the extension. But since people don't have control over how an extension is installed this is not very useful. How does one control the installation process at ie. update.mozilla.org, since there's no dependencies.
So what I really miss in the install.rdf script is a depend tag. So I can say that JSLib version blabla has to be installed for this extension to work. What could also be nice was some kind of namespace for each extension. If I in my extension have a global variable called
test then other extensions also have this variable.
The other big news in version 3.7.0 is the addition of translations. Launchy version 3.7.0 has been translated into 9 languages. Danish (da-DK), German (de-DE), Spanish (es-ES), Italian (it-IT), Dutch (nl-NL), Portuguese (pt-BR), Russian (ru-RU), Chinese Simplified (zh-CN), Traditional Chinese (zh-TW). Thanks to all the translators that read my posting.
> Loading order is the way the extensions are listed in the extension manager.
Are you sure? The last time I tested it extensions were still loaded in the reverse order they are listed in the overlayinfo files.
> So what I really miss in the install.rdf script is a depend tag.
http://www.mozilla.org/projects/firefox/extensions/packaging/extensions.html mentions em:requires but it isn't used by the Extension Manager or UMO (there was a bug somewhere).Comment by Anonymous at January 6, 2005 12:25 AM | Permalink
Is the em:requires stuff in EM even implemented? I can install extensions withs missing requirements using a trunk build, and I can't find any relevant source code that deals with "requires"... So that would need to be done first.
(Even if that were done, wouldn't the jslib people have to keep everything backwards-compatible? That could become painful as time goes on...)Comment by Mook at January 6, 2005 08:18 AM | Permalink
> Is the em:requires stuff in EM even implemented?
> Even if that were done, wouldn't the jslib people have to keep everything backwards-compatible?
This they need to do currently, but wouldn't need if em:requires would be implemented (in a reasonable way) as extensions can tell with which version they work. Good would be also if em:provides would exist...