On Monday, 2013-07-29, [email protected] wrote: > So how to do it? We would still want to access settings in the code through > QSettings, and presumably, when dconf makes it's way into Qt, it will be in > the form of a new back-end for QSettings.
Very unlikely. QSettings is one of the classes everybody would like to be replaced with something better but for which nobody had time yet. > I've had a (very) cursory look at the dconf-api, and I think this is > possible. Indeed. As far as I understand is uses a mixture of mmap#ing and D-Bus, both of which are fully supported by Qt by QFile and QtDBus respectively. Might even be viable as a stop-gap measure to wrap the GObject client library until a real Qt implementation can be made for upstreaming into whatever will replace QSettings. The dependency and type conversion overheads should be fairly acceptable even for something that is used in application startup code. Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________ Lxde-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lxde-list
