On 26 February 2016 at 21:26, Ehsan Akhgari <ehsan.akhg...@gmail.com> wrote:
> Without intending to start a shadow discussion on top of what's already > happening on the internal list (sadly), to answer your technical > question, the "platform"/Firefox point is a false dichotomy. As an > example, you can create a new application target similar to browser, > b2g/dev or mobile/android, select that using --enable-application, and > start to hack away. That should make it possible to create a > non-Firefox project on top of Gecko. You can use an HTML file for > browser.startup.homepage, and you can use <iframe mozbrowser> if you > need to load Web content. So it's definitely possible to achieve what > you want as things stand today. > OK, so to follow this logic in the case of B2G, your recommended solution would be to transform /b2g/chrome/content/shell.html [1] into a replacement for Gaia's system app and land that code directly in mozilla-central? That could potentially work for the B2G use case and would remove an entire layer from the architecture which sounds great. But it would mean putting that code in mozilla-central rather than a completely separate project on GitHub. Ben 1. https://dxr.mozilla.org/mozilla-central/source/b2g/chrome/content/shell.html _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
