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:33, 7 July 2011
, 7 July 2011no edit summary
No edit summary |
|||
| Line 19: | Line 19: | ||
Thus FFM addons are as important as FFD addons. So it is just as important for the new addon platform provided by the SDK to support building addons for FFM. | Thus FFM addons are as important as FFD addons. So it is just as important for the new addon platform provided by the SDK to support building addons for FFM. | ||
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 build an addon for FFM, FFD, or both browsers. | |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 build an addon for FFM, FFD, or both browsers. | ||
|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. | ||
It must enable an addon to determine which browser the addon is loaded in. | It must enable an addon to determine which browser the addon is loaded in. | ||
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. | |||
|Feature functional spec='''Phase One''' | |Feature functional spec='''Phase One''' | ||
| Line 41: | Line 43: | ||
'''Phase Four''' | '''Phase Four''' | ||
Design and implement additional API features for capabilities that are specific to mobile devices. | Design and implement additional API features for capabilities that are specific to mobile devices. | ||
}} | }} | ||
{{FeatureInfo | {{FeatureInfo | ||