Confirmed users, Bureaucrats and Sysops emeriti
2,088
edits
Add-on SDK in Firefox: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
}} | }} | ||
{{FeaturePageBody | {{FeaturePageBody | ||
|Feature open issues and risks=Open issues: | |||
* Need to ensure Jetpack tests are run per-checkin by default on all branches (where it makes sense) | |||
|Feature overview=Ship the Add-on SDK runtime and libraries inside Firefox. | |Feature overview=Ship the Add-on SDK runtime and libraries inside Firefox. | ||
|Feature users and use cases=* Reduced add-on size. Currently add-ons created with the SDK are 200k at a minimum. This reduces download time and installation time of add-ons, streamlining the process. | |Feature users and use cases=* Reduced add-on size. Currently add-ons created with the SDK are 200k at a minimum. This reduces download time and installation time of add-ons, streamlining the process. | ||
* Develop core features using the SDK. Firefox core developers can use the SDK libraries to build features. | * Develop core features using the SDK. Firefox core developers can use the SDK libraries to build features. | ||
* Repacking might be simpler, or not required at all | * Repacking might be simpler, or not required at all | ||
|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. | ||
| Line 23: | Line 25: | ||
* Allow sharing of modules across add-ons. | * Allow sharing of modules across add-ons. | ||
* Allow interdependency at the add-on level. | * Allow interdependency at the add-on level. | ||
|Feature implementation plan=# Allow one-way syncing of a Git repository to a Mercurial repository | |Feature implementation plan=# Allow one-way syncing of a Git repository to a Mercurial repository | ||
# Create a Git repo that's specifically for pulling from | # Create a Git repo that's specifically for pulling from | ||