Thank you Kai Koehne for the clarification. On Wed, Apr 5, 2017 at 4:51 PM, Kai Koehne <kai.koe...@qt.io> wrote:
> > > > -----Original Message----- > > From: Interest [mailto:interest-bounces+kai.koehne=qt...@qt-project.org] > > [..] > > With Qt 5.5 the Qt WebKit module is deprecated:(https://wiki.qt.io/New- > > Features-in-Qt-5.5#Deprecated_Functionality) > > > > QWebView uses WebKit as the backend. > > > > QWebEngineView uses Chromium as the backend. > > > > WebView with the same name has been defined in both WebKit and > > WebEngine. Hence import statement varies.[I believe this is the source of > > confusion ] > > > > import QtWebKit 3.0 > > import QtWebView 1.0 > > Not exactly. The terminology is arguably confusing here, but the > "QtWebView" import comes from the "Qt WebView" module ( > http://doc.qt.io/qt-5/qtwebview-index.html), which is a module that > abstracts different rendering engines (Qt WebEngine, native) away behind a > simple API. > > So > > --- > import QtWebView 1.0 > > WebView { > // ... > } > -- > should work both on mobile and desktop. On Android, iOS and WinRT the > native browsers are embedded, on all the rest Qt WebEngine is used (if > available). > > Regards > > Kai >
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
