Skip to content
This repository

Add to extensions.gnome.org #50

Open
Mystro256 opened this Issue · 6 comments

4 participants

Jeremy Newton Simon Legner grossetti Frank Dana
Jeremy Newton

If this hasn't been already, it should be added to extensions.gnome.org

Simon Legner
Owner

As of Gnome 3.2, extensions with custom GSettings cannot be installed as user and thus not from extensions.gnome.org. See http://mail.gnome.org/archives/desktop-devel-list/2011-December/msg00010.html

To fix this, we would need to switch to a different configuration storage, e.g., JSON.

Jeremy Newton

Oh well in gnome 3.4 this will be available; so I guess holding tight until March should be fine, unless this is heavily desired sooner or for gnome 3.2.

grossetti

Can you add it now please? 3.4 supports this (my RemovePanelAppMenu extension has custom GSettings). Thanks!

Frank Dana

What remains to be done in order to make this happen, I would think, is the migration away from the standalone configurator, and integration with the standard GSettings customization method.

Gnome Shell 3.4 apparently has some sort of centralized extension-preferences tool. I say "apparently" because I still haven't figured out how it's meant to be accessed directly (or if it is) — perhaps I'm blind, but the only way I stumbled across the thing was by installing the latest System Monitor Applet Extension and then selecting its "Preferences..." menu option.

Doing that brought up a "centralized" GNOME Shell Extension Preferences tool that allowed me to configure the System Monitor Applet displays, replacing the extension's previously-standalone config tool. (The tool seems rather bare-bones and tossed-together, especially the selector which lists all of the enabled extensions, even if they don't have configs. Perhaps in the future as its adoption grows that'll be OK, but for now... well, see this screenshot for why it's less-than-ideal. Yep, all of the grayed-out entries have no preferences accessible by the tool.)

So, I assume the current weather-extension-configurator.py would become a pane in this tool. There'd also have to be a slightly new/different disposition for the GSettings schema.

Once those things are in compliance with the New Way™, the extension should then be extensions.gnome.org-worthy.

Thing is, I'll be darned if I've seen any resources on making that happen. @grossetti , since I assume you've already dealt with this for your RemovePanelAppMenu, do you have any pointers to documentation or guidance on the Extension Preferences tool, and extensions' migration to using it?

grossetti

Hi @ferdnyc,

I was referring to your post with "As of Gnome 3.2, extensions with custom GSettings cannot be installed as user and thus not from extensions.gnome.org.", my code has custom GSettings, but they are set in the code itself and not "user options". I think I may have misunderstood your post. My custom GSettings override settings not directly exposed in GSettings. They added an override key that uses a dict. to override these "hidden" settings, I thought that was what you needed.

By "Centralized GNOME Shell Extension Preferences tool" I assume you are referring to this: http://blog.mecheye.net/2012/02/more-extension-api-breaks/. The Gnome Shell System Monitor applet uses it, maybe have a look at it: https://github.com/paradoxxxzero/gnome-shell-system-monitor-applet (not sure this is the same as the one you were referring to, the like gave me an error).

You can run it manually (useful for testing) using the "gnome-shell-extension-prefs extension:///uuid@example.com" command like so:

gnome-shell-extension-prefs extension:///system-monitor@paradoxxx.zero.gmail.com

(for the Gnome Shell System Monitor applet). The Media player applet also uses the centralized prefs tool: https://github.com/eonpatapon/gnome-shell-extensions-mediaplayer maybe try looking at it too.

Frank Dana

By "Centralized GNOME Shell Extension Preferences tool" I assume you are referring to this: http://blog.mecheye.net/2012/02/more-extension-api-breaks/.

Ah! Thank you, that post does indeed appear to be the "missing link" in my understanding of the preferences migration. Immensely helpful. I'll have to give it a peruse tonight, and maybe diff the system-monitor-applet code between 3.2 and 3.4 (or ping paradoxxxzero) to find out how the migration was done on that code.

The Gnome Shell System Monitor applet uses it, maybe have a look at it: https://github.com/paradoxxxzero/gnome-shell-system-monitor-applet (not sure this is the same as the one you were referring to, the like gave me an error).

Heh. Yeah, it is. My link was to its extensions.gnome.org entry. The reason you got an error, it seems, is that all of extensions.gnome.org appears to be returning 500 errors at the moment! So... that's reassuring. ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.