Re: using gsettings / gconf in extensions

[Milan Bouchet-Valat <nalimilan club fr>]

Le mercredi 25 mai 2011 à 15:55 +0200, Giovanni Campagna a écrit :
> Currently, extensions that use GSettings use
> "org.gnome.shell.extensions.<extension-id>" and
> "/org/gnome/shell/extensions/<extension-id>", yes. I think you can
> follow that prefix, if you plan to have it hosted by
> gnome-shell-extensions GIT.
> Otherwise, it is better to use your own ID (like
> org.project.YourExtension and /org/project/YourExtension), to avoid
> clobbering namespaces you don't own.
Isn't it better to put weird stuff under
org.gnome.shell.extensions.<extension-id> even when it's not shipped in
git? By using custom org.YourExtension paths, you create noise in the
dconf database root, and it doesn't help to find them if you want to
change settings. So I'd say use
org.gnome.shell.extensions.YourExtension, but use a reasonably unique
name so that it doesn't conflict with others.

> Giovanni
> 
> PS: note that extensions with GSettings must be installed system-wide,
> so you'd better have them in gnome-shell-extensions repo, so they're
> picked up by distribution packages.
Yeah, happily this makes the above issue much less of a problem... ;-)


Cheers