On Tue, 26 May 2009 11:36:48 +0200, "Werner F. Bruhin"
Both these docs are reference doc, they are not how to docs.
Not really. They don't provide any "reference" points...
There's nothing that a python programmer needs in the
current documentation...
Sadly... it doesn't work very well as reference material.
In Boa there is a little tutorial to get going with Boa/wxPython - if
you have some suggestions on how that could be enhanced to make it
easier, you can either write it and I will incorporate it or you can
just make some suggestions and I will add it to my todo list.
The wxpython documentation needs revising. It just needs a fresh
rework from an application developers perspective.
That means... what wxpython has.... what it gives you...
and some proper pythonic examples and references...
- Then one of the best tools to get going is the wxPython demo (a
separate download with the docs).
Yes - but the example python code needs to be where the C++ code
currently sits. Right where you need it. Not in some seperate
system that needs a seperate download. That's not how good
documentation works.
But there are good reasons why it is that way and Robin and others have
only so much time in a day, i.e. 24 also I wonder sometimes if Robin
figured out how to get 48 out of day.
Well I understand that completely...
But likewise, the burden of all the documentation shouldn't lie on
Robin alone.
Here some help/information on this:
C++GuideForwxPythoneers - wxPyWiki
C++ & Python Sandwich - wxPyWiki
C++Extensions - wxPyWiki
Man... (sigh)
That's a lot of documentation to have to read to find out an
answer to how to set up splitter components on a wxpython app...
I already found the spot in the reference material where it
was supposed to be but their was nothing written.
If you're somehow suggesting that I read through all the
documentation and somehow colate it into something useful
I probably would be a bit more positive....
To mind.. the existing documentation structure is pretty good. It
just needs revising. Adding better descriptions of what the classes
do... Listing the key properties and methods.. and providing
an in-situ example that a developer can cut and paste directly.
That's basically what I am suggesting needs doing.
And last but not least this is the wxpython-users list, a lot of
extremely nice and helpful bunch of people hang out here and they are
always very helpful when one asks nicely.
Yes - I don't doubt that.
But application developers too have only so many hours in the day.
I don't blame any application developer for being annoyed when they
have to work 4 hours extra hunting through useless documentation
and google till 3am to answer a question on how to do something that
should have been a two minute task....
You may say you are helpful, but I never got an answer on what
I need to do to put the splitter components together into something
working. Like I said... I gave up... moved onto something else...
David
(ps: I have a client who uses dBase IV. I dream for documentation
that good. Would anybody be interested to see scans of their
documentation? It takes only 2 mins to get an answer on literally
anything from their reference manual. And that is a paper book! )