Thanks Simon! I was thinking/hoping that with the announced move from Webkit to Chromium there would already be a solid plan on how to support the mobile platforms. Now that I know there isn't, I'll practice more patience and/or look again into wrapping the native WebView.
Cheers, Conny On Thu, 2013-09-19 at 09:47 +0200, Simon Hausmann wrote: > On Thursday 19. September 2013 09.29.47 Cornelius Hald wrote: > > Sorry to bother again, but what's the plan now regarding QQuick2 WebView > > on Android? Is it Webkit? Chromium/Blink? Nothing? Something else? And > > when? > > The initial release of Qt for Android is not going to include any integration > of a web view (of sorts) into Qt Quick2 - unfortunately. This is not because > nobody wants it, but it is simply a limitation of resources on our side and > nobody else seems to have stepped up so far to look into it. > > For Android I can think of two approaches: > > * There may be a technical way of packaging up Chromium for Android and the > Qt > integration (Qt WebEngine). This is certainly a bigger task but you know what > you get as it involves shipping the entire engine. My guess would be that the > download is about the size of Opera for Android (~25-30 MB) plus the size of > Qt and your app. > > * A probably simpler way is to figure out how to access the Android WebView > (Java), render it into an FBO and integrate the FBO into the QtQuick 2 scene > graph. This might be doable on top of Qt for Android - I don't think it would > require any changes to Qt itself (but I may be wrong here!) > > > Eventually I hope that we can find the time and resources to look into either > of these options. If somebody else steps up first to start working on that > inside the Qt project, then it would be an opportunity for us to join. > > > Simon > > > On Thu, 2013-09-12 at 17:06 +0200, Cornelius Hald wrote: > > > Hi, > > > > > > the FAQ states: "We intend to make QtWebEngine available on all > > > platforms that the upstream Chromium project supports, with the > > > exception of Android. This also means iOS won’t be supported." > > > > > > So what are the plans for Android and iOS? We currently do not have > > > QtWebkit on those platforms and support for QtWebEngine is not planned. > > > Does that mean we won't have any WebView at all for Android and iOS or > > > are some kind of wrappers around native widgets planned for those > > > systems? > > > > > > Thanks! > > > Conny > > > > > > On Thu, 2013-09-12 at 12:03 +0000, Knoll Lars wrote: > > > > Hi, > > > > > > > > As many of you know, we've been doing some research on a (chromium > > > > based) > > > > new web engine for Qt during spring and summer. I wanted to let you know > > > > that we've now come to the conclusion that we want to continue these > > > > efforts in the future. > > > > > > > > Please check > > > > http://blog.qt.digia.com/blog/2013/09/12/introducing-the-qt-webengine/ > > > > for > > > > all the details. > > > > > > > > Cheers, > > > > Lars > > > > > > > > _______________________________________________ > > > > Development mailing list > > > > Development@qt-project.org > > > > http://lists.qt-project.org/mailman/listinfo/development > > > > > > _______________________________________________ > > > Development mailing list > > > Development@qt-project.org > > > http://lists.qt-project.org/mailman/listinfo/development > > > > _______________________________________________ > > Development mailing list > > Development@qt-project.org > > http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
