| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Changes:
- Switch to using the new app launcher API wrapper from libqtappfw
in order to migrate to the new gRPC based API implementation.
- The appStarted and appTerminated methods in HomescreenHandler have
been renamed to activateApp and deactivateApp, respectively, to
better reflect what they do. A new processAppStatusEvent method
had been added that calls them as appropriate based on the event
from the AppLauncherClient status update signal.
- The copyright headers in the source files have been tweaked to
remove the Apache license boilerplate in favour of a SPDX license
tag.
- The code in main.cpp that was not formatted with Linux-style has
been reformatted to match the rest of the file.
Bug-AGL: SPEC-4559
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
Change-Id: I236cb6a412945a6df7d35652c55f664264964f9c
(cherry picked from commit 20f629dd6d8628611d950073c4f7a0446c40365a)
|
|
When the current app window is closed, the current behavior depends on
whether this action terminates the app:
- if the app is terminated, then we switch back to the launcher
- in the other case, we display the background, even if other apps are
running
In order to implement a better behavior, we should keep track of active
apps and switch back to the previously active one when the current app
window is closed.
Bug-AGL: SPEC-4222
Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>
Change-Id: Idf1fe42886e95e2b37349b066204fde002d7c3b5
|
|
As part of the App FW rework, we introduced a new app launcher service,
accessible through D-Bus. This service accepts requests to activate
applications, and notifies when a application successfully activated or
terminated.
Requests for activation are handled by a separate `launcher` application
for now, so we only need to listen on incoming signals in order to react
to those:
- when an application successfully started or is switched to, ask the
compositor to activate it
- when an application terminates, activate the launcher so the user
isn't facing a "blank" display
Bug-AGL: SPEC-4160
Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>
Change-Id: I7369944570651b45ec9dcca9ccde3dfd75719c3b
|
|
Changes:
- Remove application framework build scripts, and update the
application qmake file to just build a "homescreen" binary
and support installing it to /usr/bin.
- Remove voice API related code. Some of the associated QML
and images for the UI have been retained in case equivalent
functionality is re-added in the future.
- Remove or stub out various app framework API access for the
homescreen and launcher bindings, and comment out usage of
the Qt wrappers from libqtappfw (e.g. Bluetooth). The aim is
to provide a replacement library or libraries for the latter
that provide the same functionality.
- Remove the old homescreen API documentation and do an initial
update of the build instructions in README.md.
Bug-AGL: SPEC-4121
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
Change-Id: Iab979c8e1341f2da0384f88f163a977b03664600
|
|
The switch to the new compositor removed the callback to update the
top panel button highlight since it was being driven by the
Event_ScreenUpdated event from the old windowmanager. For now, work
around this by driving the ApplicationLauncher's setCurrent method
from the appropriate place in the HomescreenHandler object's
tapShortcut method. If a generic mechanism for notifications on
application expose becomes available via agl-shell-desktop, that
should be used instead.
Additionally, add an explicit call to setCurrent on initialization to
highlight the top panel Launcher button, matching the actual initial
UI state.
Bug-AGL: SPEC-3510
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
Change-Id: Ied5dd8e78195d061585510e60a758559ca4f69b3
|
|
Bug-AGL: SPEC-3447
Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
Change-Id: I7da44ec333217d355ba643d2d21bea7d8940ad2b
|
|
homescreen-service: add five verbs.
1.showWindow: instead of tap_shortcut and show onscreen.
2.hideWindow: used when want to hide onscreen.
3.replyShowWindow: used when post onscreen reply information to application.
4.showNotification: used by application who want to display notification on homescreen top area.
5.showInformation: used by application who want to display information on homescreen botton area.
homescreen:
display notification and information.
Bug-AGL: SPEC-1931
Change-Id: Ia17a9793c5d284458009ea71eb9594a40286fa8c
Signed-off-by: wang_zhiqiang <wang_zhiqiang@dl.cn.nexty-ele.com>
|
|
Now In homescreen-service used application_id to identify
different application, so use appid instead of appname
in "tap_shortcut" parameter.
Bug-AGL: SPEC-1764
Change-Id: I2fdda76167c7af9af65b1135b838da1742515b8b
Signed-off-by: wang_zhiqiang <wang_zhiqiang@dl.cn.nexty-ele.com>
|
|
This reverts commit 389a02a99961f1bcc6d317ffc9223ea7f2d05023.
Bug-AGL: SPEC-1685
Change-Id: I2f659dbb53b0b781ed588d19c2f3228e3abcbb4a
Signed-off-by: Tadao Tanikawa <tanikawa.tadao@jp.panasonic.com>
|
|
Use appid between hss and apps, and check event destination in libhomescreen.
So these is no need compare code when recived Event_TapShortcut Event.
BUG-AGL: SPEC-1645
Change-Id: Idd052d3f76f83e1f5bfe46627d7698655ffad85d
Signed-off-by: zheng_wenlong <wenlong_zheng@nexty-ele.com>
|
|
We decide to use homescreen instead of homescreen-2017.
Copy the source code from homescreen-2017 and delete word "-2017".
Revision: b4db06287bc997ded71deab50ff0ff5889b09e1f
Bug-AGL: SPEC-1549
Change-Id: Id77226b7ce35bbc29c868281c37b76ea3f930ad5
Signed-off-by: zheng_wenlong <wenlong_zheng@nexty-ele.com>
|
Scott Murray
Arnaud Ferraris
Marius Vlad
wang_zhiqiang
Tadao Tanikawa
zheng_wenlong