> As between Tkinter and wxPython, I started on Tkinter, but have been won > over to wxPython, although I've only played with it so far. The problem > with wxPython is that it's poorly documented, but there's a book out on it > now that you should beg, borrow or steal if you plan on using it.
Tkinter is easier to program from the start, but I quickly discarded it for wxPython. Reasons: The windows looked foreign, and childish, because as a newbie at the time I didn't want to take the time making things pretty (padx = ...) wxPython uses 'native looking windows' meaning that windows you create with wxPython will look like other windows on your machine. (In XP, for example, round edges, blue, thick, 3d looking) wxPython seems very powerful and thorough. It is also more modern. I would suggest starting with Tkinter to get a feel for what it takes to create a GUI and drive it, then when you become comfortable, switch to something more professional looking/powerful. > The big advantage of Tkinter is that it's already distributed with Python, > so you already have it installed. Yep. Definite advantage. > I've heard good things about PythonCard (which is built on top of > wxPython) but never tried it. http://pythoncard.sourceforge.net/ Can be error-prone (the resource editor sometimes freezes) and confusing (Uses a technique including importing the same module within itself?!?), but if you follow the example programs, you can get running code easily. Advantage is graphical control placement, as in a resource editor. The disadvantage of that is that an extra file is created to contain the resource information. As for being newbie friendly~~ Not as straight-forward as Tkinter to code, but easier to visualize because of the graphical control placement not available with Tkinter. Perhaps the errors have been fixed since I tested it out last. Cheers, JS _______________________________________________ Tutor maillist - Tutor@python.org http://mail.python.org/mailman/listinfo/tutor
