canmove, Confirmed users
548
edits
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
{{FeatureStatus | {{FeatureStatus | ||
|Feature name=Simplify the Add-on SDK | |Feature name=Simplify the Add-on SDK | ||
|Feature stage= | |Feature stage=Planning | ||
|Feature status=In progress | |||
|Feature version=TBD | |Feature version=TBD | ||
|Feature health=OK | |Feature health=OK | ||
Line 25: | Line 26: | ||
* 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? | ||
* Remove some generalization code contained in the python portions of the SDK | |||
|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. | ||
|Feature implementation plan=Many of the items listed in the overview will begin in conjunction with our P1 work so developers do not have to devote 100% of their time to just one feature. Therefore, the status of this full-set feature will be in progress until all items are completed or determined to be part of another feature, or no longer needed or wanted. | |||
}} | }} | ||
{{FeatureInfo | {{FeatureInfo |