On 2013-09-01, at 18:13 , Mark Finkle <[email protected]> wrote: > Work has been continuing on GeckoView, the Gecko rendering engine wrapped in > an Android widget [1].
So, let me start off by saying how excited I am about this work! I think it will likely be the basis of most of the Mobile Prototype add-ons I make, and will make those parts of my job quite a bit easier. :) > Some other ongoing work includes creating proper bindings/interfaces for > GeckoView so it's easy to use from a host application. I'm pretty happy with the interface you've described here. It seems consistent and makes sense to me. The only thing that I think would be useful that you're missing is something along the lines of addJavascriptInterface from WebView. I needed to use it in a previous prototype (terrible diff here) to notify the chrome of various in-content things happening. I think you could probably satisfy my use-cases with a generic extension to GeckoViewContent (something like "onReceivedEvent"?), if that seemed more like something you would want to implement. > The spirit of this structure is to not create a "Full Web Browser in a > Widget", but to push a lot of the management and 100% of the UI to the host > app. GeckoView should do the minimum amount of encapsulation. I don't know if the Addon-SDK people are reading this list, but I would be interested in hearing their comments on this interface, and whether it could help them implement parts of their API… Thank you, Blake. -- Blake Winton UX Engineer [email protected]
_______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
