For what I understand every detail already have such functionality [QContact.detailUri] with this field you can specify from which contact this detail belongs, based on QContact.Guid;
Is correct to say that a contact which the type is "TypeGroup" is a meta contact with information from different contacts (A merged contact)? Renato Araujo Oliveira Filho On Mon, Jan 19, 2015 at 6:12 PM, Konstantin Ritt <ritt...@gmail.com> wrote: > IMO, such a merged contact should belong to a special "address book" - one > that aggregates contacts and knows which field/detail came from this or > that real contact. > > Regards, > Konstantin > > 2015-01-20 0:27 GMT+04:00 Renato Araujo <rena...@gmail.com>: > >> Hey guys, >> >> I started to implement the class QContactCollection based on >> QOrganizeCollection[1]. Until now I just copy the code from QOrganizer >> module and renamed some classes. >> >> The idea of QContactCollection is to represent an "address-book". And >> with this we can create/remove/modify collection and query contacts based >> on the collection id. >> >> This looks great, but I have one concern about that. How to represent >> contacts that are present in more than one "Address book" (merged >> contacts)? In this case the contact can have more than one collection. >> >> Do you have any idea how to solve that? >> >> Should we use a different approach? >> >> What about use QContactCollectionId as a derived class from >> QContactDetails? >> >> >> [1] https://codereview.qt-project.org/#/c/104026/ >> >> >> Thanks >> Renato Araujo Oliveira Filho >> >> _______________________________________________ >> Development mailing list >> Development@qt-project.org >> http://lists.qt-project.org/mailman/listinfo/development >> >> >
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
