On 08/08/11 17:10, Tomeu Vizoso wrote: > On Sun, Aug 7, 2011 at 14:27, Stefan Kost <[email protected]> wrote: >> https://live.gnome.org/DocumentationProject/GtkDocLanguageBindings > For Python, we are extending the API that is provided through g-i via > "overrides": Python modules that add API on top. So part of the > sources for the Python API are outside the C library module (right now > inside pyobject, one day should be split out). > One thing we ned to agree on the community is that do we want all our api-docs look alike or do we want python docs look like other python docs etc. In the later case I don't see much things that gtk-doc can help here with. >> https://live.gnome.org/DocumentationProject/GtkDocGir > I was expecting that g-ir-parser would be able to put in the .gir > files all the information that gtk-doc requires, being able to drop > the overlapping code in gtk-doc that parses the sources and thus > having gtk-doc using .gir files as input. If nobody minds that gtk-doc will need to depend on a perl-xml parser, that could be done in the long term. But as I tried to docuemtn, there is still information that is not in the gir files (like the doc structure). This can be addressed though.
> Is that not realistic by some reason? I just hope that this would not complicate builds, as then gtk-doc would depend on gir files and not all projects that use gtkdoc might want to use gobject introspection. Stefan > Regards, > > Tomeu _______________________________________________ desktop-devel-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/desktop-devel-list
