Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>

Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>

The launcher should hide once an application has been launched, so we
get back to either the desktop or the previously open app when closing
the current window.

Moreover, this fixes an issue introduced in a previous commit where the
launcher would be shown when launching an app from the favorites bar.
Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>

When multiple applications are started and the current one exits, the
"desktop" is displayed instead of getting back to the last open
application as one would expect. This commit activates the last app when
the current one exits.
Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>

In some cases, the app-id actually used by an application might differ
from the one we infer from the corresponding .desktop file. In such
cases (for example, Flatpak demo apps such as Rhythmbox or Totem), we
need to update the app-id we store with the value actually advertised by
the application.

This requires keeping track of starting apps in a separate list, so we
can compare those with advertised app-ids when an application starts for
the first time. The comparison itself is a case-insensitive search of
the advertised app-id in the stored app-id (or the other way around),
which might not cover all possible use-cases, but should be sufficient
for our needs.
Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>

In order to have a central authority tracking application states, apps
from the favorites bar should be started using the launcher as well.

This commit propagates the app info so maynard can then pass it to the
launcher for application startup and tracking.
Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>

Applications launched from the favorites bar aren't started by the
launcher, therefore their state isn't tracked. For example, after
launching a terminal window from the favorites bar, starting the
terminal from the launcher will result in a new instance of the app
being started.

In order to avoid this situation, all apps should be started from the
same code, and the launcher therefore must provide a public function
for doing so.
Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>

In some cases (mostly when using Flatpak applications), the app_id can
be different from the ID computed from the .desktop file. In such cases,
it can be useful to overload the app-id with a value we obtained from
another source, such as the compositor for example.
Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>

This moves the logic for using `StartupWMClass` as the app_id from the
launcher to shell-app-system where it belongs.
Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>

https://phabricator.apertis.org/T8480

Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>

Before, the executable path was assumed to be the app ID, which isn't
really correct. Unfortunately, there isn't a single "correct" answer,
since different apps may set IDs of their choosing.

As a "sane" default, this code will use StartupWMClass if present,
assuming that the application will set its ID to match, but the desktop
file's basename is used otherwise.

https://phabricator.apertis.org/T8434

Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>

This removes the minor dependency on libgnome-desktop-3, as well as
being a slightly more reliable wall clock: rather than using
g_timeout_add, it uses timerfds, as recommended by systemd (see
org.freedesktop.timedate1(8)). In other words, it can easily notice when
the system clock is changed and update itself accordingly.

Signed-off-by: Vignesh Raman <vignesh.raman@collabora.com>

Signed-off-by: Vignesh Raman <vignesh.raman@collabora.com>

Signed-off-by: Vignesh Raman <vignesh.raman@collabora.com>

Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>

We may want to (or accidentally) boot a system without any input device
attached, which would cause `agl-compositor` to fail. As this isn't a
requirement and hotplugging is fully supported, this patch allows the
compositor to start successfully even in such cases.
Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Since the gnome-menus only provide a default category and blacklist function
which have little value in Apertis drop it to avoid pulling python on target.
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Add default simple menu file to enable icons in maynard launcher.
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Fix a silly mistake when declaring the type use for app_id. This issue
had no consequences on weston-8, but in weston-9 produces an segfault
when that code path was trigger, which is in the case an application
is launched via the launcher.
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Upgrade to libweston-9 as it is bullseye default.
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Remove canterbury support since Apertis will not supports it.
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Release commit for version 0.2022.5
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Use the agl-compositor protocol extension to receive notification about apps
that have been launched or destroyed. In this way the launcher is able
to re launch an app that has been stopped by other means, such as due to
a crash.
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

To allow maynard to launch an app if it hasn't already been launched
or activated it if it has implement a simple app lifecycle.
This lifecyle only support two states, APP_STOPPED and APP_STARTED,
since the once an app has been launched it should keep running.

Additionally, based on this lifecyle either launch or activate an app
when its icon is clicked.
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Release commit to bump to version 0.2022.4
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Desktop entries specifications provides a way to avoid showing applications
in the menu list by using NoDisplay key. Add the required support to avoid
showing those applications that specify this key.
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Release commit for maynard version 0.2022.3
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Currently when maynard activates either launcher or indicators_menu it
deactivates the previous surface. In order to be able to display the
previous displayed surface if it wasn't explicitly deactivated, avoid
deactivating it implicitly.

This allows now to be able to show the launcher menu when displaying
the indicators_menu as a popup.
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

In order to improve the GUI and make it more similar to the original
version configure the indicators_menu as as popup according to the
agl-compositor protocol.

As in the original version the popup will be displayed in the botton
left of the desktop.
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

In order to cleanup the code remove some trace entries.
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Release commit to update changelog for maynard 0.2022.2.
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Include libcanterbury-platform as dependency to be able to retrieve the
list of canterbury apps using the support of gnome-menus.
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Add release commit for maynard version 0.2022.1
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Currently maynard supports gnome-menus which can be used to also
retrieve the list of installed canterbury applications after using
cby_init_environment. This makes the specific calls to canterbury
to be redundant.

In order to make the code cleaner and avoid having duplicates in
list of applications displayed by the launcher remove the specific
calls to canterbury.
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

In order to avoid relying on the agl-compositor behaviour, which maximizes
the surface, explicitly set the indicators_menus window size to use the available
screen. This is the whole screen except for part used by the panel.
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>