On Mon, Nov 23, 2015 at 9:14 AM, Julien Wajsberg <[email protected]> wrote: > Also the longer term goal has always bean to be able to run the build system > inside Firefox (eg WebIDE). That said, WebIDE is simply running a shell > command these days.
In addition to what Andrew said, I see more value for being able to generate builds via a web service vs. using a local firefox to do builds. If we get to a future where the gaia apps are delivered via live URLs, it can be useful to have tools that are are more web hosting aware. For instance, I have wanted to play with allowing multiple versions of the email app that can be hosted at multiple subdomains, so that a user could configure a home screen icon (possibly with different colors/themes/capabilities) for each mail account, vs configuraing all the accounts in one email client. I see node based tooling much more likely to succeed for those efforts, for existing node package integration and contributor reasons. A side note on switching: initially we had some trouble with module bundling tools in a non-xpcshell approach that did not use Reflect.parse because of JS files using JS 1.8 style syntax that was not supported by the usual AST parsers. I expect the need for that specialized JS syntax now to have gone away now with ES2015 capabilities, but just something to keep in mind: if we stick with standardized or more commonly accepted syntax in our JS/CSS files, existing node-focused tooling will be more successful. James _______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
