On Saturday, 26 de March de 2011 22:10:13 Patrick Ohly wrote: > Yes, I know. I was just wondering whether QSparql follows that approach > intentionally and whether that is still considered good style for newly > designed APIs. QtMobility did things differently, and I personally > prefer that.
Yeah, apparently there are ways of designing APIs so that they are more easily
bound to QML.
But, to tell you the truth, I've never tried to learn them. I don't do any UI
work, so I've never bothered to learn any of the QtGui or QtDeclarative API (I
just know the general concepts, not the API).
So when I reviewed the QtSparql API, I did the best I could: design an easy to
use C++ API.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Senior Product Manager - Nokia, Qt Development Frameworks
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
