Bug 20861 - Split interfaces list into Client, CM, AccountManager, ChannelDispatcher
Summary: Split interfaces list into Client, CM, AccountManager, ChannelDispatcher
Status: RESOLVED FIXED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: tp-spec (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Danielle Madeley
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-25 08:12 UTC by Will Thompson
Modified: 2009-03-27 07:37 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Will Thompson 2009-03-25 08:12:32 UTC 
It's not clear from <http://telepathy.freedesktop.org/spec/> which components should be implementing which interfaces. It would be clearer if the index were split up into the above four components in some way, perhaps with a small preamble for each.

This might need extra spec markup, tagging each interface with its component and having some component definition file?
Comment 1 Will Thompson 2009-03-25 08:18:57 UTC 
Simon suggests having a hierarchy in all.xml:

<tp:chapter name="Connection Manager">
 <tp:docstring>Explain what a CM does.</>
 <tp:chapter name="Connection Manager object">
  <xi:include href="Connection_Manager.xml"/>
 </>
 <tp:chapter name="Connection object">
  <tp:docstring>Connections model a single connection to an IM account...</tp:docstring>
  <xi:include href="Connection.xml"/>
  <xi:include href="Connection_Interface_Aliasing.xml"/>
  <xi:include href="Connection_Interface_Avatars.xml"/>
  <xi:include href="Connection_Interface_Capabilities.xml"/>
  <xi:include href="Connection_Interface_Contact_Capabilities.xml"/>
  <xi:include href="Connection_Interface_Contact_Info.xml"/>
  <xi:include href="Connection_Interface_Contacts.xml"/>
  <xi:include href="Connection_Interface_Location.xml"/>
  <xi:include href="Connection_Interface_Presence.xml"/>
  <xi:include href="Connection_Interface_Renaming.xml"/>
  <xi:include href="Connection_Interface_Requests.xml"/>
  <xi:include href="Connection_Interface_Simple_Presence.xml"/>
 </>
</>

<tp:chapter name="Client">
...
</>

etc.
Comment 3 Danielle Madeley 2009-03-26 04:15:41 UTC 
This works either with or without <tp:chapter>

So, I noticed that wjt's example has nested chapters, which mine doesn't do at the moment.

Is nested chapters a desirable feature? If so, I may need to refactor somewhat.
Comment 4 Danielle Madeley 2009-03-26 20:02:08 UTC 
Ok, I've made this support nested sections.

I figure that <tp:chapter> is a bit of a misnomer, so I've changed it to <tp:section>.
Comment 5 Danielle Madeley 2009-03-27 07:37:45 UTC 
Merged.

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.