Micheal,
Thank you for volunteering to head up such a task. One issue to
consider is maintenance. Every time a new version of wxWindows comes out,
Robin uses an automated tool (SWIG) to generate the interface code to
python. SWIG also provides a mechanism for generating docs in HTML and a
couple of other formats. This could make maintenance easier.
Also please see the attached email from David Priest about a doc
project. If he is still working on it you may wish to join forces.
Jan
···
I can't agree more with this -- moreover, I'd be happy to
head up a documentation
translation/maintenance effort. How would one set about
doing that? Obviously
it'd be best to coordinate with you, Robin, so .. here I am.
(Case in point of
having to hunt through the demo code was simply how to use
the File Open common
dialog. That was an irritating waste of time.)The idea would be to take the C++ version and simply
translate everything into a
Python frame of reference, with all functions shown in Python
syntax, the Python
notes merged into the text, and (hopefully!) Python examples.
The end result would
be a useful document which could be a set of pages, a help
file, and a book. Am I
crazy, does anybody else wish they had that book to spread on
their desk while
coding?Michael
_______________________________________________
wxPython-users mailing list
wxPython-users@lists.sourceforge.net
http://lists.sourceforge.net/mailman/listinfo/wxpython-users