GNOME Bugzilla – Bug 625902
Port to GSettings
Last modified: 2011-09-04 18:19:54 UTC
http://live.gnome.org/GnomeGoals/GSettingsMigration
Created attachment 187765 [details] Proposed gsettings schema I have ported actual gconf schema to gsettings. I don't really know if it's needed to add some keys, so, some review will be appreciated! Regards!
I've realized that there are some modules storing its own preferences without a schema, so this schema still needs more keys. Those are general preferences keys, and hotkeys preferences.
Related, but possibly another bug: Accerciser (in a gsettings environment) should check to see if org.gnome.desktop.interface toolkit-accessibility is set to true. If not, it should do... something. :-) Tell the user, offer to set it, whatever. This might should be in the docs too. Otherwise there is confusion as to what magic is required to make apps show up as accessible -- magic that used to be much more obvious in GNOME 2 than it is now.
Guess this bug can be closed, given that Accerciser's newest version uses Gsettings.
I don't think so. Accerciser is still using gconf for its own settings. The latest release just answers Joanie's comment (which yes, should have been a separate bug :)
Good to know, Eitan. Thanks
At this moment, accerciser is using gsettings ONLY for check the toolkit-accessibility key [1], as a temporary solution. The whole migration to gsettings will take place once the pygtk migration is complete. This is to store preferences using gsettings and by removing gconf as a dependency. Anyway, I have some of this work done, FYI. Regards! [1]: http://git.gnome.org/browse/accerciser/commit/?id=4f1d67e87cb855bb6731d91da1e1b7cd1fb52ca6
Created attachment 195546 [details] [review] port to gsettings patch Here's the gconf-to-gsettings migration work.
commited: 85fc11dc5503dfd826f27b55f680d8c1b16ca469