Hi, Andre Klapper wrote: > Users (=apps) would rather convert to using GSettings in Glib/gio.
Most users (=apps) would probably like to continue using the same API, and only have the backing store change. Then there's the second type of users (=people) who want to transparently have the same preferences applied when they upgrade an application. > dconf is one backend for GSettings, another one is gconf (by > http://git.gnome.org/browse/gconf/tree/gsettings/ ), or could e.g. be > the Windows registry (if somebody wrote the code for that). So the GSettings API does not match GConf, and application developers need to change both the settings schemas and the way they call the settings API. Is that right? What happens when I run an application which has been migrated from gconf to GSettings? > A script called "gsettings-data-convert" exists to migrate user settings > from GConf to another GSettings backend, e.g. dconf. So this reads old gconf keys and updates new registry entries with them? How foolproof is it? How does an application writer integrate it into the first run of the upgraded application? Cheers, Dave. -- Email: dne...@maemo.org Jabber: bo...@jabber.org _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
