Em Sexta-feira 25. Junho 2010, às 08.48.34, Patrick Ohly escreveu: > Hello! > > I thought about posting this on the Trolltech feedback list, but as > MeeGo APIs were discussed here recently I decided to stay here. > > I have one conceptual question about QtContacts and Tracker. QtContacts > is the high-level API that applications are meant to use. It abstracts > away from the underlying storage mechanism, which happens to be Tracker > when using the qtcontacts-tracker backend. > > The goal of using Tracker is that the data can be reused in other > contexts, like direct SPARQL queries or other apps resp. APIs (like the > future QtCalendar) - right? But how does that work in practice? > > When finding a contact in Tracker, it would be necessary to open it in > QtContacts. Likewise, when creating a contact in QtContacts, some way of > referencing it in Tracker is needed. Is there an implicit guarantee that > the QContactId has a certain relationship with Tracker?
I doubt that the Contacts API will give you that guarantee because it's
supposed to be backend-agnostic. It could be gathering data from multiple
backends and none of them might be Tracker.
--
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
