On 02/26/2016 01:26 PM, Ehsan Akhgari 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.
Look at what you need to implement to get the simplest gecko based product that builds with --enable-application=my_great_app and compare it to the same project as an Electron app. There's no surprise why people are not using gecko here. Just having to build a custom gecko for N platforms is big drawback. Oh, and you're obviously Tier 100 when you do that, so you have to chase gecko's changes, sec fixes etc. It's not whether it's doable (especially not whether a gecko engineer can do it) but if it's a reasonable tool for others to use. Gecko is not one unfortunately. -- Fabrice Desré Connected Devices Mozilla Corporation _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
