Add-on SDK in Firefox: Difference between revisions

m
no edit summary
(mention another use case (porting old add-ons))
mNo edit summary
Line 29: Line 29:
* Repacking might be simpler, or not required at all
* Repacking might be simpler, or not required at all
* Scratchpad could be used as an offline version of the Add-on Builder.
* Scratchpad could be used as an offline version of the Add-on Builder.
* Old school add-ons can more easily leverage features from the addon-sdk, which should help them port older add-ons.
* Old school add-ons can more easily leverage features from the add-on sdk, which should help them port older add-ons.
|Feature dependencies=* Packageless Jetpack proposal may be a dependency ([https://github.com/mozilla/addon-sdk/wiki/JEP-packageless view])
|Feature dependencies=* Packageless Jetpack proposal may be a dependency ([https://github.com/mozilla/addon-sdk/wiki/JEP-packageless view])
|Feature requirements=* Add-on SDK loader and API libraries are shipped inside Firefox, removing the necessity of packaging them inside each add-on.
|Feature requirements=* Add-on SDK loader and API libraries are shipped inside Firefox, removing the necessity of packaging them inside each add-on.
Confirmed users
250

edits