Andrew P. Lentvorski, Jr. wrote:
On Wed, 11 Feb 2004, trash1 wrote:
I'm try to migrate from wxPython to PyGTK.
Don't get me wrong; I'm happy to see this. However, what are your reasons
for wanting to migrate from wxPython to PyGTK? I ask this because I get
asked the question of "Why use PyGTK instead of wxPython?", but I can't
really answer it well since I haven't used wxPython significantly.
I would love to hear your answers and assessments.
I'm not the original poster and I've never used wxPython but I did evaluate it when I was selecting a toolkit for my current project. The biggest problem I had with it was that, at the time, it didn't actually use gtk2 so it looked pretty awful. Other than that it seemed like a needless extra layer and the only plus was easy portability to windows which I don't care about.
I DO care about portability, so I did look at it, but
1. It was hard to learn and use, pyGTK is very intuitive
2. No GLADE! Glade rocks the house and I use it on a daily basis. I think of it as a competitive advantage over people who are coding their widgets by hand or even using a code-generation tool.
3. Very buggy (it's been a few months since I've tested, but it crashed on me all the time)
4. Distribution was a pain (please install this rpm, etc etc). pyGTK does have versioning issues, but dropline has made my life fairly easy. (Still wish I could compile a dropline release from scratch though).
-dave
_______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
