summaryrefslogtreecommitdiffstats
path: root/examples/webenginewidgets/browser/browserapplication.h
Commit message (Collapse)AuthorAgeFilesLines
* Rename the widget browser example demobrowserAllan Sandfeld Jensen2015-09-031-127/+0
| | | | | | | | | 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>
* Reintroduce private browsing mode for example browserAllan Sandfeld Jensen2015-05-111-0/+8
| | | | | | | Uses QWebEngineProfile to support private browsing mode. Change-Id: I78fa712d2425eb2df519594ee3fa5639bbcbebf6 Reviewed-by: Andras Becsi <andras.becsi@theqtcompany.com>
* Update copyright headersJani Heikkinen2015-02-161-9/+9
| | | | | | | | | 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>
* Examples: Replace deprecated Q_WS_MAC defines with Q_OS_OSX.Michael BrĂ¼ning2014-10-061-2/+2
| | | | | Change-Id: I2d9f23a9aa8871df7b3054628a2db49ea858c522 Reviewed-by: Allan Sandfeld Jensen <allan.jensen@digia.com>
* Add api to get the favicon URLAllan Sandfeld Jensen2014-07-301-3/+4
| | | | | | | | | | | Adds one of the missing pieces of the QWebFrame and QWebView APIs. Unlike the QtWebKit version this only fetches the favicon URL, and not the icon. This is because we do not want to implement an icon database, and that the icon would be loaded asynchronous anyway, bringing no guarantee to be a valid icon/image yet. Change-Id: I227311ae3676044da850e687b82bee752b5079c8 Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>
* Rename example directories to match the source install destinationJocelyn Turcotte2014-03-191-0/+118
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>