On 9/26/2010 2:53 AM, Sivan Greenberg wrote:
On Sun, Sep 26, 2010 at 8:38 AM, Ville M. Vainio<[email protected]> wrote:
On Sat, Sep 25, 2010 at 4:56 PM, Sivan Greenberg<[email protected]> wrote:
Thanks for this reply, seems that betting on MGConfItem is reasonable.
Just use QSettings if you don't need to listen to subscribe to changes
in settings (most apps don't). GConf is too heavy and
platform-specific for most needs.
Given that, I wonder if it was re-chosen for either backward
compatibility with GNOMEish legacy from Maemo, the lack of any other
system that is close in feature set or both?
it was chosen because at the time of the choice, nothing better existed.
today, dconf is very slowly getting to the point where it needs to be,
so for MeeGo 1.3 we'll evaluate moving to that
(but for that move, I would want to see a plan to get rid of all of
gconf; because if we end up long term with both GConf and dconf
then we have the worst of both worlds, and would be better of sticking
to only GConf.)
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
