canmove, Confirmed users
548
edits
Features/Jetpack/Simplify the Add-on SDK: Difference between revisions
Features/Jetpack/Simplify the Add-on SDK (view source)
Revision as of 17:24, 8 July 2011
, 8 July 2011no edit summary
No edit summary |
|||
| Line 1: | Line 1: | ||
{{FeatureStatus | {{FeatureStatus | ||
|Feature name= | |Feature name=Features/Jetpack/Simplify the Add-on SDK | ||
|Feature stage=Draft | |Feature stage=Draft | ||
|Feature version=TBD | |Feature version=TBD | ||
| Line 24: | Line 24: | ||
* support putting all addon files into a single top-level directory for simple addons that don't have enough files to justify breaking them up into data/, lib/, and test/ subdirectories | * support putting all addon files into a single top-level directory for simple addons that don't have enough files to justify breaking them up into data/, lib/, and test/ subdirectories | ||
* resolve relative and root-relative text strings passed to URL parameters relative to the location of the script and top-level addon directory for all URL parameters, respectively, so addons can specify "/data/foo.txt" in place of require("self").data.url("foo.txt") | * resolve relative and root-relative text strings passed to URL parameters relative to the location of the script and top-level addon directory for all URL parameters, respectively, so addons can specify "/data/foo.txt" in place of require("self").data.url("foo.txt") | ||
* require in content scripts? | * require in content scripts? | ||
|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. | |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 | ||