homescreenhandler: use applaunchd for app activationmarlin_12.91.0marlin/12.91.012.91.0

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

1 files changed, 7 insertions, 0 deletions

diff --git a/homescreen/src/homescreenhandler.h b/homescreen/src/homescreenhandler.h
index 6dbf31b..d94740b 100644
--- a/homescreen/src/homescreenhandler.h
+++ b/homescreen/src/homescreenhandler.h
@@ -20,6 +20,7 @@
 #include <QObject>
 
 #include "applicationlauncher.h"
+#include "applaunch_interface.h"
 
 #include "shell.h"
 #include <string>
@@ -50,9 +51,15 @@ public:
 signals:
     void showNotification(QString application_id, QString icon_path, QString text);
     void showInformation(QString info);
+
+public slots:
+    void appStarted(const QString& application_id);
+    void appTerminated(const QString& application_id);
+
 private:
     ApplicationLauncher *mp_launcher;
     Shell *aglShell;
+    org::automotivelinux::AppLaunch *applaunch_iface;
 };
 
 #endif // HOMESCREENHANDLER_H