summaryrefslogtreecommitdiffstats
path: root/src/webview/qtwebviewfunctions.cpp
Commit message (Collapse)AuthorAgeFilesLines
* Doc: Make documentation for QtWebView::initialize() visible.Topi Reinio2015-10-281-0/+1
| | | | | | | | | | Document the QtWebView module, add the Q_WEBVIEW_EXPORT macro to .qdocconf, edit the help project sections and link to the C++ module documentation from the overview. Change-Id: I3deb34e8067278915610e24a15baf52e365629fb Reviewed-by: Leena Miettinen <riitta-leena.miettinen@theqtcompany.com> Reviewed-by: Christian Stromme <christian.stromme@theqtcompany.com>
* Use Qt WebEngine by default on OS X.Christian Strømme2015-09-241-1/+1
| | | | | | | | | | This change reverts back to using Qt WebEngine as a backend on OS X, as there are still challenges that needs to be solved when using the native WebView implementation, e.g., make it possible to use it without disabling batched rendering. Change-Id: I9cc95233990055d59480ad4d47ebf3da4ebb07f1 Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@theqtcompany.com>
* Add missing header in qtwebviewfunctions.v5.6.0-alpha1Christian Strømme2015-08-281-0/+4
| | | | | | | | We need to include the header for QByteArray, as it's required when calling qputenv(). Change-Id: I245d769b050525719dc6db202a6724ce887ba4a7 Reviewed-by: Yoann Lopes <yoann.lopes@theqtcompany.com>
* Fixed bugs in license headerJani Heikkinen2015-08-251-9/+9
| | | | | | | | | Two files were using old LGPL license headers and that's why license header tests were failed. Changed those files to use LGPLv3 header template Change-Id: I95bd010087b83c6aa174d53e7c2378bdd9e57c70 Reviewed-by: Simon Hausmann <simon.hausmann@theqtcompany.com>
* Add initialize functionChristian Strømme2015-08-101-0/+74
The initialization function will set-up any platform specific requirements needed to display the WebView correctly. Initially we tried to avoid this, as it's not a very nice approach, and it was only needed when QtWebEngine back-end was the used (see: QtWebEngine::initialize()). Since we now require special set-up for OS X as well, it has become unreasonable to expect that the user should implement this logic in their application and that it's more convenient if we provide a uniform solution to make the WebView work on all platforms. The implication of this change, is that we now actually expose a C++ API and will therefore need to export the module again (making it a non-internal module). Change-Id: I87678db7cd50b25465bcf623c008f04a4cffd7df Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@theqtcompany.com>