Python Documentation Blows!

[asdf sdf]

Chris Green wrote:

> Peter Hansen <peter at engcorp.com> writes:
> 
> 
>>anton muhin wrote:
>>
>>
>>>Maybe just start a wiki based on the current documentation? It
>>>shouldn't be too difficult, should it?
>>
>>What part of http://wiki.wxpython.org/ is not adequate?
> 
> 
> One problem wxpython's wiki seems to have is not enough time to
> refactor it (coupled with the namespace changing from wxEVENT =>
> wx.EVENT ) and lots of nodes being empty or partially duplicated.
> 

i'm trying out wxpython right now and trying to locate all the resources 
i can.  wxpython is cool but, to be fair, the documentation is not there 
for the junior programmer type.

i tried the 'obstacle course' tutorial, which looked promising, but most 
of it is just a table of contents waiting to be filled in.

right now, newbies have a special problem because wxpython is in the 
middle of a 'break the world' upgrade.  and some of the changes in the 
upgrade are being debated by the developers and might be changed again 
or rolled back.

so the newbie is at risk of running across samples that may be the old 
style and not realize it.

python documentation is great.

wxpython doc is at an early stage of development.

right now, wxpython offers the smoothest intro to someone who's 
comfortable using usenet for research (everyone here, but not everyone 
by any means), not dependent on rich IDEs, already familiar with python 
and python OOP, and is comfortable mentally mapping the documentation 
for the underlying C++ libraries into their wxPython counterparts.

Junior Programmer Joe out there in VB Land is not ready for wxpython.

OOT, the wxpython community and the mailing lists are an astonishing 
responsive and helpful group.  By far the most help group per capita, 
I've ever run across.  If you give wxpython a chance, the wxpython 
community will go more than the extra mile to help you out.