gnome-shell/js
Florian Müllner e6624f8ba1 extensionSytem: Rename ENABLED/DISABLED states
The ENABLED state means that an extension's `enable()` method
was called successfully.

This usually matches whether an extension *should* be enabled
according to the enabled-extensions/disabled-extensions settings,
but not necessarily: If an extension had an error or does not
support the currently active mode, its actual state is different.

We currently only expose the actual state to external tooling,
but whether an extension should be enabled is relevant as well,
for example to disable a lock-screen only extension from the
regular session.

For that purpose we will expose a separate `enabled` property.
To avoid confusion with the existing states, change the exposed
names to (IN)ACTIVE.

This does not affect the D-Bus API, as the numeric values of
the states remain unchanged.

https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7004

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3073>
2024-01-03 20:05:05 +00:00
..
dbusServices dbusService: Exempt org.gnome.Shell from sender tracking 2023-12-13 01:27:51 +01:00
extensions extensions: Fix ngettext convenience 2023-09-15 21:41:30 +00:00
gdm js: Explicitly set expand of St.Bin children 2023-12-15 14:45:37 +00:00
misc extensionSytem: Rename ENABLED/DISABLED states 2024-01-03 20:05:05 +00:00
portalHelper js: Port Config to ESM 2023-08-10 17:42:23 +00:00
ui extensionSytem: Rename ENABLED/DISABLED states 2024-01-03 20:05:05 +00:00
js-resources.gresource.xml components: Change component loading to be asynchronous 2023-08-05 22:16:23 +02:00
meson.build extensions-app: Move Extensions app to new subproject 2020-03-27 23:33:30 +00:00
portal-resources.gresource.xml js/portal-resources: Add missing fileUtils to js path 2022-11-03 18:02:27 +00:00