canmove, Confirmed users
548
edits
Features/Jetpack/Traditional Addon Conversion to SDK Platform: Difference between revisions
Features/Jetpack/Traditional Addon Conversion to SDK Platform (view source)
Revision as of 08:40, 14 July 2011
, 14 July 2011no edit summary
No edit summary |
No edit summary |
||
| Line 29: | Line 29: | ||
Develop tools that identify kinds of chrome modification and suggest SDK APIs that developers can use to make similar kinds of modifications. Develop tools that identify XPCOM services and automatically convert them to CommonJS modules. Develop tools that identify code that runs at startup and automatically converts it to the addon's main code. | Develop tools that identify kinds of chrome modification and suggest SDK APIs that developers can use to make similar kinds of modifications. Develop tools that identify XPCOM services and automatically convert them to CommonJS modules. Develop tools that identify code that runs at startup and automatically converts it to the addon's main code. | ||
|Feature landing criteria=We have determined that with the release of our support for e10s, we will have to break our low-level APIs (not the commonly used high-level APIs). Because of this, it is best if we deliver any tools and messaging around this feature until after we have landed this breaking-change feature. | |||
}} | }} | ||
{{FeatureInfo | {{FeatureInfo | ||