← Back to team overview

indicator-sound-developers team mailing list archive

Re: Changes to the sound menu registration process for Natty

 

Hello Conor
Ok. I just forgot that GSettings is now part of GLib.




> Hi Jorn,
> 
> >>Then apps would not have to add another dependency.
> 
> Considering GSettings is now part of GLib what extra dependency are you 
> thinking of ?
> 
> >>How about using a dbus call or property to opt-out the appearing in the
> >>Sound Menu?
> 
> I believe this GSettings method to be the cleanest, using a DBus call 
> involves the sound menu exposing the appropriate dbus method/property, 
> the client pinging this dbus method/property and then for me in the 
> background to write straight back to the GSettings entry. If clients 
> would just write straight to this gsettings entry in the first place it 
> reduces traffic on the bus and an unnecessary circuitous route to do the 
> same thing. Considering each client will need some sort of sound menu 
> plugin extension to contain the distribution specific code doing a DBus 
> call or fetching the appropriate GSettings and modifying it accordingly 
> is much of a muchness.
> 
> Conor
> 
> 
> 
> 
> On 14/12/10 21:14, shuerhaaken wrote:
> > How about using a dbus call or property to opt-out the appearing in the
> > Sound Menu? Then apps would not have to add another dependency.
> > Jörn
> >
> >
> >> Apologies for this folks, but after talking with the packagers it seems
> >> this approach is not the wisest. By writing to a file in the xdg data
> >> dir any required update to the system version will be ignored if favour
> >> of the xdg data dir version. Not ideal obviously. Understandably
> >> packagers don't like this sort of thing :)
> >>
> >> So after talking with the Unity guys it looks like g-settings is the way
> >> we should go.
> >> I am currently working on the indicator sound gsettings schema. This
> >> again will mean less work for client developers. Less work than what I
> >> proposed last week.
> >>
> >> I propose to have a key called something like 'blacklist-entries' which
> >> if I client (or more the user of a client) wishes to opt out of the
> >> sound menu then the application will need to add the name of the desktop
> >> file to this array. It should be of type ("as").
> >>
> >> That way client developers will not need to do anything other that
> >> adhere to the mpris2 spec order to get their application working with
> >> the menu. The UI for allowing the users to opt in and out should edit
> >> this entry removing (opt in - by default on) or adding (opt out) their
> >> desktop file name.
> >>
> >> Sorry for the uturn.
> >> I just want to get this right this time for your sake and mine.
> >>
> >> Thoughts?
> >>
> >> Conor
> >>
> >> On 08/12/10 12:00, Conor Curran wrote:
> >>> Hi Jorn,
> >>>
> >>> After thinking this over I would think it would be a good idea to use
> >>>
> >>> X-Canonical-Indicator-Sound-Integrate
> >>>
> >>> as the entry in the Desktop file. Being more precise allows us for
> >>> potential room for manoeuvre in the future if needed.
> >>>
> >>> Conor
> >>>
> >>>
> >>> On 08/12/10 11:33, shuerhaaken wrote:
> >>>> Ok, thanks for explaining!
> >>>> That's a comfortable way of doing this.
> >>>> Is the "X-Canonical-Indicator-Sound" thing targeted for Natty?
> >>>> Regards
> >>>> Jörn
> >>>>
> >>>>> -----BEGIN PGP SIGNED MESSAGE-----
> >>>>> Hash: SHA1
> >>>>>
> >>>>> On 12/08/2010 05:25 AM, shuerhaaken wrote:
> >>>>>> Ok.
> >>>>>> I guess the (per-user)desktop files in $XDG_DATA_HOME/applications
> >>>>>> will
> >>>>>> then be used before the ones in /usr/share/applications/ and these
> >>>>>> have
> >>>>>> to be full copies of the original desktop files
> >>>>>> in /usr/share/applications/ + some extra entries ?
> >>>>>> Sorry for this lazy question.
> >>>>>> Regards and thanks
> >>>>>> Jörn
> >>>>>>
> >>>>>>
> >>>>> Yeah, this is how it works when you edit a launcher from alacarte too.
> >>>>> GLib has helpers for this. Basically just load a GKeyFile of type
> >>>>> G_KEY_FILE_DESKTOP_TYPE_APPLICATION, modify the keys, and then write it
> >>>>> back out in the data dir.
> >>>>>
> >>>>>
> >>>>> - -- Alex Launi
> >>>>> Canonical Desktop Experience Team
> >>>>> -----BEGIN PGP SIGNATURE-----
> >>>>> Version: GnuPG v1.4.10 (GNU/Linux)
> >>>>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> >>>>>
> >>>>> iEYEARECAAYFAkz/ZkIACgkQpL94dTyos27LFACfWNq95nXxZOPsXzi2NcwBp8kT
> >>>>> BckAni2sIOet2YdymxkOv8c8+3oN+lvx
> >>>>> =ap9d
> >>>>> -----END PGP SIGNATURE-----
> >>>>
> >>>> _______________________________________________
> >>>> Mailing list: https://launchpad.net/~indicator-sound-developers
> >>>> Post to     : indicator-sound-developers@xxxxxxxxxxxxxxxxxxx
> >>>> Unsubscribe : https://launchpad.net/~indicator-sound-developers
> >>>> More help   : https://help.launchpad.net/ListHelp
> >>> _______________________________________________
> >>> Mailing list: https://launchpad.net/~indicator-sound-developers
> >>> Post to     : indicator-sound-developers@xxxxxxxxxxxxxxxxxxx
> >>> Unsubscribe : https://launchpad.net/~indicator-sound-developers
> >>> More help   : https://help.launchpad.net/ListHelp
> >> _______________________________________________
> >> Mailing list: https://launchpad.net/~indicator-sound-developers
> >> Post to     : indicator-sound-developers@xxxxxxxxxxxxxxxxxxx
> >> Unsubscribe : https://launchpad.net/~indicator-sound-developers
> >> More help   : https://help.launchpad.net/ListHelp
> >





References