Hey Robin,
I was just wondering what the status is on the documentation you've been creating for wxPython, specifically the auto-generated ones? What was the tool you were using again and did the changes you made get incorporated back into the main release of that tool so that I might be able to use it for PythonCard?
ka
Kevin Altis wrote:
Hey Robin,
I was just wondering what the status is on the documentation you've been creating for wxPython, specifically the auto-generated ones? What was the tool you were using again and did the changes you made get incorporated back into the main release of that tool so that I might be able to use it for PythonCard?
I'm using epydoc, with some customizations added. I submitted a patch to epydoc and IIRC earlier this year some changes were applied, some were not and one was changed (incompatibly [1]) before being checked in. I havn't updated my version to include the new epydoc changes in CVS yet so I've put some packages on starship. I'll put up a pre-patched tarball of SWIG with my patches included there too.
http://starship.python.net/crew/robind/wxPython/tools/
[1] The change had to do with the expected format of the function signatures embedded in docstrings that include parameter types. I hacked SWIG to output a simplified C-like syntax, and updated epydoc to recognize that syntax. But Ed prefered the proposed syntax for adding parameter types to Python and implemented that syntax instead. So I'll have to update my SWIG patches to output that syntax before I can make the switch to the newer epydoc...
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!