Add-on Options

[Brian King]

The override option described at:

http://starkravingfinkle.org/blog/2009/09/fennec-handling-add-on-options/

... is quite straightforward.

However, what if there is no options url to override? So, the mobile
add-on is sharing the same code-base as the desktop add-on, and the
latter has no options, i.e. no em:optionsUrl.

Know any good hacks to keep the button disabled on desktop while
enabling it on mobile?

- Brian

[Mark Finkle]

> Know any good hacks to keep the button disabled on desktop while
> enabling it on mobile?

We could add code to check that the optionsURL has content. I'm not sure we want to do that as we fill the list (performance issue), but we could disable the button if we see that is has no content (or returns an XML error).

Not ideal, but it would give some feedback. Let me know what you think, or file a bug to add this check.

[Brian King]

Mark Finkle wrote:
> We could add code to check that the optionsURL has content. I'm not
> sure we want to do that as we fill the list (performance issue), but
> we could disable the button if we see that is has no content (or
> returns an XML error).
>
> Not ideal, but it would give some feedback. Let me know what you
> think, or file a bug to add this check.

Not sure if this would be optimal and/or if we want to give error
feedback here.

There could be a separate em:optionsMobileURL or something like that.
Then we might hear the other app (TB, Seamonkey, ...) folks crying foul
looking for their own.

Or in chrome.manifest something like:

override chrome://myapp/content/settings.xul null
application={ec8030f7-c20a-464f-9b0e-13a3a9e97384}

--
Brian King
Need Mozilla Project Hosting?
http://mozdev.org