On Sat, Sep 25, 2010 at 5:45 PM, Robin Burchell <[email protected]> wrote: > No, at least, I very much doubt it. libgq seems to be unmaintained - or > at least, nobody seems interested in taking my patches to it, despite > repeated attempts to get somebody to have a look (see > http://lists.maemo.org/pipermail/maemo-developers/2010-August/027366.html > for details on that). I also don't think it is packaged for MeeGo. > > I suspect that MGConfItem > (http://apidocs.meego.com/mtf/class_m_g_conf_item.html) is the thing to use, > though > personally I think this would be better placed at the Qt level either > relating to > QSettings (as mentioned in a reply to this mail) or something, so as for > application > developers to maintain maximum portability (to e.g. Symbian)
Interestingly enough, the apidoc for MGConfItem looks suspiciously the same like the \brief in [0]. Seems likes only the name was changed into t MeeGo SDK naming. (MGConfItem instead o GConfItem as available from libgq). Anyway, this is probably the way to go and yes, your note that it should sit part of Qt instead of being "duplicated" in MeeGo makes sense, although sometimes it makes it easier to release a "consistent" API that wraps everything to unify access, so you always use MG* instead of Using Q* for settings, and MG* for touch stuff etc. Thanks for this reply, seems that betting on MGConfItem is reasonable. I wonder why we have to "suspect" things btw, isn't the fact it is at apidoc.meego.com makes it an "official" way to work with the settings? -Sivan _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
