Setting the Qt::AA_EnableHighDpiScaling attribute makes sure that the
scrollbars are scaled, and that the default zoom level is sensible.

Task-number: QTBUG-54113
Change-Id: I0ae7eb97cb9e2824e7f9b92d77cf2986cac66685
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>

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>

From Qt 5.7 -> examples are lisenced under BSD license, see
http://blog.qt.io/blog/2016/01/13/new-agreement-with-the-kde-free-qt-foundation/


Updated license headers to use new BSD header

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

Change-Id: I98924e5f8754b7b2ed095abf00eb73fa26399b2d
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 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>

Qt copyrights are now in The Qt Company, so we could update the source
code headers accordingly. In the same go we should also fix the links to
point to qt.io.

Change-Id: Ieb6bac7a1be5c25eb7cb917495b58b6a870ca6d4
Reviewed-by: Pierre Rossi <pierre.rossi@theqtcompany.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>

Import the sources as-is, without adding it to the build, to allow
performing diffs later on the changes that were needed to port it
to use QtWebEngine and manage source compatibility issues.

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

Change-Id: I58d83f4f33728f92e4bf13b6be30b15528fdd033
Reviewed-by: Zeno Albisser <zeno.albisser@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>

Cleaner than deciding on startup with an env variable

This layers things properly to be able to implement the UI in the
example application instead of directly in shell_qt.cpp.

This is still using global variables to allow the Shell platform
code to do callbacks to the API classes. This should go away once
we properly implemented a WebContentsDelegate.

Some more start-up fixes and a hack for test command line options for debugging multi-process startup