ext Thiago Macieira wrote:
Em terça-feira, 25 de janeiro de 2011, às 15:27:02, Urho Konttori escreveu:
Don't we have mobility publish and subscribe (or qvaluespace) for the
exact purpose outlined here as the change notification?
P&S is very good at providing dynamic value changes across the entire system.
But as it is not connected to the system settings, it's a separate namespace.
There's no guarantee that a system setting found under a certain key can be
observed in P&S.
Also, and here I'm unfamiliar with P&S, can any application change the value
found in the P&S value space? What happens when this app quits?
There are different backends to P&S. Shared memory is the most volatile
and the one people often mistake to be the only backend.
Take a peek at:
http://doc.qt.nokia.com/qtmobility-1.2/publ-subs.html
Gconf is even now available as one of the layers (and so is windows
registry and symbian settings).
Beauty of P&S is that you only need to care about the backend if you
want to. You can just select one that provides the features you actually
want (e.g. I want to store this tuple to a layer that provides permanent
storage), or request for scan of all different backends for the key you
need.
Layer can be also read only, which then means that an app cannot change
the value.
Thus, shouldn't you use that if you need notifications and QSettings for
the cases you don't. Seems pretty logical to me.
Having said that, I do vote for Marius Vollmers proposal that there
should be a dconf backend to the qvaluespace in the future.
------------------------------------------------------------------------
_______________________________________________
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
_______________________________________________
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
