[gtk-doc] TODO: add some thoughts about including inherited docs

[Stefan Kost <stefkost src gnome org>]

commit ef141ae885e1e9948960ead815edeb757411a5e3
Author: Stefan Sauer <ensonic users sf net>
Date:   Wed Sep 14 15:37:13 2011 +0200

    TODO: add some thoughts about including inherited docs

 TODO |    8 ++++++--
 1 files changed, 6 insertions(+), 2 deletions(-)
---
diff --git a/TODO b/TODO
index ad08987..7f160d1 100644
--- a/TODO
+++ b/TODO
@@ -180,6 +180,7 @@ more warnings:
   * devhelp could show a selector for the language
   * need to get existing python/~mm docs to use it, gtk-doc could output
     language=C for own docs
+
 == installation ==
 * need to install each book with a prefix
 * would be good to have a language attribute in book tag to allow filter by language
@@ -215,7 +216,7 @@ The changes could be made in gtkdoc-mkdb::ExpandAbbreviations()
 * we could require stdin for input and stdout for output, the wrapper for the
   actual tool can ensure the convention
 
-== ascii doc as a frontend ==
+== asciidoc as a frontend ==
 Can we offer integration with asciidoc (http://www.methods.co.nz/asciidoc/)?
 This way the master document could be written much easier. It would be cool if
 we could use the asciidoc markup in source-comments also.
@@ -270,6 +271,10 @@ problems:
 * we need to catch those when processing the docbook and expanding the |[
 * require new macro syntax
 
+== show inherited api ==
+could we write small html files for each object for methods, signals and properties and then use iframes to combine those at runtime like in javadoc?
+could we do that using javascript and some other magic?
+
 
 = syntax =
 == wildcards in symbol names ==
@@ -477,4 +482,3 @@ grep "gst_caps_is_always_compatible" tags
     nytprofhtml
     firefox nytprof/index.html
 
-