1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
|
<HTML>
<head><title>Other Python GUIs</title></head>
<BODY BGCOLOR=#FFFFFF>
<A NAME="wxpother"></A><CENTER>
<A HREF="wx.htm"><img align=center src="contents.gif" BORDER=0 ALT="Contents"></A> <A HREF="wx317.htm#wxPython"><img align=center src="up.gif" BORDER=0 ALT="Up"></A> <A HREF="wx319.htm#wxpwhy"><img align=center src="back.gif" BORDER=0 ALT="Previous"></A> <A HREF="wx321.htm#wxpbuild"><img align=center src="forward.gif" BORDER=0 ALT="Next"></A> </CENTER><HR>
<H2>Other Python GUIs</H2>
<P>
There are other GUI solutions out there for Python.<P>
<B><FONT COLOR="#FF0000">Tkinter</FONT></B><P>
Tkinter is the defacto standard GUI for Python. It is available
on nearly every platform that Python and Tcl/TK are. Why Tcl/Tk?
Well because Tkinter is just a wrapper around Tcl's GUI toolkit, Tk.
This has its upsides and its downsides...<P>
The upside is that Tk is a pretty veristile toolkit. It can be made
to do a lot of things in a lot of different environments. It is fairly
easy to create new widgets and use them interchangably in your
programs.<P>
The downside is Tcl. When using Tkinter you actually have two
separate language interpreters running, the Python interpreter and the
Tcl interpreter for the GUI. Since the guts of Tcl is mostly about
string processing, it is fairly slow as well. (Not too bad on a fast
Pentium II, but you really notice the difference on slower machines.)<P>
It wasn't until the lastest version of Tcl/Tk that native Look and
Feel's were possible on non-Motif platforms. This is because Tk
usually implements it's own widgets (controls) even when there are
native controls available.<P>
Tkinter is a pretty low-level toolkit. You have to do a lot of work
(verbose program code) to do things that would be much simpler with a higher
level of abstraction.<P>
<B><FONT COLOR="#FF0000">PythonWin</FONT></B><P>
PythonWin is an add-on package for Python for the Win32 platform. It
includes wrappers for MFC as well as much of the win32 API. Because
of its foundation, it is very familiar for programmers who have
experience with MFC and the Win32 API. It is obviously not compatible
with other platforms and toolkits. PythonWin is organized as separate
packages and modules so you can use the pieces you need without having
to use the GUI portions.<P>
<B><FONT COLOR="#FF0000">Others</FONT></B><P>
There are quite a few other GUI modules available for Python, some in
active use, some that havn't been updated for ages. Most are simple
wrappers around some C or C++ toolkit or another, and most are not
cross-platform compatible. See <A HREF="http://www.python.org/download/Contributed.html#Graphics">this
link</A>
for a listing of a few of them.<P>
</BODY></HTML>
|
