GNOME Bugzilla – Bug 734432
[ui-review] GNOME Shell extensions are not shown
Last modified: 2016-03-02 11:38:20 UTC
There is no method to manage installed shell extensions in gnome-software. There should be a way to find available extensions and install them directly from gnome-software.
Allan, any ideas? Seems pretty logical given we're installing other kinds of "addons" in various different ways...
This might help us: https://github.com/ianbrunelli/gnome-shell-extension-installer
The problem here is how/where you would configure extensions that have been installed. A lot of extensions have preferences, and it would be a bit odd if Software turned into some kind of secondary control center.
Yes, please offer a module in control center dealing with extensions. I am sure that extensions can be queried/inspected on all types of settings and setting locations they use. Actually, at the moment the reverse is true. It is odd that extensions are not to be managed from the control center. Many of the same sort of settings are now managed from two places, i.e. control center and https://extensions.gnome.org/local For many users this is too confusing.
Alternatively, offer an icon in control center that opens up https://extensions.gnome.org/local in a web browser so all users can find it easily.
I'm planning on working on this next cycle.
This is the new UI I'm working towards: https://dl.dropboxusercontent.com/u/5031519/software/software-shell-extensions-wires.png It does however have quite a lot of duplication; for instance you can get to the extension settings two very different ways, and you can disable the extension in the popover, but not when looking at the extension details. You can remove the extension in two places, and you can also enable or disable all the plugins in two different ways. We also currently have two different warnings in different styles in the popover and the details panel. I'm struggling to work out what the purpose of the popover is, when you could trivially include a enable/disable GtkSwitch in the details panel. By putting the "enable/disable everything" switch where the extension settings button goes you could completely eliminate the popover and a ton of overhead and complexity -- plus then the extensions match the expectations of all the other things in GNOME Software. I'm unclear what clicking the line in the popover would do; logically it would take you to the details page for the extension but this is in a modal dialog and so it would have to be auto-closed.
(In reply to Richard Hughes from comment #7) > This is the new UI I'm working towards: > https://dl.dropboxusercontent.com/u/5031519/software/software-shell- > extensions-wires.png > > It does however have quite a lot of duplication; for instance you can get to > the extension settings two very different ways You can get to extension settings from the extensions category page and from the extension details page. Why is that a problem? Should we not show the settings in one of those places? >, and you can disable the > extension in the popover, but not when looking at the extension details. Yep, that's intentional. > You > can remove the extension in two places, Yes, from the settings window and from the details page. > and you can also enable or disable > all the plugins in two different ways. I only see one - in the settings window. What's the other? > We also currently have two different > warnings in different styles in the popover and the details panel. True. > I'm struggling to work out what the purpose of the popover is, when you > could trivially include a enable/disable GtkSwitch in the details panel. By > putting the "enable/disable everything" switch where the extension settings > button goes you could completely eliminate the popover and a ton of overhead > and complexity -- plus then the extensions match the expectations of all the > other things in GNOME Software. It's not a popover, it's a separate "app" that we already include, called gnome-extension-prefs. This is explained in the mockup notes. The primary motivation behind having a separate settings window was to avoid Software itself from becoming a settings utility. That's not Software's job: it exists to add and remove software, not to configure that software. One alternative would be to put everything related to extensions, including installation and removal, into the Tweak Tool. We could certainly explore that option. > I'm unclear what clicking the line in the > popover would do ... You can try it in gnome-extension-prefs.
commit 03f77ef7b32b7553ecf0cf60cc7cbac65da63571 Author: Richard Hughes <richard@hughsie.com> Date: Tue Mar 1 13:33:11 2016 +0000 Add support for GNOME Shell extensions There are a few more style tweaks required to 100% match the mockup, but it's certainly good enough to test in its current form. Fixes: https://bugzilla.gnome.org/show_bug.cgi?id=734432 note, you also need new appstream-data if your distro is providing packaged shell-extensions too -- and you need an appstream-builder at least new enough to have this commit: commit 72c1168373de06d8e13012292079a0cbbe6ec4fa Author: Richard Hughes <richard@hughsie.com> Date: Tue Mar 1 22:34:35 2016 +0000 Add support for GNOME Shell extensions :100644 100644 60dbcdd... 3352bbc... M configure.ac :100644 100644 cf47ac8... eb2ff9f... M contrib/libappstream-glib.spec.in :100644 100644 b933ed2... 861fa37... M libappstream-builder/plugins/Makefile.am :000000 100644 0000000... 8842b1f... A libappstream-builder/plugins/asb-plugin-shell-extension.c
In comment #8, don't you mean gnome-shell-extension-prefs ?