Hi all,
I want to start a discussion about Servo's Android support. The current
state is quite basic and doesn't provide what we need to cover several
interesting use cases.
So far I have identified these:
1- Full screen app (games, VR).
2- Browser with a pure html "chrome" like browser.html.
3- Browser with a native (java) chrome.
4- Reusable WebView (ServoView !) for other apps to embed.
5- Providing a CustomTab implementation (Chrome and Fennec support that).
1- and 2- are the only cases we can cover with the current platform
code. However I believe that we need more flexibility and that the key
here is to implement the ServoView, as it is a dependency for all the
other cases.
ServoView would expose an API as close as possible to
https://developer.android.com/reference/android/webkit/WebView.html to
ease reusability in the Android community.
This ties into the overall embedding story, which I discussed with Paul.
We have alignment there, relying mostly on 2 aspects:
- the embedding support provided by libservo will be low level enough to
let us build the ServoView and CustomTabs on top of it. Expect a lot of
JNI fun!
- glutin may not be something we want to keep using. I haven't looked in
details yet but glutin may be too high level an opinionated for us in
this context (eg. can glutin let us display several ServoViews?).
So my current plan of action is to verify whether glutin is suitable or
not on Android, fix that if needed and then start on a ServoView
implementation.
Thoughts?
--
Fabrice Desré
Emerging Technologies
Mozilla Corporation
_______________________________________________
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
