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). On 27 December 2013 23:10, Daniel Narvaez <dwnarv...@gmail.com> wrote: > For both activity-specific and plugins-specific settings we could probably > do something like this > > > http://askubuntu.com/questions/251712/how-can-i-install-a-gsettings-schema-without-root-privileges > > We could add an helper to toolkit to setup the schema. Hopefully it would > be possible to also integrate this with the gsettings override mechanism > which would allow deployments to provide different defaults. > > This is more complex that just using ConfigParser or json of course. > > I don't have a strong feeling about what direction we should take. I > wouldn't rush this though, because it's adding new API that we will have to > support. As far as I know we can keep using GConf for this kiind of > settings until we have a good alternative. > > > > On 27 December 2013 22:39, Walter Bender <walter.ben...@gmail.com> wrote: > >> On Fri, Dec 27, 2013 at 5:22 PM, Daniel Narvaez <dwnarv...@gmail.com> >> wrote: >> > On 27 December 2013 22:16, Emil Dudev <emildu...@gmail.com> wrote: >> >> >> >> Here are the keys that activites still use from GConf: >> >> org.sugarlabs.speech pitch, rate >> >> org.sugarlabs.user nick, color >> >> org.sugarlabs backup-url >> >> org.sugarlabs.collaboration jabber-server >> >> org.sugarlabs.power automatic >> >> org.sugarlabs.font default-face, default-size >> >> The activities are numerous, so I didn't include them here, just the >> >> values they user. >> >> >> >> Activities that set keys in GConf: >> >> AboutMe: /desktop/sugar/user/nick, /desktop/sugar/user/color >> >> xoEditor: /desktop/sugar/user/color >> > >> > >> > These should be changed to use gsettings I think, I don't think there >> is a >> > way to keep compatibility. >> > >> >> >> >> TurtleArtMini, TortugadeMexico, GoGo, AmazonasTortuga, TurtleFlags, >> >> TurtleConfusion, TurtleBots, TurtleBlocks: >> /desktop/sugar/power/automatic >> > >> > >> > Maybe someone here can explain what is this about? More out of >> curiosity but >> > are they all forks? >> >> They are all forks: different variants of Turtle. I can work around >> gconf for Turtle easily enough, but as I mentioned earlier, not sure >> what to do the webservices. They use gconf to store server-specific >> data. >> >> -walter >> > >> > _______________________________________________ >> > Sugar-devel mailing list >> > Sugar-devel@lists.sugarlabs.org >> > http://lists.sugarlabs.org/listinfo/sugar-devel >> > >> >> >> >> -- >> Walter Bender >> Sugar Labs >> http://www.sugarlabs.org >> > > > > -- > Daniel Narvaez > -- Daniel Narvaez
_______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel