This example demonstrates how to convert 'dic' dictionary files
into 'bdict' binary format using qwebengine_convert_dict tool.
It shows how to implement language selection. It adds two dummy
dictionaries.

Change-Id: Iffc23a0ed4e51cbc749f666c8f565fafb3739a9b
Reviewed-by: Michael Brüning <michael.bruning@qt.io>

Demobrowser changes:
* remove QLocalServer/Socket
* remove AutoSaver
* remove restoreLastSession
* remove general QSettings
* remove downloadManager
* remove bookmarkManager
* remove historyManager
* remove searchBar
* favor setStyleSheet over overriding paint methods
* use lambdas where suitable
* use QProgressBar instead of own painted widget
* use QToolButton instead of own painted buttons
* remove QStackWidget, use single UrlLineEdit per window
  instead of per tab
* split files to keep own classes: webpage and webview
* remove tracking windows by QPoiner
* remove WebPageActionMapper, TabBar classes
* remove QDrag dead code
* remove special OS X close app handling
* fix encapsulation, clean up application logic

Change-Id: I4849b6a2de739dea4f01229abdb90418601a2397
Reviewed-by: Kai Koehne <kai.koehne@theqtcompany.com>
Reviewed-by: Alexandru Croitor <alexandru.croitor@theqtcompany.com>

Task-number: QTBUG-51383
Change-Id: I872bdae7267e7dbf2a93a831d435517bcd4bad64
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@theqtcompany.com>
Reviewed-by: Michal Klocek <michal.klocek@theqtcompany.com>
Reviewed-by: Joerg Bornemann <joerg.bornemann@theqtcompany.com>

A cookiebrowser shows collected cookies during
browsing, users can view cookie content, delete
and add new cookies.

Change-Id: Ib9cdc29e7ca34c488dd249b44f9e32491517bd60
Reviewed-by: Kai Koehne <kai.koehne@theqtcompany.com>

The name "fancybrowser" tricks people into thinking that this is the
reference browser example. But this example is a very simple browser
with an additional fancy content manipulation feature.
Rename this example to contentmanipulation to reflect reality.

Change-Id: I200b701acdc4de1210b550b9f054753e5f1d1ea4
(cherry-pick from eb8eb72e

)
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@theqtcompany.com>

This example shows the use of QWebEngineView in a hybrid application,
and how one can leverage JavaScript libraries to provide functionality
with minimal effort.

QWebEngineView is used to preview a MarkDown document. The text is
exposed to the view through QWebChannel. An off-the-self js library
converts it to HTML.

Change-Id: I24c38106da3ec18975c71c16f7f7a58e93142f9e
Reviewed-by: Joerg Bornemann <joerg.bornemann@theqtcompany.com>

The name "fancybrowser" tricks people into thinking that this is the
reference browser example. But this example is a very simple browser
with an additional fancy content manipulation feature.
Rename this example to contentmanipulation to reflect reality.

Change-Id: I200b701acdc4de1210b550b9f054753e5f1d1ea4
Reviewed-by: Michael Brüning <michael.bruning@theqtcompany.com>
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@theqtcompany.com>
Reviewed-by: Kai Koehne <kai.koehne@theqtcompany.com>

The browser example already uses the name demobrowser internally, this
changes the external name to make it easier to refer to explicitly, and
avoid users thinking fancybrowser is the better example.

Change-Id: Ic093eb4881352b5f796bf565df01edb929aba39c
Reviewed-by: Joerg Bornemann <joerg.bornemann@theqtcompany.com>

To allow the qt5.git integration, allow the build to succeed if the
repository is checked out on a platform that we don't maintain.

This is the initial list of platforms that we want the integration
to succeed and we can add new ones once we start maintaining them.

Change-Id: Idce2a84eb8d5b1ef7f14d399fe013f666b479108
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

We actually already depend on dev (5.4) in other areas.

Change-Id: Iab297a51ab06209a96f11f97c74463d38203eda8
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

Change-Id: Icecb6b716a45b4682ddd9b16383f3aa4a5acb312
Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>

This means that widgets application now need to setup the GL context
sharing as well. QWebEngineWidgets::initialize() must be called,
which has the same effect as QWebEngine::initialize().
The QtWebEngineWidgets now depends on the QtWebEngine module to make
this happen.

Since QOpenGLWidget is only available in Qt 5.3, this patch also
disables the webenginewidgets module completely when building using
Qt 5.2.

Change-Id: I0e99a779d1eb080f2ccf5a338ff0763ad64e6eba
Reviewed-by: Simon Hausmann <simon.hausmann@digia.com>

To match other modules example directory structures we should deploy our
examples in a directory matching the module name, webengine and
webenginewidgets in our case.

qmake uses the relative directory of each example up to the upper "examples"
directory to decide where they will be deployed when running the sources
install target.

Change-Id: I59ce7ff8a30f98fad20064c7eecf72b784f1d275
Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>

This example hasn't been touched since we imported QtWebKit examples.
If we need to have a more test-purpose widgets browser in the future,
we can dig it back from the history.

Change-Id: Icee9bd7f09827a97b33c6783b87311e331d963b1
Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>

Change-Id: Ia61fbe3ef6b76c7530d10d4a3305d4208b3469ef
Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>

The ifdefs should later be removed along with the feature
implementations.

Change-Id: If73f4c4c02c00e90d6cf54c6a08bb37f43fa95bc
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

This also ajust the name to be consistent with other Qt examples.
- Move nano browser one directory level down,
  also renaming them to match their target name
- Remove the dashes from the target names
- Rename the qtquick example directory to quick, matching the style in lib

Change-Id: I4a5e31be0b919ae596eadbf731be52372ae61151
Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>

This is the first step to making proper Qt Modules out of QtWebEngine.
The Widgets integration becomes a proper C++ Qt Module while we make
the QtQuick side a QML plugin for now (could probably be promoted if
the need arises).

Code-wise, this means the introduction of a WebContentsAdapterClient
interface that is subclassed by the private implementation of our API
classes for delegation of things that are UI specific. Functionality
from WebContents and the like is exposed via the WebContentsAdapter.

Change-Id: I4ca3395b9fe8502a24e36002cfd5af44067bb6e8
Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>

Cleaner than deciding on startup with an env variable