On Fr, 2011-03-25 at 16:01 +0000, Thiago Macieira wrote: > Em sexta-feira, 25 de março de 2011, às 08:30:43, Arjan van de Ven escreveu: > > my concern is based on the (lack of) progress around QSparql in MeeGo. > > I'm sure it's all great in Harmattan, > > but a solid story for MeeGo has so far been lacking. Ideally QSparql > > becomes a real, full and open source member of the Qt family of APIs. > > (a solid story also includes proper moving away from older APIs) > > > > Until that's there.... color me a bit skeptical... it's been promised > > for a long time and hasn't really materialized very well yet. > > I don't know what's holding back its opensourcing. > > The joining to the Qt family is pending the completion of Qt modularisation > and the Qt 4.8 relase. Its schedule is targetted to MeeGo 1.3 and, as far as > we knew, there were no dependencies.
The last time I looked at QSparql, admittedly several months ago, it didn't strike me as a particularly modern C++ API. For example, it had lots of plain pointers where I would expect light-weight handles instead. QtMobility feels a lot more modern in comparison. Just my two cents, I have no idea what the goal is for QSparql. Is it meant to be part of Qt? Will there be an API review by Qt developers before including QSparql in Qt? To give just one example, who is the owner of a QSparqlResult? This example here has an explicit delete: http://maemo.gitorious.org/maemo-af/qsparql/blobs/master/examples/sparql/asynctracker/main.cpp This one doesn't: http://maemo.gitorious.org/maemo-af/qsparql/blobs/master/examples/sparql/simple/main.cpp These questions (and memory leak?) could be avoided if QSparqlResult wasn't a plain pointer. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
