[Bug 29484] New: RequestableChannelClass should have high-level API
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue Aug 10 14:21:09 CEST 2010
https://bugs.freedesktop.org/show_bug.cgi?id=29484
Summary: RequestableChannelClass should have high-level API
Product: Telepathy
Version: git master
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: medium
Component: tp-qt4
AssignedTo: telepathy-bugs at lists.freedesktop.org
ReportedBy: ollisal at gmail.com
QAContact: telepathy-bugs at lists.freedesktop.org
Blocks: 29090
The D-Bus spec generated RequestableChannelClass struct is spreading across
TpQt4 APIs at an alarming rate (:D). While we already have some higher-level
accessors such as ContactCapabilities::supportsMediaCalls(), should we, in
fact, have a higher-level ChannelClass object (similarly to
Channel::GroupMemberChangeDetails) wrapping the variant map and having
accessors to the well-known channel immutable keys (such as
{set,has,}ChannelType), etc. There should also be something to manipulate the
optional parameters array with.
I believe this would be most useful for the planned filtering API additions
(bug #29090), specifically constructing filter channel classes and making sense
of existing filters. It would also provide a middle ground between the
CapabilitiesBase::supports() accessors and the bare variant map access still
needed for some tasks (at least in extensions).
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
More information about the telepathy-bugs
mailing list