I'm using wxPython, after very brief forays into Tk and Qt, and I like it a lot. wx generally wraps the native widgets of whatever OS/desktop it runs on, and its idiom felt more comfortable to me than the others. Also, unlike Qt, it's free... I hate to be a cheapskate, but I'm a very small business and I need to put food on my family, so the Qt license is a major hurdle.
<br><br><rant><br>I have to say, though, that as a recovering Visual Studio user there is one thing - believe me, it's the only thing! - I miss, and that's an honest-to-goodness WYSIWYG GUI designer. For the love of Pete, if Microsoft can get it right - and it's the only thing they did get right, IMHO - why can't we? Why can't you just draw your GUI on the screen and concentrate on the actual functionality in peace?
<br><br>In the wx world, I tried both PythonCard and wxGlade. PythonCard might be OK, but I didn't like it a bit; its stated goal is to be a re-creation of HyperCard, and I was never a fan. Also, I tried it just as I was first getting started with Python, and it sorta felt at odds with the gestalt of the language. I'm probably not being fair to it. Ah well.
<br><br>wxGlade wants to re-create the joys of working with Glade, but I've never used Glade. If it's anything like wxGlade, I'm glad to have missed out. wxGlade does some very nifty, sophisticated and impressive GUI work to create, for your delectation, a representation of your GUI that looks virtually nothing like the finished product. Looking at the display mid-process, you can neither see what the finished product will look like, nor what the code will look like. Along the way, there's a hierarchical organizer thingy that in theory should help you to put widgets inside of the frames, panels and sizers that contain them, but in my experience actually tends to put them at the same hierarchical level and refuses to let you fix any mistakes you might make. I've tried it four or five times - every time I get tired of wxCoding by hand - and each time I realize it's going to be easier to do it by hand.
<br><br>It's not really that hard, by the way. Draw yourself a picture ahead of time - on paper, or (as I do) with hyphens and pipe characters in the comments - so you can keep straight which sizers go inside of which. Then, build from the inside out. And when you get weary - and oh, you will get weary - indulge in just a little nostalgie de la bue.
<br><br></rant><br><br><br><div class="gmail_quote">On Jan 3, 2008 12:11 AM, Alan Gauld <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>"Roy Chen" <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote<br><br>> I suppose with any GUI toolkit/builder, you're going to have learn<br>> some part<br>> of the API anyway. I might just see how I go with wxPython for now.
<br><br>OK, wxPython is a fine toolkt. Just be aware that it does not have a<br>GUI<br>builder per se, you have to write the GUI as source code or use a<br>third<br>party GUI builder.<br><br>Alan G.<br><br><br>_______________________________________________
<br>Tutor maillist - <a href="mailto:Tutor@python.org">Tutor@python.org</a><br><a href="http://mail.python.org/mailman/listinfo/tutor" target="_blank">http://mail.python.org/mailman/listinfo/tutor</a><br></blockquote></div>
<br><br clear="all"><br>-- <br><a href="http://www.fsrtechnologies.com">www.fsrtechnologies.com</a>