canmove, Confirmed users
548
edits
Features/Jetpack/SDK Support for Firefox for Mobile Addons: Difference between revisions
Jump to navigation
Jump to search
Features/Jetpack/SDK Support for Firefox for Mobile Addons (view source)
Revision as of 17:43, 7 July 2011
, 7 July 2011no edit summary
No edit summary |
No edit summary |
||
| Line 20: | Line 20: | ||
Ideally, addons built using the SDK's high-level APIs should work on both FFD and FFM by default without requiring addon developers to specifically target mobile devices, f.e. high-level APIs that enable addons to introduce chrome elements should adapt those elements to the FFM and FFD interfaces. | Ideally, addons built using the SDK's high-level APIs should work on both FFD and FFM by default without requiring addon developers to specifically target mobile devices, f.e. high-level APIs that enable addons to introduce chrome elements should adapt those elements to the FFM and FFD interfaces. | ||
|Feature users and use cases=The target audience is addon developers. The use case is an add-on developer using the Add-on SDK (either directly or via the Add-on Builder) to | |Feature users and use cases=The target audience is addon developers. The use case is simply that an add-on developer using the Add-on SDK (either directly or via the Add-on Builder) will use the SDK to create and add-on with either Desktop or Mobile in mind, and that add-on works in either platform with no extra effort or thought from the developer. | ||
|Feature dependencies=The feature may depend on landing support for specific interface elements in the FFM interface. It may also depend on support for OOP addons, or at least on support for loading content scripts in separate processes, since FFM loads content in a separate process. | |Feature dependencies=The feature may depend on landing support for specific interface elements in the FFM interface. It may also depend on support for OOP addons, or at least on support for loading content scripts in separate processes, since FFM loads content in a separate process. | ||
|Feature requirements=The feature must load an addon built using the SDK in both FFD and FFM. It should make addons that use only the high-level APIs provided by the SDK work by default on both FFD and FFM, although it may require addons to provide browser-specific code if it is not possible to make all APIs "just work" in both browsers. | |Feature requirements=The feature must load an addon built using the SDK in both FFD and FFM. It should make addons that use only the high-level APIs provided by the SDK work by default on both FFD and FFM, although it may require addons to provide browser-specific code if it is not possible to make all APIs "just work" in both browsers. | ||
| Line 28: | Line 28: | ||
It may provide additional API features that are specific to mobile devices. | It may provide additional API features that are specific to mobile devices. | ||
We must also continue the work that has already begun to reduce the footprint of an add-on built with jetpack. | We must also continue the work that has already begun to reduce the footprint of an add-on built with jetpack. | ||
|Feature functional spec='''Phase One''' | |Feature functional spec='''Phase One''' | ||