On terça-feira, 11 de dezembro de 2012 09.41.48, Mark wrote: > Perhaps it's an idea to look at KConfig for Qt inclusion? KConfig (XT) > seems nice and works rather well in KDE applications. All that's > needed then is a QML API to access the KConfig configuration. If i'm > right, KDE already has that through data engines though that probably > doesn't work. Perhaps a global Qt QML function like "Qt.config(...)" > or "Qt.configValue(...)" would need to be introduced.
KConfig is also inadequate because it does not support notification of changes from other ends. KConfig is just a better QSettings, it doesn't solve the problems we needed to solve. > As for QSettings, wasn't it supposed to be deprecated in Qt5? It was, but since we have no replacement yet, it couldn't be deprecated nor removed. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
