On 08/19/2015 07:07 AM, Chris Mills wrote: > >> On 7 Aug 2015, at 17:51, Fabrice Desré <[email protected]> wrote: >> >> On 08/07/2015 09:20 AM, Michael Henretty wrote: >> >>> It sounds like the way gecko will distinguish between the add-on and the >>> app install path is whether the package zip contains `manifest.webapp` >>> or `manifest.json`. Is that correct? >> >> If there is no manifest.webapp, we look for manifest.json. If it's >> there, we consider it's an add-on; if not, error! If there is a >> manifest.webapp, we treat that as an app like usual. But I removed the >> all "customization" support. >> >> We then convert the manifest.json in a webapp manifest, so that you >> always get a usable app.manifest property, and so consumers of the >> mozApps api keep just working. >> >>> Will Settings->Add-ons need to be modified to display the new add-on >>> type? If so, this needs to land soon after the Gecko parts, otherwise >>> users won't be able to enable/disable/uninstall add-ons. If not though, >>> this means this new add-ons will still be fetch-able using mgmt.getAll >>> and will have role=addon. In this case, what happens to the deprecated >>> add-ons? Do they get returned with mgmt.getAll? Will we have a way Gaia >>> side to distinguish between them? >> >> Install/uninstall and enabling/disabling just work as before. The only >> broken thing in the add-on panel with the new gecko patch is the part >> that tells which apps are impacted by the add-on, because the patterns >> used are not in the app manifest anymore, but in manifest.json. So we'll >> have to update that. >> >>> The Hackerplace migration plan is as follows: >>> - reach out to each add-on developer and give them a step by step guide >>> to migrating to the new format (seems straightforward) >> >> Yep, I can draft something here, and I have a couple of examples. > > Remember that we already have a basic guide at > > https://developer.mozilla.org/en-US/Firefox_OS/Add-ons > > It would be great to get that guide updated asap, so perhaps we could kill > two birds with one stone here? If you give me any notes/example you were > going to write about the subject, I could use that as a quick pathway to > updating the doc.
Chris, we created an etherpad at https://etherpad.mozilla.org/converting-fxos-addons covering migration. Fabrice -- Fabrice Desré b2g team Mozilla Corporation _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
