Update changelog
Marco Trevisan (Treviño)
2 years ago
| 0 | gnome-shell-extension-appindicator (40-1) UNRELEASED; urgency=medium | |
| 1 | ||
| 2 | [ Marco Trevisan (Treviño) ] | |
| 3 | * New upstream release: | |
| 4 | - statusNotifierWatcher: Emit StatusNotifierHostRegistered (and | |
| 5 | Unregistered) signals. | |
| 6 | Other signals we were missing for long time, the specs includes these | |
| 7 | signals and they should be emitted when the watcher appears/disappears | |
| 8 | So do this, although it seems that Qt apps are still ignoring it. | |
| 9 | - indicatorStatusIcon: add polyfill for versionCheck in GNOME 40 | |
| 10 | - iconCache: Do not dispose the icon when clearing the cache. | |
| 11 | The icon can be a property of the Gio.EmblemedIcon and we should not | |
| 12 | dispose it as its parent doesn't support handling the child removal | |
| 13 | - metadata: Remove 40.beta as supported given we support 40 already. | |
| 14 | - promiseUtils: Promptly remove a source if was already cancelled | |
| 15 | - promiseUtils: Disconnect cancellable when the promise is resolved. | |
| 16 | In CancellablePromise we were connecting to the cancellable in order to | |
| 17 | monitor its cancellation, however we never disconnected from it and this | |
| 18 | was causing gjs to keep a reference on the promise itself, being the | |
| 19 | scope of the cancellable callback, and thus never garbaging collecting | |
| 20 | both the promise and its children (such as GSources). | |
| 21 | So, connect earlier to the signal and once we've resolved the promise, | |
| 22 | disconnect form the cancellable. | |
| 23 | - promiseUtils: Disconnect cancellation signal after resolving or rejecting. | |
| 24 | As per the previous commit we do disconnect from cancellation, but this | |
| 25 | happens too early so the cancellation event isn't ever tracked. | |
| 26 | We need in fact to handle it after that the promise is resolved or | |
| 27 | rejected. | |
| 28 | In the rejected case, we need to be extra careful though, as in case | |
| 29 | the cancellation happens as per cancellation's ::cancelled signal | |
| 30 | callback we need to do this in the next idle cycle or we'll deadlock. | |
| 31 | - prefs: Use es6 class and support Gtk4. GNOME 40 requires it | |
| 32 | - appIndicator: Do not lower opacity on versions after GNOME 40. | |
| 33 | There's no such effect upstream anymore so we don't want to switch that | |
| 34 | - appIndicator: Also toggle desaturate effect on mouse hover | |
| 35 | - settingsManager: Move gsettings initializtion to SettingsManager. | |
| 36 | Quite simple class for now but it avoids us to initialize a new | |
| 37 | gsettings instance for each indicator | |
| 38 | - appIndicator: Track hover status using native StWidget's hover property | |
| 39 | - IndicatorStatusIcon: Bind hover property with child IconActor. | |
| 40 | Whatever happens during hover on the whole indicator (including label) | |
| 41 | should affect also the icon, so we can just bind the hover property | |
| 42 | - appIndicator: Use more consistent names for settings updates | |
| 43 | - appIndicator: Cleanup emission of icon signal on status changes. | |
| 44 | We were handling this already in a common place, so let's move there | |
| 45 | - appIndicator: Get and expose the accessibility name. | |
| 46 | Some indicators (such as the Ayatana appindicator based) may include | |
| 47 | accessible descriptions so read and expose them if any or fallback with | |
| 48 | the indicator title otherwise. | |
| 49 | - appIndicator: Do not reload icons when updating the effects applied to it. | |
| 50 | Those are just effects that are not dependent on the icon content, so | |
| 51 | we can just update the icon without having check the effects all the | |
| 52 | times. | |
| 53 | - trayIconsManager: Move handling of legacy tray icons into a nicer class. | |
| 54 | Also move more into the wrapper AppIndicatorsIndicatorTrayIcon, and use | |
| 55 | Shell.TrayManager's unmanage_screen() in newer versions of the shell | |
| 56 | instead of relying on the ugly (and unreliable) tray unset + garbage | |
| 57 | collector invocation. | |
| 58 | - indicatorStatusIcon: Use the accessible name or WM class for a11y. | |
| 59 | We wrongly passed the indicator unique id as the accessible name to the | |
| 60 | shell for ages, we must instead use something that the screen readers | |
| 61 | may use for that. | |
| 62 | So, on appindicators we can use the exposed accessible name while for | |
| 63 | tray icons we can try use the wm class, even if it could be very generic | |
| 64 | - indicatorStatusIcon: Do not create a menu for tray icons | |
| 65 | - util: Wait for display opened only on X11 setup. | |
| 66 | This is actually only relevant for wayland sessions with Xwayland, as | |
| 67 | it may lead to opening the X11 display with some delay. | |
| 68 | But let's keep it to be a bit more conservative, and unblock the case | |
| 69 | for setups with no-x11 at all. | |
| 70 | - appIndicator: Use custom theme icon based on Shell one as default theme. | |
| 71 | Especially under wayland we should avoid to get the theme from the | |
| 72 | default gtk one as it may be always unset, as it depends on the Gdk | |
| 73 | Screen that is undefined in such scenario. | |
| 74 | So add an helper function to create a new Gtk theme using the shell's | |
| 75 | gtk icon theme and try to use it when no default gtk theme is available. | |
| 76 | We could probably do this in all the cases, but for now let's keep X11 | |
| 77 | environment as it is. | |
| 78 | * debian/gbp.conf: Do not use patch numbers | |
| 79 | * debian/patches: Refresh | |
| 80 | * debian/control: Add full support to gnome-shell 40 | |
| 81 | * debian/control: Update extension description | |
| 82 | * debian/patches: Use meson based build system | |
| 83 | * debian/control: Build depend on jq and meson | |
| 84 | * debian/rules: Do not install compiled schemas | |
| 85 | * debian/control: Add suggestions on extension prefs and libappindicator | |
| 86 | * debian/upstream/metadata: Add upstream references | |
| 87 | * debian/control: Use dh-sequence-gnome. | |
| 88 | In this way we also get for free ubuntu-specific tools such as | |
| 89 | dh-translations without having to do an ubuntu-specific fork | |
| 90 | ||
| 91 | [ Fini Jastrow ] | |
| 92 | * Add icon opacity, size, position and other effects settings. | |
| 93 | The icons can be very colorful. Some people might not like it and older | |
| 94 | icons do not blend too well with newer monochrome ones. | |
| 95 | Add settings to configure multiple values of the icons and in | |
| 96 | particular: | |
| 97 | - Icons position in the panel | |
| 98 | - Icon size | |
| 99 | - Opacity | |
| 100 | - Desaturation | |
| 101 | - Brightness | |
| 102 | - Contrast | |
| 103 | As per this a new preference dialog is provided to configure such values | |
| 104 | * appIndicator: Fix resizing pixmap icons | |
| 105 | Icons created from pixmaps can not be resized (properly). | |
| 106 | When we create a icon from a pixmap we actually crate the icon in the | |
| 107 | native size. For example if the smallest available pixmap is 22 px the | |
| 108 | icon will also be 22 px, regardless of requested icon size. | |
| 109 | This is ok if the pixmap is by chance the requested size. But this is | |
| 110 | not always the case, especiually if the icon size is user selectable. | |
| 111 | So after creating the pixmap image we tell it how big it shall be. | |
| 112 | ||
| 113 | [ jingi_jeong ] | |
| 114 | * feature: Add topicons-plus extension logic. | |
| 115 | To add support to legacy tray, merge topicons-plus extension logic. | |
| 116 | Create topicons.js file and connect with original appindicator code. | |
| 117 | ||
| 118 | -- Marco Trevisan (Treviño) <marco@ubuntu.com> Tue, 15 Jun 2021 01:07:37 +0200 | |
| 119 | ||
| 0 | 120 | gnome-shell-extension-appindicator (35-1) experimental; urgency=medium |
| 1 | 121 | |
| 2 | 122 | [ Marco Trevisan (Treviño) ] |