| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Change-Id: Ib4e94bebdd2b2416a9ed6a5fc21e357223ab36fb
Reviewed-by: Dominik Holland <dominik.holland@qt.io>
(cherry picked from commit 6448f72561db8d176c938c2a2957dc242ede8a4b)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I474f8bc8d8a3efa7b0f8405892d56a793a88e883
Reviewed-by: Kavindra Palaraja <kpalaraja@luxoft.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These intents features are now available:
- requests from the system-ui
- disambiguation when no applicationId is specified
- requesting from/replying to an in-process app
(green is always running as a single-process app)
- private intents (blue-window-private)
- intents that require capabilities
(only the sysui and red can call rotate-window on blue)
Also, the example wrapper script is now able to deal with
developer builds.
Change-Id: I9ff2d6012b2c9cf29e32abaaa7d4fa3b3122944e
Reviewed-by: Daniel d'Andrada <daniel.dandrada@luxoft.com>
|
|
This commit adds support for Intents, aka. a loosely coupled IPC between
arbitrary applications in the AM system.
(please read https://wiki.qt.io/QtAppMan-Intents for same background
information).
The core implementation on both server and client side in this patch is not
dependent on the AM itself (apart from the common-lib for convenience sake,
but this dependency could easily be removed). There are 2 interfaces
that are implemented in the manager-lib and launcher-lib that connect the
Intent core to the actual AM and AM's qml runtime launcher.
Missing features:
- updating the list of intents on app installation and removal
- support for background services in the AM itself
- support for "file-handles" in the request and reply part
- documentation
- an example that is better focused on intents themselves
Change-Id: Ia7cab2bb569fb2cdb8e5ab7e8167e477cff3068c
Reviewed-by: Dominik Holland <dominik.holland@pelagicore.com>
|