On Tue, 2010-09-14 at 08:19 +0100, Ivan Frade wrote:
> Hi Patrick,
>
> AFAIK it is a bug in qtcontacts-tracker. In tracker you save in
> nco:photo (a DataObject with) the path of the contact photo. The binary
> blob with the picture is *not* in tracker (it is a regular file in the
> filesystem).
Ah, I see. I didn't follow the definition of nco:photo into the nie
ontology (still learning all this...). Right now, nco:photo in MeeGo
points towards an ID (icon-m-content-avatar-placeholder) about which no
further information is recorded.
So the questions then become:
* Where should such a file be stored?
* Who creates and removes it?
Both qtcontacts-tracker and contactsd (= Telepathy2Tracker sync,
http://gitorious.org/qtcontacts-tracker/contactsd) create contacts.
Based on the the alternative name ("to tracker") I assumed that
contactsd would interface with Tracker directly, but looking at the
source code briefly shows that it has dependencies on QtContacts.
Aleksandar, can you clarify?
If qtcontacts-tracker is the only entity which is allowed to manipulate
nco:photo items, then we don't need a system-wide policy. For apps,
Tracker data about contacts basically becomes read-only.
> The really great solution would be to integrate the contact picture
> with the thumbnailing system (get the photo of the contact is like
> asking a thumbnail of the contact URL); but that is not
> implemented/supported or even designed yet.
"the thumbnailing system" - this is the first time I hear about this. Do
you have pointers to further information about it?
--
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
