[Bug 77139] New: [next] remove dbus-glib GTypes from public API: low-hanging ones

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Apr 7 08:03:53 PDT 2014


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

          Priority: medium
            Bug ID: 77139
                CC: xclaesse at gmail.com
          Assignee: simon.mcvittie at collabora.co.uk
            Blocks: 76369
           Summary: [next] remove dbus-glib GTypes from public API:
                    low-hanging ones
        QA Contact: telepathy-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: simon.mcvittie at collabora.co.uk
          Hardware: Other
            Status: ASSIGNED
           Version: git master
         Component: tp-glib
           Product: Telepathy

+++ This bug was initially created as a clone of Bug #76369 +++

We should make sure that dbus-glib isn't exposed in our high-level API.

This is a start. Of the things in Bug #76369, I covered:


TpAccount:connection-error-details is an a{sv}. TpAccount::status-changed
contains the same.

tp_capabilities_get_channel_classes returns a{sv}s.
TpCapabilities:channel-classes is the same.

TpCapabilities:channel-classes (but it also has channel-classes-variant)


tp_connection_manager_param_get_default has a parallel GVariant version
already, so it can probably be deleted.

Unrelated, but handle.h should talk about entity types, not handle types.

tp_message_set takes a GValue.

tp_account_get_avatar_finish() returns a GArray<guchar> which is OK but a bit
odd.

TpChannelDispatchOperation:cdo-properties

TpChannel:channel-properties

TpChannel::group-members-changed (the details)

TpObserveChannelContext:observer-info

TpTextChannel:message-types (would be OK with a different GType)

TpAccountRequest:avatar is a GArray of undocumented type (by inspection:
GArray<guchar>, which is a bit weird and a GBytes would probably be better).

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


More information about the telepathy-bugs mailing list