Features/Jetpack/Make Add-on SDK Hug the Web Harder: Difference between revisions

no edit summary
No edit summary
Line 15: Line 15:
But some aspects of the SDK environment are not as weblike as they could be. Addon code runs in a JavaScript context that does not have access to web globals like XMLHttpRequest. And the SDK doesn't support the emerging standard for modules in JavaScript (nor does Firefox at this point).
But some aspects of the SDK environment are not as weblike as they could be. Addon code runs in a JavaScript context that does not have access to web globals like XMLHttpRequest. And the SDK doesn't support the emerging standard for modules in JavaScript (nor does Firefox at this point).


To reduce the barrier to entry for web developers to build Firefox addons to the absolute minimum, the SDK should provide the most weblike programming environment possible.  
To reduce the barrier to entry for web developers to build Firefox addons to the absolute minimum, the SDK should provide the most weblike programming environment possible.
|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.  
 
Additionally, we might support XHR, SetTimeout, and SetInterval
 
In the future we might even consider making the experience of developing an add-on resemble creating for the web by moving main.js to main.html and making the relative paths work as they do when developing a website.
 
|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.
}}
}}
{{FeatureInfo
{{FeatureInfo
canmove, Confirmed users
548

edits