[Bug 77187] [next] Remove dbus-glib GTypes from public API: properties and handwritten signals

[bugzilla-daemon at freedesktop.org]

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

--- Comment #1 from Simon McVittie <simon.mcvittie at collabora.co.uk> ---
On Bug #76369 I wrote:

> TpBaseConnectionManager:protocols (because it contains their properties)
> TpBaseConnection:requestable-channel-classes
> TpBaseConnection:dbus-status
> TpExportableChannel:channel-properties

These are done in a branch.
http://cgit.freedesktop.org/~smcv/telepathy-glib/log?h=rm-dbus-glib-properties1

Still to do:

Misc
----

> TpBasePasswordChannel:sasl-error-details (but it's internal anyway)

Not used in the "big 5" CMs.

> TpBaseProtocol:immutable-properties

Gabble uses that, and overriding it is documented to be how you extend the
Protocol. I think we should make it into a GVariant.

The Call stuff
--------------

> TpBaseCallChannel:contents, TpBaseCallChannel:call-state-reason,
> TpBaseCallChannel:call-state-details, TpBaseCallChannel:call-members,
> TpBaseCallChannel:member-identifiers
> TpBaseCallContent:streams
> TpBaseCallStream:remote-members (but it would be fine with a different GType)
> TpBaseCallStream:remote-member-identifiers (but it would be fine with a
> different GType)
> TpBaseMediaCallContent:remote-media-descriptions,
> TpBaseMediaCallContent:local-media-descriptions,
> TpBaseMediaCallContent:media-description-offer,
> TpBaseMediaCallStream:local-credentials,
> TpBaseMediaCallStream:local-candidates, TpBaseMediaCallStream:stun-servers,
> TpBaseMediaCallStream:relay-info, TpBaseMediaCallStream:endpoints (but it
> would be OK with a different GType)
> TpCallContentMediaDescription:codecs, TpCallContentMediaDescription:ssrcs,
> TpCallContentMediaDescription:header-extensions,
> TpCallContentMediaDescription:feedback-messages
> TpCallStreamEndpoint:remote-credentials,
> TpCallStreamEndpoint:remote-candidates,
> TpCallStreamEndpoint:selected-candidate-pairs,
> TpCallStreamEndpoint:endpoint-state,
> TpCallStreamEndpoint::candidate-selected,
> TpCallStreamEndpoint::candidate-accepted,
> TpCallStreamEndpoint::candidate-rejected

None of those are used in the "big 5" CMs.

> TpBaseMediaCallContent::local-media-description-updated

Rakia and Gabble do use that.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.