I like the idea, however I would probably have used XPath or
http://docs.persvr.org/documentation/jsonquery
I also don't understand why the QML db API is enough?
and done something like:
Rect {
width: xpathquery(storage, "/" + id + "/width");
}
Storage {
id:storage
source: "sample.db"
}
I'd throw a curve out there to you and say with source, you can do
"http://some.site.com/";, and supply account credentials.
Implement a lightweight HTTP server and have persistent remote settings storage
:-)
________________________________
From: João Abecasis <joao.abeca...@nokia.com>
To: qt-qml@qt.nokia.com
Sent: Thursday, November 17, 2011 10:34 AM
Subject: [Qt-qml] Settings / State Saving proposal for QML
Ahem,
I have a very basic working prototype for a generic Settings API for QML that I
would like to bring up for discussion.
The API is pretty minimal, here's example usage:
Rectangle {
id: main
height: 480
width: 640
color: settings.color
Settings {
id: settings
property string color: "blue"
property alias height: main.height
property alias width: main.width
}
}
I pushed the code to a clone of the Desktop Components repository over on
gitorious. There's some further information in the commit message:
https://qt.gitorious.org/~biochimia/qt-components/biochimias-desktop/commit/c1ac32929065f24783f4d254d1786dce8202b274
While this needs further refinement and exploration (e.g., ignore the fact that
it is using QSettings underneath ;-), what do people around here think of this
approach?
Cheers,
João
_______________________________________________
Qt-qml mailing list
Qt-qml@qt.nokia.com
http://lists.qt.nokia.com/mailman/listinfo/qt-qml_______________________________________________
Qt-qml mailing list
Qt-qml@qt.nokia.com
http://lists.qt.nokia.com/mailman/listinfo/qt-qml
