Alternatively, maybe we should just support the options_ui manifest property from Chrome, like we're doing with most WebExtension APIs?
Docs: https://developer.chrome.com/extensions/optionsV2 Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1212685 On Mon, Oct 12, 2015 at 3:50 PM, Andre Garzia <[email protected]> wrote: > Michael, > > In my opinion having the add-on developer write code to inject his option > panel into the settings app is constantly reinventing the wheel. It would > be better in my opinion if we could have a key in the manifest.json that > would list each key, type, label and default value for all configurable > options, like: > > "options": [ > {"key": "lefthanded", "label": "Left handed user", "type": "boolean", > "default": false} > ] > > The settings app could parse this and assemble the needed panels for each > addon. Every time someone changes something there the addon receives some > sort of change event. All the options are exposed in the proxied global, > something like "window.addon.options" visible only in the addon scope. > > This would make the addon developer life easier because all they would > need to do is define the options in a json, no injection code necessary. > This would lead to more powerful addons as more tweeks are allowed. > > This whole system outlined above could be implemented as a POC as an addon > that injects system and looks into other addons manifests. > > On Wed, Oct 7, 2015 at 7:10 AM, Michael Henretty <[email protected]> > wrote: > >> +dev-fxos >> >> On Wed, Oct 7, 2015 at 12:13 AM, Eddie Lin <[email protected]> wrote: >> >>> I'm asking this because currently we can still declare activity filters >>> in manifest.webapp, >>> which makes an add-on being able to run as an app triggered with >>> MozActivity. >>> >>> Actually this is useful for add-on devs who wants to write a settings >>> page for their add-on, >>> I wonder if there will be any security concerns hence manifest.webapp >>> would get blocked or something in the future? >>> >> >>> >> Maybe another way to do this properly is to support "options_page" key in >>> manifest.json? >>> https://developer.chrome.com/extensions/options >>> >> >> >> Interesting! What is the use case for having an add-on act as an app that >> handles a MozActivity? Add-ons can already have a settings panel by simply >> injecting themselves into the Settings app. And IIRC, some add-ons even add >> a button in the Settings app which will "launch" their add-on, and show a >> configuration page from within their "app". If you wanted to handle a >> MozActivity from an add-on, why not inject into a Gaia app that already >> handles that activity and extend the functionality from there? >> >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "foxfood-feedback" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/a/mozilla.com/d/msgid/foxfood-feedback/CAF63MF3%3DZ8Lav-e6FbXdG%2B_%3Dz5uVWtw8Z-Zt%2B_uehobSU7Hrhw%40mail.gmail.com >> <https://groups.google.com/a/mozilla.com/d/msgid/foxfood-feedback/CAF63MF3%3DZ8Lav-e6FbXdG%2B_%3Dz5uVWtw8Z-Zt%2B_uehobSU7Hrhw%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > > -- > You received this message because you are subscribed to the Google Groups > "foxfood-feedback" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/a/mozilla.com/d/msgid/foxfood-feedback/CAFB_yNzWB-%2B%3DQY0nDskmJQ-%3DoOFbG9FHV21odx5rKMsqKniW0A%40mail.gmail.com > <https://groups.google.com/a/mozilla.com/d/msgid/foxfood-feedback/CAFB_yNzWB-%2B%3DQY0nDskmJQ-%3DoOFbG9FHV21odx5rKMsqKniW0A%40mail.gmail.com?utm_medium=email&utm_source=footer> > . >
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
