Summary: | Split interfaces list into Client, CM, AccountManager, ChannelDispatcher | ||
---|---|---|---|
Product: | Telepathy | Reporter: | Will Thompson <will> |
Component: | tp-spec | Assignee: | Danielle Madeley <danielle> |
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
Will Thompson
2009-03-25 08:12:32 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. 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. 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>. 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.