Den 29/07/2013 13.28 skrev "Kevin Krammer" <email@example.com>:
> On Monday, 2013-07-29, firstname.lastname@example.org 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.
Are you sure? To me it seemed people disliked the ini- files. Not so much QSettings.
Anyway I believe QSettings will stay for the duration of qt5 - at least.
> > 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.
> Kevin Krammer, KDE developer, xdg-utils developer
> KDE user support, developer mentoring
You received this message because you are subscribed to the Google
Groups "Razor-qt" group.
For more options, visit this group at
You received this message because you are subscribed to the Google Groups "Razor-qt" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
For more options, visit https://groups.google.com/groups/opt_out.