On 12/13/2011 9:33 AM, Sebastian Zartner wrote:
> Thanks for the fast reply.
>
>> No, we do not plan on implementing any extension dependency feature. We
>> looked at this closely, and the UI required to implement extension
>> dependencies "properly" would be hugely complex and require some very
>> advanced features from AMO.
> That quite disappoints me. With "requires" you already had a simple system for checking version dependencies. Why was the feature dropped?
I thought I just explained this: the feature didn't work well, didn't
meet most extension author's needs (because it didn't check version
ranges), and supporting it with the new extension UI would have
introduced significant complexity which we don't believe is warranted.
> As I am seeing it, every Firebug extension will now have to check via the addons manager API, if Firebug is installed and if the version is supported.
I don't think you should use the extension manager API for this. Just
expose a JS module or a service (implemented by firebug), and have the
firebug addons do the version checking. If the JS module/service is
missing, then Firebug isn't installed. This is a small code pattern you
can promote with the Firebug extension community.
--BDS