]> git.saurik.com Git - wxWidgets.git/blame - docs/latex/wx/wxPython.tex
Minor changes
[wxWidgets.git] / docs / latex / wx / wxPython.tex
CommitLineData
06d20283
RD
1\chapter{wxPython Notes}\label{wxPython}
2\pagenumbering{arabic}%
3\setheader{{\it CHAPTER \thechapter}}{}{}{}{}{{\it CHAPTER \thechapter}}%
4\setfooter{\thepage}{}{}{}{}{\thepage}%
5
2a47d3c1
JS
6This addendum is written by Robin Dunn, author of the wxPython wrapper
7
06d20283
RD
8%----------------------------------------------------------------------
9\section{What is wxPython?}\label{wxpwhat}
10
f899db6d 11wxPython is a blending of the wxWindows GUI classes and the
06d20283
RD
12\urlref{Python}{http://www.python.org/} programming language.
13
14\wxheading{Python}
15
f899db6d 16So what is Python? Go to
06d20283
RD
17\urlref{http://www.python.org}{http://www.python.org}
18to learn more, but in a nutshell Python is an interpreted,
19interactive, object-oriented programming language. It is often
20compared to Tcl, Perl, Scheme or Java.
21
22Python combines remarkable power with very clear syntax. It has
23modules, classes, exceptions, very high level dynamic data types, and
24dynamic typing. There are interfaces to many system calls and
25libraries, and new built-in modules are easily written in C or
26C++. Python is also usable as an extension language for applications
27that need a programmable interface.
28
29Python is copyrighted but freely usable and distributable, even for
30commercial use.
31
32\wxheading{wxPython}
33
34wxPython is a Python package that can be imported at runtime that
35includes a collection of Python modules and an extension module
36(native code). It provides a series of Python classes that mirror (or
37shadow) many of the wxWindows GUI classes. This extension module
38attempts to mirror the class heiarchy of wxWindows as closely as
39possble. This means that there is a wxFrame class in wxPython that
40looks, smells, tastes and acts almost the same as the wxFrame class in
41the C++ version.
42
43wxPython is very versitile. It can be used to create standalone GUI
44applications, or in situations where Python is embedded in a C++
45application as an internal scripting or macro language.
46
47Currently wxPython is available for Win32 platforms and the GTK
2a47d3c1
JS
48toolkit (wxGTK) on most Unix/X-windows platforms. The effort to
49enable wxPython for wxMotif will begin shortly. See \helpref{Building Python}{wxpbuild} for
50details about getting wxPython working for you.
06d20283
RD
51
52
53%----------------------------------------------------------------------
54\section{Why use wxPython?}\label{wxpwhy}
55
06d20283 56So why would you want to use wxPython over just C++ and wxWindows?
2a47d3c1
JS
57Personally I prefer using Python for everything. I only use C++ when
58I absolutely have to eek more performance out of an algorithm, and even
06d20283
RD
59then I ususally code it as an extension module and leave the majority
60of the program in Python.
61
62Another good thing to use wxPython for is quick prototyping of your
63wxWindows apps. With C++ you have to continuously go though the
64edit-compile-link-run cycle, which can be quite time comsuming. With
65Python it is only an edit-run cycle. You can easily build an
66application in a few hours with Python that would normally take a few
67days or longer with C++. Converting a wxPython app to a C++/wxWindows app
68should be a straight forward task.
69
06d20283
RD
70%----------------------------------------------------------------------
71\section{Other Python GUIs}\label{wxpother}
72
73There are other GUI solutions out there for Python.
74
75\wxheading{Tkinter}
76
77Tkinter is the defacto standard GUI for Python. It is available
78on nearly every platform that Python and Tcl/TK are. Why Tcl/Tk?
79Well because Tkinter is just a wrapper around Tcl's GUI toolkit, Tk.
80This has its upsides and its downsides...
81
82The upside is that Tk is a pretty veristile toolkit. It can be made
83to do a lot of things in a lot of different environments. It is fairly
84easy to create new widgets and use them interchangably in your
85programs.
86
87The downside is Tcl. When using Tkinter you actually have two
88separate language interpreters running, the Python interpreter and the
89Tcl interpreter for the GUI. Since the guts of Tcl is mostly about
90string processing, it is fairly slow as well. (Not too bad on a fast
91Pentium II, but you really notice the difference on slower machines.)
92
93It wasn't until the lastest version of Tcl/Tk that native Look and
94Feel's were possible on non-Motif platforms. This is because Tk
95usually implements it's own widgets (controls) even when there are
96native controls available.
97
98Tkinter is a pretty low-level toolkit. You have to do a lot of work
99(verbose program code) to do things that would be much simpler with a higher
100level of abstraction.
101
102\wxheading{PythonWin}
103
104PythonWin is an add-on package for Python for the Win32 platform. It
105includes wrappers for MFC as well as much of the win32 API. Because
106of its foundation, it is very familiar for programmers who have
107experience with MFC and the Win32 API. It is obviously not compatible
108with other platforms and toolkits. PythonWin is organized as separate
109packages and modules so you can use the pieces you need without having
110to use the GUI portions.
111
112\wxheading{Others}
113
114There are quite a few other GUI modules available for Python, some in
115active use, some that havn't been updated for ages. Most are simple
116wrappers around some C or C++ toolkit or another, and most are not
117cross-platform compatible. See \urlref{this
118link}{http://www.python.org/download/Contributed.html\#Graphics}
119for a listing of a few of them.
120
06d20283
RD
121%----------------------------------------------------------------------
122\section{Building wxPython}\label{wxpbuild}
123
124I used SWIG (\urlref{http://www.swig.org}{http://www.swig.org}) to
125create the source code for the extension module. This enabled me to
126only have to deal with a small amount of code and only have to bother
127with the exceptional issues. SWIG takes care of the rest and
128generates all the repetative code for me. You don't need SWIG to
129build the extension module as all the generated C++ code is included
130under the src directory. If you try to build wxPython and get errors
131because SWIG is missing, then simply touch the .cpp and .py files so
132make won't attempt to build them from the .i files.
133
134I added a few minor features to SWIG to control some of the code
135generation. If you want to play around with this the patches are in
136wxPython/SWIG.patches and they should be applied to the 1.1p5 version
f899db6d 137of SWIG. These new patches are documented at
06d20283
RD
138\urlref{this site}{http://starship.skyport.net/crew/robind/python/\#swig},
139and they should also end up in the 1.2 version of SWIG.
140
141wxPython is organized as a Python package. This means that the
142directory containing the results of the build process should be a
143subdirectory of a directory on the \tt{PYTHONPATH}, (and preferably
144should be named wxPython.) You can control where the build process
145will dump wxPython by setting the \tt{TARGETDIR} makefile variable.
146The default is \tt{\$(WXWIN)/utils/wxPython}. If you leave it here
147then you should add \tt{\$(WXWIN)/utils} to your \tt{PYTHONPATH}.
f899db6d 148However, you may prefer to use something that is already on your
06d20283 149\tt{PYTHONPATH}, such as the \tt{site-packages} directory on Unix
2a47d3c1 150systems.
06d20283
RD
151
152\wxheading{Win32}
153
154These instructions assume that you have Microsoft Visual C++ 5.0 or
1556.0, that you have installed the command-line tools, and that the
156appropriate environment variables are set for these tools. You should
157also have Python 1.5.1 installed, and wxWindows installed and built as
158specified below.
159
160\begin{enumerate}\itemsep=0pt
161\item Build wxWindows with \tt{wxUSE_RESOURCE_LOADING_IN_MSW} set to 1 in
162\tt{include/wx/msw/setup.h} so icons can be loaded dynamically. While
163there, make sure \tt{wxUSE_OWNER_DRAWN} is also set to 1.
06d20283 164\item Change into the \tt{\$(WXWIN)/utils/wxPython/src} directory.
06d20283
RD
165\item Edit makefile.vc and specify where your python installation is at.
166You may also want to fiddle with the \tt{TARGETDIR} variable as described
167above.
06d20283 168\item Run \tt{nmake -f makefile.vc}
06d20283
RD
169\item If it builds successfully, congratulations! Move on to the next
170step. If not then you can try mailing the wxwin-developers list for
f899db6d 171help. Also, I will always have a pre-built win32 version of this extension module at
06d20283 172\urlref{http://alldunn.com/wxPython}{http://alldunn.com/wxPython}.
f899db6d
RD
173\item Change to the \tt{\$(WXWIN)/utils/wxPython/demo} directory.
174\item Try executing the demo program. Note that some of the demos print
06d20283
RD
175diagnositc or test info to standard output, so they will require the
176console version of python. For example:
177
f899db6d 178\tt{python demo.py}
06d20283
RD
179
180To run them without requiring a console, you can use the \tt{pythonw.exe}
181version of Python either from the command line or from a shortcut.
06d20283
RD
182\end{enumerate}
183
06d20283
RD
184\wxheading{Unix}
185
186These directions assume that you have already successfully built
f899db6d 187wxWindows for GTK, and installed Python 1.5.1 or later. If you build Python
06d20283
RD
188yourself, you will get everything installed that you need simply by
189doing \bftt{make install}. If you get Python from an RPM or other
190pre-packaged source then there will probably be a separate package
191with the development libraries, etc. that you will need to install.
192
193
194\begin{enumerate}\itemsep=0pt
195\item Change into the \tt{\$(WXWIN)/utils/wxPython/src} directory.
06d20283
RD
196\item Edit \tt{Setup.in} and ensure that the flags, directories, and toolkit
197options are correct, (hopefully this will be done by \tt{configure}
198soon.) See the above commentary about \tt{TARGETDIR}. There are a
199few sample Setup.in.[platform] files provided.
06d20283
RD
200\item Run this command to generate a makefile:
201
2a47d3c1 202\tt{make -f Makefile.pre.in boot}
06d20283 203
f899db6d 204\item Once you have the \tt{Makefile}, run \bftt{make} to build and then
06d20283 205\bftt{make install} to install the wxPython extension module.
f899db6d
RD
206\item Change to the \tt{\$(WXWIN)/utils/wxPython/demo} directory.
207\item Try executing the demo program. For example:
06d20283 208
f899db6d 209\tt{python demo.py}
06d20283
RD
210\end{enumerate}
211
212
06d20283
RD
213%----------------------------------------------------------------------
214\section{Using wxPython}\label{wxpusing}
215
216\wxheading{First things first...}
217
218I'm not going to try and teach the Python language here. You can do
219that at the \urlref{Python Tutorial}{http://www.python.org/doc/tut/tut.html}.
220I'm also going to assume that you know a bit about wxWindows already,
221enough to notice the similarities in the classes used.
222
223Take a look at the following wxPython program. You can find a similar
f899db6d 224program in the \tt{wxPython/demo} directory, named \tt{DialogUnits.py}. If your
06d20283
RD
225Python and wxPython are properly installed, you should be able to run
226it by issuing this command:
227
228\begin{indented}{1cm}
f899db6d 229 \bftt{python DialogUnits.py}
06d20283
RD
230\end{indented}
231
232\hrule
233
234\begin{verbatim}
235001: ## import all of the wxPython GUI package
236002: from wxPython.wx import *
237003:
238004: ## Create a new frame class, derived from the wxPython Frame.
239005: class MyFrame(wxFrame):
240006:
241007: def __init__(self, parent, id, title):
242008: # First, call the base class' __init__ method to create the frame
243009: wxFrame.__init__(self, parent, id, title,
244010: wxPoint(100, 100), wxSize(160, 100))
245011:
246012: # Associate some events with methods of this class
247013: EVT_SIZE(self, self.OnSize)
248014: EVT_MOVE(self, self.OnMove)
249015:
250016: # Add a panel and some controls to display the size and position
251017: panel = wxPanel(self, -1)
252018: wxStaticText(panel, -1, "Size:",
253019: wxDLG_PNT(panel, wxPoint(4, 4)), wxDefaultSize)
254020: wxStaticText(panel, -1, "Pos:",
255021: wxDLG_PNT(panel, wxPoint(4, 14)), wxDefaultSize)
256022: self.sizeCtrl = wxTextCtrl(panel, -1, "",
257023: wxDLG_PNT(panel, wxPoint(24, 4)),
258024: wxDLG_SZE(panel, wxSize(36, -1)),
259025: wxTE_READONLY)
260026: self.posCtrl = wxTextCtrl(panel, -1, "",
261027: wxDLG_PNT(panel, wxPoint(24, 14)),
262028: wxDLG_SZE(panel, wxSize(36, -1)),
263029: wxTE_READONLY)
264030:
265031:
266032: # This method is called automatically when the CLOSE event is
267033: # sent to this window
268034: def OnCloseWindow(self, event):
269035: # tell the window to kill itself
270036: self.Destroy()
271037:
272038: # This method is called by the system when the window is resized,
273039: # because of the association above.
274040: def OnSize(self, event):
275041: size = event.GetSize()
276042: self.sizeCtrl.SetValue("%s, %s" % (size.width, size.height))
277043:
278044: # tell the event system to continue looking for an event handler,
279045: # so the default handler will get called.
280046: event.Skip()
281047:
282048: # This method is called by the system when the window is moved,
283049: # because of the association above.
284050: def OnMove(self, event):
285051: pos = event.GetPosition()
286052: self.posCtrl.SetValue("%s, %s" % (pos.x, pos.y))
287053:
288054:
289055: # Every wxWindows application must have a class derived from wxApp
290056: class MyApp(wxApp):
291057:
292058: # wxWindows calls this method to initialize the application
293059: def OnInit(self):
294060:
295061: # Create an instance of our customized Frame class
296062: frame = MyFrame(NULL, -1, "This is a test")
297063: frame.Show(true)
298064:
299065: # Tell wxWindows that this is our main window
300066: self.SetTopWindow(frame)
301067:
302068: # Return a success flag
303069: return true
304070:
305071:
306072: app = MyApp(0) # Create an instance of the application class
307073: app.MainLoop() # Tell it to start processing events
308074:
309\end{verbatim}
310\hrule
311
2a47d3c1
JS
312\wxheading{Things to notice}
313
314\begin{enumerate}\itemsep=0pt
06d20283
RD
315\item At line 2 the wxPython classes, constants, and etc. are imported
316into the current module's namespace. If you prefer to reduce
317namespace polution you can use "\tt{from wxPython import wx}" and
318then access all the wxPython identifiers through the wx module, for
319example, "\tt{wx.wxFrame}".
06d20283
RD
320\item At line 13 the frame's sizing and moving events are connected to
321methods of the class. These helper functions are intended to be like
322the event table macros that wxWindows employs. But since static event
323tables are impossible with wxPython, we use helpers that are named the
324same to dynamically build the table. The only real difference is
325that the first arguemnt to the event helpers is always the window that
326the event table entry should be added to.
2a47d3c1 327\item Notice the use of \tt{wxDLG\_PNT} and \tt{wxDLG\_SZE} in lines 19
06d20283
RD
328- 29 to convert from dialog units to pixels. These helpers are unique
329to wxPython since Python can't do method overloading like C++.
06d20283 330\item There is an \tt{OnCloseWindow} method at line 34 but no call to
2a47d3c1 331EVT\_CLOSE to attach the event to the method. Does it really get
f899db6d 332called? The answer is, yes it does. This is because many of the
06d20283
RD
333\em{standard} events are attached to windows that have the associated
334\em{standard} method names. I have tried to follow the lead of the
335C++ classes in this area to determine what is \em{standard} but since
336that changes from time to time I can make no guarentees, nor will it
2a47d3c1 337be fully documented. When in doubt, use an EVT\_*** function.
06d20283
RD
338\item At lines 17 to 21 notice that there are no saved references to
339the panel or the static text items that are created. Those of you
340who know Python might be wondering what happens when Python deletes
341these objects when they go out of scope. Do they disappear from the GUI? They
342don't. Remember that in wxPython the Python objects are just shadows of the
343coresponding C++ objects. Once the C++ windows and controls are
344attached to their parents, the parents manage them and delete them
345when necessary. For this reason, most wxPython objects do not need to
2a47d3c1 346have a \_\_del\_\_ method that explicitly causes the C++ object to be
06d20283
RD
347deleted. If you ever have the need to forcibly delete a window, use
348the Destroy() method as shown on line 36.
06d20283 349\item Just like wxWindows in C++, wxPython apps need to create a class
f899db6d 350derived from \tt{wxApp} (line 56) that implements a method named
06d20283
RD
351\tt{OnInit}, (line 59.) This method should create the application's
352main window (line 62) and use \tt{wxApp.SetTopWindow()} (line 66) to
353inform wxWindows about it.
06d20283
RD
354\item And finally, at line 72 an instance of the application class is
355created. At this point wxPython finishes initializing itself, and calls
356the \tt{OnInit} method to get things started. (The zero parameter here is
357a flag for functionality that isn't quite implemented yet. Just
358ignore it for now.) The call to \tt{MainLoop} at line 73 starts the event
359loop which continues until the application terminates or all the top
360level windows are closed.
06d20283
RD
361\end{enumerate}
362
06d20283
RD
363%----------------------------------------------------------------------
364\section{wxWindows classes implemented in wxPython}\label{wxpclasses}
365
366The following classes are supported in wxPython. Most provide nearly
367full implementations of the public interfaces specified in the C++
368documentation, others are less so. They will all be brought as close
369as possible to the C++ spec over time.
370
371\begin{itemize}\itemsep=0pt
372\item \helpref{wxAcceleratorEntry}{wxacceleratorentry}
373\item \helpref{wxAcceleratorTable}{wxacceleratortable}
374\item \helpref{wxActivateEvent}{wxactivateevent}
375\item \helpref{wxBitmapButton}{wxbitmapbutton}
376\item \helpref{wxBitmap}{wxbitmap}
f899db6d 377\item wxBMPHandler
06d20283
RD
378\item \helpref{wxBrush}{wxbrush}
379\item \helpref{wxButton}{wxbutton}
380\item \helpref{wxCalculateLayoutEvent}{wxcalculatelayoutevent}
381\item \helpref{wxCheckBox}{wxcheckbox}
382\item \helpref{wxCheckListBox}{wxchecklistbox}
383\item \helpref{wxChoice}{wxchoice}
384\item \helpref{wxClientDC}{wxclientdc}
385\item \helpref{wxCloseEvent}{wxcloseevent}
386\item \helpref{wxColourData}{wxcolourdata}
387\item \helpref{wxColourDialog}{wxcolourdialog}
388\item \helpref{wxColour}{wxcolour}
389\item \helpref{wxComboBox}{wxcombobox}
390\item \helpref{wxCommandEvent}{wxcommandevent}
391\item \helpref{wxConfig}{wxconfigbase}
392\item \helpref{wxControl}{wxcontrol}
393\item \helpref{wxCursor}{wxcursor}
394\item \helpref{wxDC}{wxdc}
395\item \helpref{wxDialog}{wxdialog}
396\item \helpref{wxDirDialog}{wxdirdialog}
397\item \helpref{wxDropFilesEvent}{wxdropfilesevent}
398\item \helpref{wxEraseEvent}{wxeraseevent}
399\item \helpref{wxEvent}{wxevent}
400\item \helpref{wxEvtHandler}{wxevthandler}
401\item \helpref{wxFileDialog}{wxfiledialog}
402\item \helpref{wxFocusEvent}{wxfocusevent}
403\item \helpref{wxFontData}{wxfontdata}
404\item \helpref{wxFontDialog}{wxfontdialog}
405\item \helpref{wxFont}{wxfont}
406\item \helpref{wxFrame}{wxframe}
407\item \helpref{wxGauge}{wxgauge}
f899db6d
RD
408\item wxGIFHandler
409\item wxGLCanvas
fd34e3a5
JS
410\item wxGridCell
411\item wxGridEvent
06d20283 412\item \helpref{wxGrid}{wxgrid}
fd34e3a5 413\item wxIconizeEvent
06d20283
RD
414\item \helpref{wxIcon}{wxicon}
415\item \helpref{wxIdleEvent}{wxidleevent}
f899db6d
RD
416\item \helpref{wxImage}{wximage}
417\item \helpref{wxImageHandler}{wximagehandler}
06d20283
RD
418\item \helpref{wxImageList}{wximagelist}
419\item \helpref{wxIndividualLayoutConstraint}{wxindividuallayoutconstraint}
420\item \helpref{wxInitDialogEvent}{wxinitdialogevent}
421\item \helpref{wxJoystickEvent}{wxjoystickevent}
f899db6d 422\item wxJPEGHandler
06d20283
RD
423\item \helpref{wxKeyEvent}{wxkeyevent}
424\item \helpref{wxLayoutAlgorithm}{wxlayoutalgorithm}
425\item \helpref{wxLayoutConstraints}{wxlayoutconstraints}
426\item \helpref{wxListBox}{wxlistbox}
427\item \helpref{wxListCtrl}{wxlistctrl}
428\item \helpref{wxListEvent}{wxlistevent}
21f280f4 429\item \helpref{wxListItem}{wxlistctrlsetitem}
06d20283
RD
430\item \helpref{wxMDIChildFrame}{wxmdichildframe}
431\item \helpref{wxMDIClientWindow}{wxmdiclientwindow}
432\item \helpref{wxMDIParentFrame}{wxmdiparentframe}
433\item \helpref{wxMask}{wxmask}
fd34e3a5 434\item wxMaximizeEvent
06d20283
RD
435\item \helpref{wxMemoryDC}{wxmemorydc}
436\item \helpref{wxMenuBar}{wxmenubar}
437\item \helpref{wxMenuEvent}{wxmenuevent}
438\item \helpref{wxMenuItem}{wxmenuitem}
439\item \helpref{wxMenu}{wxmenu}
440\item \helpref{wxMessageDialog}{wxmessagedialog}
441\item \helpref{wxMetaFileDC}{wxmetafiledc}
442\item \helpref{wxMiniFrame}{wxminiframe}
443\item \helpref{wxMouseEvent}{wxmouseevent}
444\item \helpref{wxMoveEvent}{wxmoveevent}
445\item \helpref{wxNotebookEvent}{wxnotebookevent}
446\item \helpref{wxNotebook}{wxnotebook}
7bcb11d3 447\item \helpref{wxPageSetupDialogData}{wxpagesetupdialogdata}
06d20283
RD
448\item \helpref{wxPageSetupDialog}{wxpagesetupdialog}
449\item \helpref{wxPaintDC}{wxpaintdc}
450\item \helpref{wxPaintEvent}{wxpaintevent}
451\item \helpref{wxPalette}{wxpalette}
452\item \helpref{wxPanel}{wxpanel}
453\item \helpref{wxPen}{wxpen}
f899db6d 454\item wxPNGHandler
06d20283
RD
455\item \helpref{wxPoint}{wxpoint}
456\item \helpref{wxPostScriptDC}{wxpostscriptdc}
2233e5b8 457\item \helpref{wxPreviewFrame}{wxpreviewframe}
06d20283 458\item \helpref{wxPrintData}{wxprintdata}
2233e5b8 459\item \helpref{wxPrintDialogData}{wxprintdialogdata}
06d20283 460\item \helpref{wxPrintDialog}{wxprintdialog}
2233e5b8
RD
461\item \helpref{wxPrinter}{wxprinter}
462\item \helpref{wxPrintPreview}{wxprintpreview}
06d20283 463\item \helpref{wxPrinterDC}{wxprinterdc}
2233e5b8 464\item \helpref{wxPrintout}{wxprintout}
06d20283
RD
465\item \helpref{wxQueryLayoutInfoEvent}{wxquerylayoutinfoevent}
466\item \helpref{wxRadioBox}{wxradiobox}
467\item \helpref{wxRadioButton}{wxradiobutton}
468\item \helpref{wxRealPoint}{wxrealpoint}
469\item \helpref{wxRect}{wxrect}
470\item \helpref{wxRegionIterator}{wxregioniterator}
471\item \helpref{wxRegion}{wxregion}
472\item \helpref{wxSashEvent}{wxsashevent}
473\item \helpref{wxSashLayoutWindow}{wxsashlayoutwindow}
474\item \helpref{wxSashWindow}{wxsashwindow}
475\item \helpref{wxScreenDC}{wxscreendc}
476\item \helpref{wxScrollBar}{wxscrollbar}
477\item \helpref{wxScrollEvent}{wxscrollevent}
478\item \helpref{wxScrolledWindow}{wxscrolledwindow}
fd34e3a5 479\item wxShowEvent
06d20283
RD
480\item \helpref{wxSingleChoiceDialog}{wxsinglechoicedialog}
481\item \helpref{wxSizeEvent}{wxsizeevent}
482\item \helpref{wxSize}{wxsize}
483\item \helpref{wxSlider}{wxslider}
484\item \helpref{wxSpinButton}{wxspinbutton}
fd34e3a5 485\item wxSpinEvent
06d20283
RD
486\item \helpref{wxSplitterWindow}{wxsplitterwindow}
487\item \helpref{wxStaticBitmap}{wxstaticbitmap}
488\item \helpref{wxStaticBox}{wxstaticbox}
2233e5b8 489\item wxStaticLine
06d20283
RD
490\item \helpref{wxStaticText}{wxstatictext}
491\item \helpref{wxStatusBar}{wxstatusbar}
492\item \helpref{wxSysColourChangedEvent}{wxsyscolourchangedevent}
493\item \helpref{wxTaskBarIcon}{wxtaskbaricon}
494\item \helpref{wxTextCtrl}{wxtextctrl}
495\item \helpref{wxTextEntryDialog}{wxtextentrydialog}
496\item \helpref{wxTimer}{wxtimer}
fd34e3a5 497\item wxToolBarTool
06d20283 498\item \helpref{wxToolBar}{wxtoolbar}
fd34e3a5 499\item wxToolTip
06d20283
RD
500\item \helpref{wxTreeCtrl}{wxtreectrl}
501\item \helpref{wxTreeEvent}{wxtreeevent}
502\item \helpref{wxTreeItemData}{wxtreeitemdata}
fd34e3a5 503\item wxTreeItemId
06d20283
RD
504\item \helpref{wxUpdateUIEvent}{wxupdateuievent}
505\item \helpref{wxWindowDC}{wxwindowdc}
506\item \helpref{wxWindow}{wxwindow}
2233e5b8
RD
507
508
06d20283
RD
509\end{itemize}
510
511%----------------------------------------------------------------------
512\section{Where to go for help}\label{wxphelp}
513
514Since wxPython is a blending of multiple technologies, help comes from
f899db6d 515multiple sources. See
06d20283
RD
516\urlref{http://alldunn.com/wxPython}{http://alldunn.com/wxPython} for details on
517various sources of help, but probably the best source is the
518wxPython-users mail list. You can view the archive or subscribe by
519going to
520
521\urlref{http://starship.python.net/mailman/listinfo/wxpython-users}{http://starship.python.net/mailman/listinfo/wxpython-users}
522
523Or you can send mail directly to the list using this address:
524
525wxpython-users@starship.python.net
526