[Bug 21787] Connection.Interface.ContactLists

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=21787

--- Comment #8 from Simon McVittie <simon.mcvittie at collabora.co.uk> 2010-04-14 09:11:20 PDT ---
Bugs:

* We need a way to signal publication requests *with the associated message*
(or just signal them and have a function-based accessor for the message, or
something). telepathy-qt4 doesn't yet do this either, although it does have a
convenient presencePublicationRequested() signal.

Extra features in telepathy-qt4:

* Tp::Contact has addedToGroup(), removedFromGroup() signals, whereas in my API
sketch, TpContact only has notify::groups - this would be easy to add though

* telepathy-qt4 has canRequestPresenceSubscription(),
canRemovePresenceSubscription(), etc., whereas this new API simplifies it to
CanChangeSubscriptions - hopefully we don't need the extra complexity and can
just ignore it

* telepathy-qt4 allows messages in more places - hopefully requesting
subscription is the only one that actually matters

* telepathy-qt4 can block and unblock contacts, which I've deferred here

* telepathy-qt4 also emits a signal when groups' members change - do we need
this, or can it just be inferred from the contacts' signals?

Omissions in telepathy-qt4:

* telepathy-qt4 doesn't yet have API for replacing a contact's groups (in the
older D-Bus API it uses, this would be unnecessarily hard)

* telepathy-qt4 doesn't have API for "completely remove a contact" yet (in the
older D-Bus API it uses, this is removal from "stored")

Misc differences:

* telepathy-qt4 puts the contact stuff on a helper object, Tp::ContactManager

Notable similarities:

* PresenceState is a 1:1 copy of what's already in telepathy-qt4

* Groups.Groups is Tp::ContactManager::allKnownGroups() in telepathy-qt4

* ContactList.Contacts is Tp::ContactManager::allKnownContacts()

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.