Bug 28751 - tp_proxy_has_interface not introspectable
Summary: tp_proxy_has_interface not introspectable
Status: RESOLVED FIXED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: tp-glib (show other bugs)
Version: unspecified
Hardware: Other All
: medium enhancement
Assignee: Simon McVittie
QA Contact: Telepathy bugs list
URL: http://git.collabora.co.uk/?p=user/sm...
Whiteboard:
Keywords: patch
Depends on:
Blocks:
 
Reported: 2010-06-25 00:25 UTC by Danielle Madeley
Modified: 2010-07-14 03:09 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Danielle Madeley 2010-06-25 00:25:11 UTC
It would be really great to do a bindable version of tp_proxy_has_interface().
Comment 1 Simon McVittie 2010-07-13 03:48:33 UTC
Fixed in my trivia branch, please review.
Comment 2 Danielle Madeley 2010-07-13 19:11:26 UTC
All 6 ++

Although why (skip) the getters? Seems a little inconsistent since in general they're not skipped throughout the rest of the API.
Comment 3 Simon McVittie 2010-07-14 03:09:34 UTC
(In reply to comment #2)
> All 6 ++

Sorry, forgot to close this; Guillaume reviewed the branch and also approved it. Fixed in git for 0.11.11.

> Although why (skip) the getters? Seems a little inconsistent since in general
> they're not skipped throughout the rest of the API.

If we have properties, is there much/any value in having getters too, for g-i? For instance, in Python (assuming we bound this file at all):

    my_base_client.props.dbus_daemon
    my_base_client.get_dbus_daemon()

I basically consider these duplicate getters to be "C bindings" for the properties, rather than a feature in their own right. Is that appropriate?

(This is more of a concern for getters that are called borrow_foo or dup_foo because of their C semantics, which should basically be turned into "get" by bindings anyway - if we keep these visible, we need to be careful to have the g-i name for these be appropriate, perhaps with the "Rename to:" annotation, if that works these days.)


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.