| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
If we want to allow destroying the main window, we need to also
create it dynamically. Use an intermediate root QtObject to take
care of this.
Change-Id: I04ba2ac7b1a24ea75ee1eecc3ab9157e8645ab30
Reviewed-by: Andras Becsi <andras.becsi@theqtcompany.com>
|
| |
|
|
|
|
|
|
|
| |
- Remove the unnecessary intermediate ApplicationEngine class
- Rename quickwindow.qml to BrowserWindow.qml
- Move the injected Utils QObject into utils.h
Change-Id: I3b0551e2bf477fc94640c71736de26c46c1ab633
Reviewed-by: Andras Becsi <andras.becsi@theqtcompany.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch exposes downloadStarted and downloadFinished
signals on the WebEngineProfile to notify about downloads.
The WebEngineDownloadItem exposes a subset of Chromium's
content::DownloadItem functionality.
For now we expose minimal requirements to be able to control
downloads in QML but this can be extended in the future.
This patch also adds a DownloadView to quicktestbrowser
to demonstrate the usage of the new API.
[ChangeLog][QtWebEngineQML] Add QtQuick download API
Change-Id: I8d8f0daf02c4e0151000427fc2a4b37d28b9db52
Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>
|
| |
|
|
|
|
|
| |
and add shortcuts in the examples (with a basic UI in the test browser)
Change-Id: I237a04cf0b1fce2e0c6f8a19891ff3cb51727a40
Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>
|
| |
|
|
|
|
|
|
|
| |
To have a more "discoverable" UX, and cleaner UI (requiring private
QML API for now).
Change-Id: Ic275287d429149a1c353a1cbdc5b7f9b19e57410
Reviewed-by: Gabriel de Dietrich <gabriel.dedietrich@digia.com>
Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>
|
| |
|
|
|
| |
Change-Id: Ia04c86285543fa10cd5d11c52bf2b6f1b1e20db5
Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>
|
|
|
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 <pierre.rossi@gmail.com>
|
