Commits on Source (74)
-
Florian Müllner authored
... and official start of the next development cycle.
f527fe37 -
Yosef Or Boczko authored
(cherry picked from commit c477f10b)
db305687 -
Florian Müllner authored
Gitlab started inserting a /-/ in its URLs, account for that. https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/merge_requests/113
7b82c5e1 -
Florian Müllner authored
The buttons currently appear more as an attachment to the label than as distinct controls. Address that by: - applying .button styling - increasing spacing between label and button - aligning buttons at the end https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/issues/223
0426d1d8 -
Florian Müllner authored
We already align the buttons correctly here, but otherwise they can use the same treatment as in the drive-menu. https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/issues/223
bce63d31 -
Florian Müllner authored
The tool has a dedicated command for creating an extension bundle. It knows how to handle translations and GSettings schemas, so we don't have to. https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/merge_requests/114
35427ed4 -
Florian Müllner authored
Each extension zip we create includes the translations of all extensions, which is clearly wasteful. Avoid that by generating per-extension .pot files and filtering out unnecessary translations. https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/merge_requests/114
a6ee142f -
Florian Müllner authored
Similar to how we let CI create flatpaks for application, create and expose extension bundles for easier testing. https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/merge_requests/114
5a4b71ba -
Florian Müllner authored
Otherwise recent versions of eslint want "dangling" commas, which is at least ugly considering that most functions don't allow adding arguments at leisure. https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/merge_requests/116
4722b89c -
Florian Müllner authored
All jobs but one use the same issue, so specify that globally instead of for each job. https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/merge_requests/116
a317d790 -
Florian Müllner authored
The current names are an artifact from when flatpak-ci used review/stop_review jobs. 'review' is a much better name and matches what gnome-shell itself uses. https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/merge_requests/116
2e21f7cf -
Florian Müllner authored
This is currently done as part of `ninja test`, but doing the check in a separate CI job means it can run in parallel with other review jobs and fail before trying to build. https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/merge_requests/116
fc8a46f1 -
Florian Müllner authored
Those checks are just as well handled by the CI, and removing them makes for a nice build system cleanup. https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/merge_requests/116
8fb5476a -
Florian Müllner authored
We already do a meson build/install when exporting extension bundles, and now that the syntax check is handled by the CI instead of `meson test`, the job just duplicates work. https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/merge_requests/116
a3541ff0 -
Florian Müllner authored
While we don't endorse or support 3rd party theming, the extension exists and is actively used. However right now the most convenient way of setting it up is by installing Tweak Tool; give users an alternative by providing a simple settings dialog ourselves. https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/merge_requests/117
739b1e11 -
Florian Müllner authored
The user-themes extension actually never had translatable strings.
b1c1b011 -
Milan Crha authored
It seems that gtk+ resets the active radio whenever a new radio button is added into the group, thus rather restore the current mode after the group is fully populated. https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/merge_requests/119
b00e5316 -
Florian Müllner authored
Inline toolbars are an outdated UI pattern, and both the toolbar widget and the inline styling have been removed from GTK4. Making sure the extension doesn't get in the way of a future GTK4 port is a good excuse for modernizing the UI, so do just that :-) Replace treeview and toolbar with an editable list as outline in the HIG: https://developer.gnome.org/hig/stable/lists.html.en https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/merge_requests/120
90d3c5c5 -
Florian Müllner authored
Session mode stylesheets are installed in gnome-shell's theme directory instead of a subdirectory of the global themes direc- tory. https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/merge_requests/118
5b2bdd13 -
Kristjan SCHMIDT authored
(cherry picked from commit c5246b74)
9e7eff4a -
Dz Chen authoredf4013c7a
-
Danial Behzadi authored9f276547
-
Yuri Chornoivan authored92a23613
-
Anders Jonsson authored564235d4
-
Daniel Mustieles authored0c223de0
-
Florian Müllner authored
A row has to be activated to select a theme, not merely selected. The selection therefore doesn't do anything, so disable it.
ac937b95 -
Florian Müllner authored17b5c040
-
Florian Müllner authored
Update NEWS.
81f999f7 -
Cheng-Chia Tseng authoredff94c5a1
-
Florian Müllner authored
auto-move uses the same outdated UI pattern as workspace-indicator did until commit 90d3c5c5, imposing the same problems for a future GTK4 port. So replace treeview and toolbar with an editable list like we did for the other extension. https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/merge_requests/121
c87cfc82 -
Florian Müllner authored
The current widget uses UI patterns that are reminiscent of GNOME 2. It doesn't take a lot to make it look more modern: Simply giving the radio group a distinct background and border allows us to move the whole UI to the center, making the dialog more balanced and visually pleasing. https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/merge_requests/121
9db7b96f -
Yuri Chornoivan authored7bc9b282
-
Daniel Mustieles authored608a8b16
-
Emin Tufan Çetin authoredc16f9828
-
Danial Behzadi authoreda74862e7
-
Daniel Șerbănescu authored867ace0b
-
Florian Müllner authored
Those properties were deprecated (and made no-ops) last cycle, and have now been removed altogether. https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/merge_requests/122
8c53fd95 -
Florian Müllner authored
Those properties were deprecated (and made no-ops) last cycle, and have now been removed altogether. https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/merge_requests/122
60ad2e37 -
Florian Müllner authored
It has been removed in favor of notify::allocation. https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/merge_requests/122
f96943a4 -
Florian Müllner authored
The method was deprecated for years and has finally been removed. Just set appropriate expand/align properties on the children and add them with the usual add_child() method. https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/merge_requests/122
aeaba3f3 -
Matej Urbančič authoredb5ff8601
-
Florian Müllner authored
Update NEWS.
7f2c39cd -
Jordi Mas authored761fdf10
-
sicklylife authored1391acd7
-
sicklylife authored7beebc11
-
Boyuan Yang authoredad5e70b0
-
Baurzhan Muftakhidinov authored
(cherry picked from commit 9a8b5caca33ee2e4a7811151bd1cbb78ea3d9de6)
920b925b -
Baurzhan Muftakhidinov authoredf449ab31
-
Florian Müllner authored
Since PanelMenu.Button started to inherit from St.Widget, the custom _allocate() function isn't called anymore. Simply changing the function to vfunc_allocate() doesn't work as other changes happened in the meantime, so for now just remove it altogether. https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/merge_requests/124
b6a3503f -
Florian Müllner authored
The window picker saw a significant overhaul. Amazingly the adjustments necessary are relatively small ... https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/merge_requests/124
3742f79d -
Florian Müllner authored
The extension was affected pretty badly by the window picker overhaul; adjust to all(?) the major and minor changes to get it to work again. https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/merge_requests/124
eff625fc -
Florian Müllner authored
Update NEWS.
67d2e2f6 -
Fabio Tomat authoredbc497781
-
Efstathios Iosifidis authored9a2d6d68
-
Florian Müllner authored
Originally the classic session replaced `gnome-shell.desktop` with `gnome-shell-classic.desktop` (to add the --mode=classic parameter) and added `nautilus-classic.desktop` (to force on desktop icons). Neither is the case anymore (and hasn't been for years): Nowadays the only expected difference is the GNOME_SHELL_SESSION_MODE variable and the DesktopNames field, which are both set from the session .desktop file rather than the gnome-session session definition. Any difference in the latter - like not starting the USBProtection plugin and missing systemd user session support - are bugs. The easiest way to avoid those in the future is by removing the obsolete duplication that enables them, so do just that. https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/merge_requests/126
9a78c7e4 -
Anders Jonsson authoredfcbdeba8
-
Asier Sarasua Garmendia authoreda41cd3c1
-
Alexandre Franke authored3859c093
-
Florian Müllner authored80030687
-
Florian Müllner authored
Update NEWS.
e39c3b45 -
Fran Dieguez authored1537ac39
-
Akarshan Biswas authored02290e8b
-
Kukuh Syafaat authoredebfbc397
-
Piotr Drąg authoredf6ada58f
-
Rafael authored1d2fdf5c
-
Jiri Grönroos authoredbf8a31a6
-
Марко Костић authored17d07239
-
gogo authored61a54add
-
gogo authored59bcc0a6
-
Florian Müllner authoredbf1f1298
-
Florian Müllner authored
Update NEWS.
75919911 -
Marco Trevisan authored8b9be8f1