This is a guide to the wxPython GUI toolkit, written **by** a Python
programmer **for** his fellow Python programmers. It began as a
This is a guide to the wxPython GUI toolkit, written **by** a Python
programmer **for** his fellow Python programmers. It began as a
for C++ programmers), and evolved from there. And while there's
nothing wrong with C++...
Okay, you got me there. I hate C++. That's why I use Python. If you
for C++ programmers), and evolved from there. And while there's
nothing wrong with C++...
Okay, you got me there. I hate C++. That's why I use Python. If you
guide that's written with Python programmers in mind, keep reading
this one. If you like it, feel free to send me freshly roasted coffee
beans, dark chocolate, and large denomination currency. Better yet,
guide that's written with Python programmers in mind, keep reading
this one. If you like it, feel free to send me freshly roasted coffee
beans, dark chocolate, and large denomination currency. Better yet,
allows Python programmers to create programs with a robust, highly
functional graphical user interface, simply and easily. It is
implemented as a Python extension module (native code) that wraps the
allows Python programmers to create programs with a robust, highly
functional graphical user interface, simply and easily. It is
implemented as a Python extension module (native code) that wraps the
it is free for anyone to use and the source code is available for
anyone to look at and modify. And anyone can contribute fixes or
enhnacments to the project.
it is free for anyone to use and the source code is available for
anyone to look at and modify. And anyone can contribute fixes or
enhnacments to the project.
and other facilities on more than one platform. Version 2 currently
supports all desktop versions of MS Windows, Unix with GTK+, Unix with
Motif, and MacOS. An OS/2 port is in progress.
and other facilities on more than one platform. Version 2 currently
supports all desktop versions of MS Windows, Unix with GTK+, Unix with
Motif, and MacOS. An OS/2 port is in progress.
Applications Institute, University of Edinburgh, for internal use, and
was first made publicly available in 1992. Version 2 is a vastly
improved version written and maintained by Julian Smart, Robert
Applications Institute, University of Edinburgh, for internal use, and
was first made publicly available in 1992. Version 2 is a vastly
improved version written and maintained by Julian Smart, Robert
maximize investment in GUI application development. While a number of
commercial class libraries already existed for cross-platform
development, none met all of the following criteria:
maximize investment in GUI application development. While a number of
commercial class libraries already existed for cross-platform
development, none met all of the following criteria:
frameworks have emerged. However, none has the range of features,
flexibility, documentation and the well-established development team
frameworks have emerged. However, none has the range of features,
flexibility, documentation and the well-established development team
-As open source software, wxWindows has benefited from comments, ideas,
+As open source software, wxWidgets has benefited from comments, ideas,
over free libraries without an independent development team), plus a
robustness against the transience of one individual or company. This
openness and availability of source code is especially important when
over free libraries without an independent development team), plus a
robustness against the transience of one individual or company. This
openness and availability of source code is especially important when
overstated, since GUI application development is very time-consuming,
and sustained popularity of particular GUIs cannot be guaranteed.
Code can very quickly become obsolete if it addresses the wrong
overstated, since GUI application development is very time-consuming,
and sustained popularity of particular GUIs cannot be guaranteed.
Code can very quickly become obsolete if it addresses the wrong
-platform or audience. wxWindows helps to insulate the programmer from
-these winds of change. Although wxWindows may not be suitable for
+platform or audience. wxWidgets helps to insulate the programmer from
+these winds of change. Although wxWidgets may not be suitable for
every application (such as an OLE-intensive program), it provides
access to most of the functionality a GUI program normally requires,
plus many extras such as network programming, PostScript output, and
HTML rendering; and it can of course be extended as needs dictate. As
a bonus, it provides a far cleaner and easier programming interface
than the native APIs. Programmers may find it worthwhile to use
every application (such as an OLE-intensive program), it provides
access to most of the functionality a GUI program normally requires,
plus many extras such as network programming, PostScript output, and
HTML rendering; and it can of course be extended as needs dictate. As
a bonus, it provides a far cleaner and easier programming interface
than the native APIs. Programmers may find it worthwhile to use
paragraphs, but here are some of the benefits:
* Low cost (free, in fact!)
paragraphs, but here are some of the benefits:
* Low cost (free, in fact!)
GUI applications aren't all graphical wizardry. You'll also need
lists and hash tables. But since you're working with Python, you
should use the ones Python provides (list, tuple, dict), rather than
GUI applications aren't all graphical wizardry. You'll also need
lists and hash tables. But since you're working with Python, you
should use the ones Python provides (list, tuple, dict), rather than
The basic rule of thumb is this: If you can do it directly in Python,
you probably should. If there is a reason not to use a Python data
The basic rule of thumb is this: If you can do it directly in Python,
you probably should. If there is a reason not to use a Python data
You will undoubtedly need some platform-independent file functions,
and you may find it handy to maintain and search a list of paths using
You will undoubtedly need some platform-independent file functions,
and you may find it handy to maintain and search a list of paths using
so you don't need to delete these descendants explicitly.
.. When deleting a frame or dialog, use Destroy rather than delete so
so you don't need to delete these descendants explicitly.
.. When deleting a frame or dialog, use Destroy rather than delete so
until idle time (when all messages have been processed) to actually
delete the window, to avoid problems associated with the GUI
sending events to deleted windows.
.. If you decide to allocate a C++ array of objects (such as wxBitmap)
until idle time (when all messages have been processed) to actually
delete the window, to avoid problems associated with the GUI
sending events to deleted windows.
.. If you decide to allocate a C++ array of objects (such as wxBitmap)
- that may be cleaned up by wxWindows, make sure you delete the array
- explicitly before wxWindows has a chance to do so on exit, since
+ that may be cleaned up by wxWidgets, make sure you delete the array
+ explicitly before wxWidgets has a chance to do so on exit, since
calling delete on array members will cause memory problems.
.. wxColour can be created statically: it is not automatically cleaned
calling delete on array members will cause memory problems.
.. wxColour can be created statically: it is not automatically cleaned
translated into something appropriate for the wxPython version.
The two dots followed by uniformly indented text turns this
paragraph into a reStructuredText comment, so it doesn't appear
translated into something appropriate for the wxPython version.
The two dots followed by uniformly indented text turns this
paragraph into a reStructuredText comment, so it doesn't appear
As such, it adheres to the same license, which is provided here:
.. include:: ../licence/licendoc.txt
As such, it adheres to the same license, which is provided here:
.. include:: ../licence/licendoc.txt
projects / wxWidgets.git / blobdiff