diff options
Diffstat (limited to 'src/webenginewidgets/doc/src/qtwebenginewidgets.qdoc')
| -rw-r--r-- | src/webenginewidgets/doc/src/qtwebenginewidgets.qdoc | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/src/webenginewidgets/doc/src/qtwebenginewidgets.qdoc b/src/webenginewidgets/doc/src/qtwebenginewidgets.qdoc index 2c5791fdd..c2a3ac329 100644 --- a/src/webenginewidgets/doc/src/qtwebenginewidgets.qdoc +++ b/src/webenginewidgets/doc/src/qtwebenginewidgets.qdoc @@ -66,6 +66,25 @@ Chromium itself can be found on the \l{http://www.chromium.org} {Chromium Project} Web site. + \section1 Should I use Qt WebEngine or Qt WebKit? + + Qt WebEngine supercedes the \l{Qt WebKit Widgets}{Qt WebKit} module, which + was based on the WebKit project, but isn't actively synchronized with the + upstream WebKit code since Qt 5.2. + + Chromium provides its own network and painting engines and is developed + tightly together with its dependent modules, thus Qt WebEngine provides + better and more reliable support for the latest HTML5 specification. + For this reason Qt WebEngine is however heavier than Qt WebKit and doesn't + give direct access to the network stack and the HTML document through C++ APIs. + + For new code we suggest using Qt WebEngine, but it makes sense to continue + using Qt WebKit for applications that are in need of a deeper C++ API than + having better and up-to-date support for HTML, CSS and JavaScript features. + + For tips on how to change a Qt WebKit application to use Qt WebEngine, see + \l{Porting from Qt WebKit to Qt WebEngine} + \section1 Including In Your Project To include the definitions of the module's classes, use the |