117
edits
Features/Jetpack/CFX in JS: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
|Feature status=In progress | |Feature status=In progress | ||
|Feature health=OK | |Feature health=OK | ||
|Feature status note=Trying to split the train in multiple wagons. | |||
Between planning and starting development. | |||
}} | }} | ||
{{FeatureTeam | {{FeatureTeam | ||
| Line 21: | Line 23: | ||
|Feature non-goals=Execute "Add-on SDK as an Addon" or "Ship SDK via AMO" features. | |Feature non-goals=Execute "Add-on SDK as an Addon" or "Ship SDK via AMO" features. | ||
CFX in JS shouldn't aim to ship the SDK in a XPI in order to host it on AMO, even if it will most likely help these two goals. It may just end up being a requirement for them. | CFX in JS shouldn't aim to ship the SDK in a XPI in order to host it on AMO, even if it will most likely help these two goals. It may just end up being a requirement for them. | ||
|Feature implementation plan=This work can easily be splitted in multiple, eventually parallel steps: | |||
- Be able to execute Javascript code hosted in an addon from cfx in python | |||
Then we would be able do implement following CFX workflow steps in JS: | |||
- Install and execute an Addon | |||
- Generate the XPI out of the manifest | |||
- Compute the manifest out of packages/modules | |||
- Read/seek for packages/modules on filesystem | |||
- Interpret command line options | |||
- Build a command line application with mozilla-platform/Firefox | |||
- Write shell/bash scripts in order to setup cfx environnement (equivalent of source bin/activate) | |||
|Feature implementation notes=Main tracking bug: https://bugzilla.mozilla.org/show_bug.cgi?id=746124 | |||
}} | }} | ||
{{FeatureInfo | {{FeatureInfo | ||