[Sugar-devel] From GConf to GSettings

Daniel Narvaez dwnarvaez at gmail.com
Mon Dec 30 04:50:37 EST 2013


Adding the list. By the way we should discuss this with Sai too, he is
working on a patch which is similar and might even conflict.

I'm travelling and just on an iPhone so it's hard for me to properly look
at the code and suggest something. I can do so when I get back home,
probably in a few days.

Something I'm wondering is if we should turn all the favorites stuff into a
dictionary. If I remember correctly, the current code is basically trying
to make a dictionary using dynamic key names? And Sai is adding another
property using that approach.

If the dictionary idea make sense, we can then discuss how to avoid
conflicts.

On Sunday, 29 December 2013, Emil Dudev wrote:

> Hello,
>
> It's hard to find you on IRC.
>
> I've managed to port the rest of sugar to use GSettings. I doubt you'll
> like my solution, but I couldn't find a better one.
> Commit:
> https://github.com/edudev/sugar/commit/7b6f5af3783bd48c6891e712268dffb284dadbd7
> When I checked my settings in GConf, I found that for these keys they are
> at their default values. I think that so is with the rest of sugar's
> community, so I don't think that a special data conversion is needed.
>
> I think it's safe to remove the parts of gconf in sugar-toolkit-gtk3. I
> couldn't find any code that still uses it.
>
> Emil Dudev
>
> On Sat, Dec 28, 2013 at 1:42 AM, Daniel Narvaez <dwnarvaez at gmail.com<javascript:_e({}, 'cvml', 'dwnarvaez at gmail.com');>
> > wrote:
>
>> To summarize what is left here:
>>
>> * Port activities to use sugar3.profile and gsettings. Maybe we just need
>> to document this and let activity authors deal with it.
>> * Make sure we deal with schemas translations correctly. It might just
>> work with Fedora 20, or it might need little tweak.
>> * Remove the remaining bits of GConf usage in the sugar shell. They was
>> not easy to get rid of because they use dynamic keys. Just a couple of
>> places but migration will not be trivial. When that's done we can also drop
>> the gconf schemas.
>> * Remove the remaining bits of GConf in sugar-toolkit-gtk3.
>> * Write a feature page for future documentation. I think Emil has it done
>> as an md file, he was trying to get access to the wiki.
>> * Figure out what to do with activity-specific and plugins-specific
>> settings.
>>
>> (Not sure which of these are part of the current GCI task really, I'll
>> let Walter deal with that :P).
>>
>> --
>> Daniel Narvaez
>>
>
>

-- 
Daniel Narvaez
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20131230/386a27a9/attachment.html>


More information about the Sugar-devel mailing list