With all the focus on App Stores, and the sand boxing that goes along with
them, it would be a poor choice to allow developers to specify their own
storage paths. The OS should provide you with a storage location and your
framework should give you access to it, just as QML SQL does today. This way,
your app won't ever fail the approval process for using funky storage
locations.
If you want nested/group/hierarchical, that's up to you.
What I thought I was seeing, and what I liked, was an automatic binding to
persistent storage. The idea that I can give an object a persistent location
and updates to it will be saved and retrieved automatically.
The windows registry should no longer be used SQLite has won that war. The
registry should onl y be used to indicate the presence of your program and to
set up any system associations that your program needs to provide. One funky
thing about the registry is that it can be locked down, and things you think
you have access to, you might not because they are readable but
administrator-only wriatable. You'll save yourself a lot of headaches by using
your own database.
________________________________
From: Shawn Rutledge <shawn.t.rutle...@gmail.com>
To: João Abecasis <joao.abeca...@nokia.com>
Cc: qt-qml@qt.nokia.com
Sent: Friday, November 18, 2011 8:00 AM
Subject: Re: [Qt-qml] Settings / State Saving proposal for QML
2011/11/18 João Abecasis <joao.abeca...@nokia.com>:
> The reason for trying to keep some distance from QSettings is exactly that it
> has flaws and issues. I don't want to be *forced* to use it or re-implement
> it. Ideally, the backend will be handled by a platform-specific plugin that
> is *not* QSettings or based on it.
QSettings could be extended to support json too though.
>
> (Also note that there is a wish to remove QSettings from Qt Core in Qt 5,
> pending availability of something to replace it with.)
Why? We wouldn't lose the ability to read and write the same data
stores that QSettings does? I think the registry is not considered
obsolete yet on Windows, as ugly as it is?
_______________________________________________
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
