On Thu, 2003-02-13 at 22:07, Miguel de Icaza wrote: > > > > However, I noticed there are a lot of virtual functions in the xml. > > Should these be present? I'm not sure what to write for them. Any hints? > > > > Similarly, should constructors be documented? More specifically the ones > > that only take a handle to the underlying object. > > Can you give us an example of this one?
In doc/en/Entry.xml, there is a public constructor on line 277 that takes a raw IntPtr. I would have thought the details of it should be hidden? There are lots of virtual methods in that same xml file (from line 59) that do not appear in my generated Entry.cs file. Should they be documented? > In order of importance, I would say: > > Gtk/Glade > Gdk/Gnome > Glib/Gnomeprint > Art/Atk/Pango > Gst Does Gst# have a maintainer? I've found it a great API to use, but has a couple of bugs, and I'd like to ensure it's "supported" to wrap GStreamer 0.6.0 rather than the dated 0.4.2 it currently wraps. If the above happens, I would hope that the priority and usefulness of Gst# docs would go up. :) Regards, Lee. _______________________________________________ Mono-docs-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-docs-list
