So I have some tips about documentation: 1. it would be great to have an option to enter my thoughts, tips, misunderstandings right on the documentation page. Like PHP does. I think it's good. [...]And I think, there is plenty of "little informations" that could
be collected from users.
Exactly my sentiments. I've often been reading the docs and come across a small item which was unclear or could have been explained better. It's currently too troublesome to submit a "full" documentation patch or annotation. If the docs had a link to a wiki page for instance, I could make the change and perhaps the changes could be batch merged into CVS periodically.
2. While viewing info about classess there are viewed only methods and signals from the displayed class. But there are a lot of other methods form ancestors. [...]
This one, I don't really mind - after working for a little while it becomes intuitively obvious which base class you should be looking in. Regards, Stephen. _______________________________________________ pygtk mailing list [email protected] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
