Help in wxpython

Mike Driscoll kyosohma at gmail.com
Thu Dec 3 17:09:26 EST 2009


On Dec 3, 3:22 pm, Nobody <nob... at nowhere.com> wrote:
> On Thu, 03 Dec 2009 07:55:19 +0000, r0g wrote:
> > I have to recommend to opposite, stick with wx. What's the point of
> > tying yourself into GTK when wx works on Mac, PC and Linux?
>
> The main drawbacks are that wxWidgets sucks compared to GTK or Qt (mostly
> due to being modelled on the Win32 API, which itself sucks compared to
> most Unix/X11 toolkits), and that wxPython is woefully under-documented
> (whereas PyGTK is better documented than GTK itself).
>
> But if you need portability, wxPython is the way to go.

There is currently an on-going documentation initiative going on for
wxPython. Robin Dunn is doing some work on it that will allow much
easier documentation patching (as I understand it), so that should get
better.

Also, I am slowly working my way through wxPython many widgets and
doing tutorials on them on my blog, which I then stick in the official
wxPython wiki if I think the article is good enough.

-------------------
Mike Driscoll

Blog:   http://blog.pythonlibrary.org



More information about the Python-list mailing list