Bug 16995

Summary: Work around gtkdoc's inability to document GInterfaces' signals and properties
Product: Telepathy Reporter: Simon McVittie <smcv>
Component: tp-glibAssignee: Simon McVittie <smcv>
Status: RESOLVED FIXED QA Contact: Telepathy bugs list <telepathy-bugs>
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Simon McVittie 2008-08-05 08:48:57 UTC
We need to document the required signals and properties for our public GInterfaces, TpChannelIface and TpChannelFactoryIface (and also GabbleExportableChannel and GabbleChannelManager, when we move those to telepathy-glib).

The information exists in the source code but it doesn't make it into the HTML, because gtkdoc only knows how to extract signals and properties from GObjects, not GInterfaces.
Comment 1 Murray Cumming 2008-08-05 23:05:34 UTC
Is there a gtk-doc bug open for that? It should be possible (we manage to extra signal and property information for GInterfaces to generate .defs for gtkmm).
Comment 2 Simon McVittie 2008-09-02 05:44:26 UTC
I talked to Stefan about this while in Helsinki, and it looks like I can probably sort this out when I have time. (We might need a newer minimum version of gtkdoc.)
Comment 3 Simon McVittie 2008-09-26 07:46:28 UTC
Will be fixed in the next release, at the cost of requiring gtkdoc 1.10.

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.