path: root/examples/webengine
Commit message (Collapse)AuthorAgeFilesLines
* Prepend the namespace for ElideMiddle.Zeno Albisser2014-05-161-1/+1
| | | | | Change-Id: If2ac075f095c83fd53c939d3494c7807328ed2dc Reviewed-by: Pierre Rossi <>
* Add linkHovered signal to the QQuickWebEngineViewSzabolcs David2014-05-051-0/+32
| | | | | | | | I dropped hovered title support from the QtWebKit API, it seems we don't need that logic. Change-Id: I5617c295344512a35aa526a6f1307f0b21f866d6 Reviewed-by: Andras Becsi <>
* Centralize OpenGL initializationSimon Hausmann2014-03-312-9/+3
| | | | | | | | | | We now require the user to use QWebEngine::initialize() in main (preferably) and print out an error message if this wasn't set up accordingly. This limits the use of private scene graph API to inside QWebEngine and offers public API for users of the API. Change-Id: I787c176a85ab7784dbc8787d9876960b4872959e Reviewed-by: Jocelyn Turcotte <>
* Fix typo in quicknanobrowser.proPeter Varga2014-03-261-2/+1
| | | | | | | | | Remove ContextMenuExtras.qml entry from the project file of the quicknanobrowser. It is unnecessary after the quicknanobrowser fork. Change-Id: I87055413392e14817429678f29b520e55cafbbd1 Reviewed-by: Andras Becsi <>
* Fork the quicknanobrowser as tests/quicktestbrowserJocelyn Turcotte2014-03-195-129/+1
| | | | | | | | | | | | | | This also removed experimental API uses from the quicknanobrowser example, which should be used mainly for documentation purposes. The quicktestbrowser should be the one that we use from now on as a raw testbed of new APIs. As with other targets in the tests directory, it will only be built by default if Qt is configured with -developer-build (and without -nomake tests). Change-Id: Ib4461c898cd3227bbb810493daac4d841d0d8f3e Reviewed-by: Pierre Rossi <>
* Rename example directories to match the source install destinationJocelyn Turcotte2014-03-1912-0/+604
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 <>