Re: Fix gsettings path to use /org/gnome instead /apps
- From: Milan Bouchet-Valat <nalimilan club fr>
- To: Luca Ferretti <lferrett gnome org>
- Cc: desktop-devel-list <desktop-devel-list gnome org>
- Subject: Re: Fix gsettings path to use /org/gnome instead /apps
- Date: Fri, 25 Mar 2011 10:41:57 +0100
On jeu., 2011-03-24 at 23:41 +0100, Luca Ferretti wrote:
> Flash news from release team to our all brave developers.
>
> A member of release team known as *cough*Luca Ferretti*cough* was sure
> gsettings PATHs and gsettings IDs were the same, so he was also sure all
> GNOME 3 core apps were using the proper path. So he never sent any
> notice or filed bug report...
>
> But we don't want to blame his errors, we want to have a fine tuned
> GNOME 3 Desktop. A quick grep[1] shows about 15 basic modules using the
> wrong PATH. Patches are available here[2][3].
Looking at the patches, I see people chose different conventions for id
and path. For example, the Shell uses the id org.gnome.shell, and
gnome-system-monitor uses org.gnome.gnome-system-monitor. This in turns
can lead to different paths: your patches use /org/gnome/gnome-shell
and /org/gnome/gnome-system-monitor. But this isn't consistent with the
id for the Shell (same problem with gnome-power-manager).
Can we choose one of these conventions? Then, I think id and path should
have the same form when there's no reason to make it different.
(Personally, I think /org/gnome/shell is better
than /org/gnome/gnome-shell because gnome- is redundant.)
Regards
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]