On Friday, August 7, 2015 at 2:11:56 AM UTC+8, Fabrice Desré wrote: > Hi all, > > Work is ongoing to share the same add-on api across gecko based > products. Bill landed the toolkit and desktop support this week, and I'm > close to land the initial b2g support. This is happening in bug 1190995 > and bug 1191619. > > That means that the current add-ons will stop working and need to be > converted to the "chrome extensions" format. They are still zip files, > but without a manifest.webapp file. Instead, provide a manifest.json > that is compatible with https://developer.chrome.com/extensions/manifest . > Since we only supported script injection, the most interesting section > will be https://developer.chrome.com/extensions/content_scripts > > I'm fine with holding up landing if we want to let hackerplace hosted > add-ons some time to proceed with the conversion, but I will land late > next week at the latest. > > Fabrice > -- > Fabrice Desré > b2g team > Mozilla Corporation
Does this means the current development way, namely to install experiment Add-on via WebIDE and debug it, will not work anymore? Since now it needs a hosted `update.webapp`, which seems not a part of such flow. Also, does that means each developer now needs to implement the installation page as the article "Publishing apps yourself" describes? _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
