Re: [Ekiga-devel-list] GSettings in ekiga
- From: Peter Robinson <pbrobinson gmail com>
- To: Ekiga development mailing list <ekiga-devel-list gnome org>
- Subject: Re: [Ekiga-devel-list] GSettings in ekiga
- Date: Thu, 10 Jun 2010 19:04:45 +0100
On Thu, Jun 10, 2010 at 6:45 PM, Peter Robinson <pbrobinson gmail com> wrote:
> On Thu, Jun 10, 2010 at 5:24 PM, Eugen Dedu
> <Eugen Dedu pu-pm univ-fcomte fr> wrote:
>> On 10/06/10 18:12, Peter Robinson wrote:
>>>
>>> On Thu, Jun 10, 2010 at 3:01 PM, Julien Puydt<jpuydt free fr> wrote:
>>>>
>>>> Hi,
>>>>
>>>> here is what I have done :
>>>> - look the api and try to get a grip on it ;
>>>> - update the gmconf api in various ways :
>>>> * remove unused code ;
>>>> * remove useless code ;
>>>> * tweak the api a little (a small leak nest just got away) ;
>>>> - write some GSettings code.
>>>>
>>>> Most of it is in master already -- only the last part isn't yet.
>>>>
>>>> What the code I wrote lacks :
>>>> - initialization code ;
>>>> - actually triggering the callbacks when configuration gets changed ;
>>>> - check for valid sanity (I never compiled it -- it's just correct in my
>>>> head) ;
>>>> - appear in Makefile.am (see previous point) ;
>>>> - an option in configure for gmconf-as-gsettings ;
>>>> - a schema (should be done by converting the gconf schema) ;
>>>> - a migration path for our users (I have no clear idea how to do that
>>>> yet).
>>>>
>>>> I plan to move the gconf schema to lib/gmconf/ (and move everything
>>>> related
>>>> to it there), since that makes more sense -- will it be a problem for
>>>> packagers?
>>>>
>>>> What annoys me deeply for now -- and the main reason I didn't bother to
>>>> make
>>>> my code compiled yet, is that I don't have the right glib on my system.
>>>> Yes,
>>>> debian *unstable* doesn't have glib>= 2.26 yet. Of course, I could get
>>>> out
>>>> of my way and probably find experimental packages somewhere. But why does
>>>> gnome want to move to GSettings if it isn't even in the *bleeding edge*
>>>> distributions yet!? Won't it give us headaches with our users? For
>>>> instance,
>>>> http://www.gtk.org/download-windows.html says that we don't have 2.26
>>>> available on win32 either...
>>>
>>> It is in Fedora rawhide. Clearly Debian experimental isn't that
>>> bleeding edge :-P
>>>
>>> But the dconf side of it is still relatively new, its all only been in
>>> Fedora for less than a month.
>>
>> Where it is written that GSettings are mandatory for gnome 3.0? We could
>> ask André Klapper for that. Moreover, glib 2.26 does not yet exist (2.25 is
>> the current). I suppose there is a misunderstanding here.
>
> The 2.25 release is the devel release headed to 2.26. The gnome-3
> cycle is outlined on the wiki [1] and Aug 16th it states 0 modules
> depending on GConf.
>
> http://live.gnome.org/TwoPointThirtyone
There's also some details on the migration here
http://live.gnome.org/GnomeGoals/GSettingsMigration
Apparently according to Andre [1] there's also a need to use GSeal for
gtk3 as well. Details here
http://live.gnome.org/GnomeGoals/UseGseal
Peter
[1] http://blogs.gnome.org/aklapper/2010/06/10/heads-up-gnome-2-31-soon-to-ship-gtk-2-90/
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]