X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/a98f98ac6f4422f259fc3324975156f7554adf41..dc484d491b15355285a89da275c58c2ef247d1f4:/docs/latex/wx/wxPython.tex?ds=inline diff --git a/docs/latex/wx/wxPython.tex b/docs/latex/wx/wxPython.tex index efba33ab20..f640eaddfa 100644 --- a/docs/latex/wx/wxPython.tex +++ b/docs/latex/wx/wxPython.tex @@ -1,14 +1,13 @@ -\chapter{wxPython Notes}\label{wxPython} +\section{wxPython overview}\label{wxpython} +%\setheader{{\it CHAPTER \thechapter}}{}{}{}{}{{\it CHAPTER \thechapter}}% +%\setfooter{\thepage}{}{}{}{}{\thepage}% -\setheader{{\it CHAPTER \thechapter}}{}{}{}{}{{\it CHAPTER \thechapter}}% -\setfooter{\thepage}{}{}{}{}{\thepage}% - -This addendum is written by Robin Dunn, author of the wxPython wrapper +This topic was written by Robin Dunn, author of the wxPython wrapper. %---------------------------------------------------------------------- -\section{What is wxPython?}\label{wxpwhat} +\subsection{What is wxPython?}\label{wxpwhat} -wxPython is a blending of the wxWindows GUI classes and the +wxPython is a blending of the wxWidgets GUI classes and the \urlref{Python}{http://www.python.org/} programming language. \wxheading{Python} @@ -34,13 +33,13 @@ commercial use. wxPython is a Python package that can be imported at runtime that includes a collection of Python modules and an extension module (native code). It provides a series of Python classes that mirror (or -shadow) many of the wxWindows GUI classes. This extension module -attempts to mirror the class heirarchy of wxWindows as closely as +shadow) many of the wxWidgets GUI classes. This extension module +attempts to mirror the class hierarchy of wxWidgets as closely as possible. This means that there is a wxFrame class in wxPython that looks, smells, tastes and acts almost the same as the wxFrame class in the C++ version. -wxPython is very versitile. It can be used to create standalone GUI +wxPython is very versatile. It can be used to create standalone GUI applications, or in situations where Python is embedded in a C++ application as an internal scripting or macro language. @@ -50,30 +49,30 @@ website \urlref{http://wxPython.org/}{http://wxPython.org/} for details about getting wxPython working for you. %---------------------------------------------------------------------- -\section{Why use wxPython?}\label{wxpwhy} +\subsection{Why use wxPython?}\label{wxpwhy} -So why would you want to use wxPython over just C++ and wxWindows? +So why would you want to use wxPython over just C++ and wxWidgets? Personally I prefer using Python for everything. I only use C++ when I -absolutely have to eek more performance out of an algorithm, and even +absolutely have to eke more performance out of an algorithm, and even then I usually code it as an extension module and leave the majority of the program in Python. Another good thing to use wxPython for is quick prototyping of your -wxWindows apps. With C++ you have to continuously go though the +wxWidgets apps. With C++ you have to continuously go though the edit-compile-link-run cycle, which can be quite time consuming. With Python it is only an edit-run cycle. You can easily build an application in a few hours with Python that would normally take a few -days or longer with C++. Converting a wxPython app to a C++/wxWindows app +days or longer with C++. Converting a wxPython app to a C++/wxWidgets app should be a straight forward task. %---------------------------------------------------------------------- -\section{Other Python GUIs}\label{wxpother} +\subsection{Other Python GUIs}\label{wxpother} There are other GUI solutions out there for Python. \wxheading{Tkinter} -Tkinter is the defacto standard GUI for Python. It is available +Tkinter is the de facto 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... @@ -116,15 +115,14 @@ wrappers around some C or C++ toolkit or another, and most are not cross-platform compatible. See \urlref{this link}{http://www.python.org/download/Contributed.html\#Graphics} for a listing of a few of them. - %---------------------------------------------------------------------- -\section{Using wxPython}\label{wxpusing} +\subsection{Using wxPython}\label{wxpusing} \wxheading{First things first...} I'm not going to try and teach the Python language here. You can do that at the \urlref{Python Tutorial}{http://www.python.org/doc/tut/tut.html}. -I'm also going to assume that you know a bit about wxWindows already, +I'm also going to assume that you know a bit about wxWidgets already, enough to notice the similarities in the classes used. Take a look at the following wxPython program. You can find a similar @@ -193,17 +191,17 @@ it by issuing this command: 052: self.posCtrl.SetValue("%s, %s" % (pos.x, pos.y)) 053: 054: -055: # Every wxWindows application must have a class derived from wxApp +055: # Every wxWidgets application must have a class derived from wxApp 056: class MyApp(wxApp): 057: -058: # wxWindows calls this method to initialize the application +058: # wxWidgets calls this method to initialize the application 059: def OnInit(self): 060: 061: # Create an instance of our customized Frame class 062: frame = MyFrame(NULL, -1, "This is a test") 063: frame.Show(true) 064: -065: # Tell wxWindows that this is our main window +065: # Tell wxWidgets that this is our main window 066: self.SetTopWindow(frame) 067: 068: # Return a success flag @@ -226,7 +224,7 @@ then access all the wxPython identifiers through the wx module, for example, "{\tt wx.wxFrame}". \item At line 13 the frame's sizing and moving events are connected to methods of the class. These helper functions are intended to be like -the event table macros that wxWindows employs. But since static event +the event table macros that wxWidgets employs. But since static event tables are impossible with wxPython, we use helpers that are named the same to dynamically build the table. The only real difference is that the first argument to the event helpers is always the window that @@ -253,11 +251,11 @@ when necessary. For this reason, most wxPython objects do not need to have a \_\_del\_\_ method that explicitly causes the C++ object to be deleted. If you ever have the need to forcibly delete a window, use the Destroy() method as shown on line 36. -\item Just like wxWindows in C++, wxPython apps need to create a class +\item Just like wxWidgets in C++, wxPython apps need to create a class derived from {\tt wxApp} (line 56) that implements a method named {\tt OnInit}, (line 59.) This method should create the application's main window (line 62) and use {\tt wxApp.SetTopWindow()} (line 66) to -inform wxWindows about it. +inform wxWidgets about it. \item And finally, at line 72 an instance of the application class is created. At this point wxPython finishes initializing itself, and calls the {\tt OnInit} method to get things started. (The zero parameter here is @@ -268,7 +266,7 @@ level windows are closed. \end{enumerate} %---------------------------------------------------------------------- -\section{wxWindows classes implemented in wxPython}\label{wxpclasses} +\subsection{wxWidgets classes implemented in wxPython}\label{wxpclasses} The following classes are supported in wxPython. Most provide nearly full implementations of the public interfaces specified in the C++ @@ -290,7 +288,7 @@ as possible to the C++ spec over time. \item \helpref{wxButton}{wxbutton} \item \helpref{wxCalculateLayoutEvent}{wxcalculatelayoutevent} \item \helpref{wxCalendarCtrl}{wxcalendarctrl} -\item wxCaret +\item \helpref{wxCaret}{wxcaret} \item \helpref{wxCheckBox}{wxcheckbox} \item \helpref{wxCheckListBox}{wxchecklistbox} \item \helpref{wxChoice}{wxchoice} @@ -322,7 +320,7 @@ as possible to the C++ spec over time. \item \helpref{wxEraseEvent}{wxeraseevent} \item \helpref{wxEvent}{wxevent} \item \helpref{wxEvtHandler}{wxevthandler} -\item wxFileConfig +\item \helpref{wxFileConfig}{wxfileconfig} \item \helpref{wxFileDataObject}{wxfiledataobject} \item \helpref{wxFileDialog}{wxfiledialog} \item \helpref{wxFileDropTarget}{wxfiledroptarget} @@ -336,10 +334,10 @@ as possible to the C++ spec over time. \item \helpref{wxFSFile}{wxfsfile} \item \helpref{wxGauge}{wxgauge} \item wxGIFHandler -\item wxGLCanvas +\item \helpref{wxGLCanvas}{wxglcanvas} \begin{comment} \item wxGridCell -\item wxGridEvent +\item \helpref{wxGridEvent}{wxgridevent} \item \helpref{wxGrid}{wxgrid} \end{comment} \item \helpref{wxHtmlCell}{wxhtmlcell} @@ -353,7 +351,7 @@ as possible to the C++ spec over time. \item \helpref{wxHtmlPrintout}{wxhtmlprintout} \item \helpref{wxHtmlWinTagHandler}{wxhtmlwintaghandler} \item \helpref{wxHtmlWindow}{wxhtmlwindow} -\item wxIconizeEvent +\item \helpref{wxIconizeEvent}{wxiconizeevent} \item \helpref{wxIcon}{wxicon} \item \helpref{wxIdleEvent}{wxidleevent} \item \helpref{wxImage}{wximage} @@ -373,7 +371,7 @@ as possible to the C++ spec over time. \item \helpref{wxListEvent}{wxlistevent} \item \helpref{wxListItem}{wxlistctrlsetitem} \item \helpref{wxMask}{wxmask} -\item wxMaximizeEvent +\item \helpref{wxMaximizeEvent}{wxmaximizeevent} \item \helpref{wxMDIChildFrame}{wxmdichildframe} \item \helpref{wxMDIClientWindow}{wxmdiclientwindow} \item \helpref{wxMDIParentFrame}{wxmdiparentframe} @@ -429,10 +427,10 @@ as possible to the C++ spec over time. \item \helpref{wxSizeEvent}{wxsizeevent} \item \helpref{wxSize}{wxsize} \item \helpref{wxSizer}{wxsizer} -\item wxSizerItem +\item \helpref{wxSizerItem}{wxsizeritem} \item \helpref{wxSlider}{wxslider} \item \helpref{wxSpinButton}{wxspinbutton} -\item wxSpinEvent +\item \helpref{wxSpinEvent}{wxspinevent} \item \helpref{wxSplitterWindow}{wxsplitterwindow} \item \helpref{wxStaticBitmap}{wxstaticbitmap} \item \helpref{wxStaticBox}{wxstaticbox} @@ -452,7 +450,7 @@ as possible to the C++ spec over time. \item \helpref{wxTipProvider}{wxtipprovider} \item wxToolBarTool \item \helpref{wxToolBar}{wxtoolbar} -\item wxToolTip +\item \helpref{wxToolTip}{wxtooltip} \item \helpref{wxTreeCtrl}{wxtreectrl} \item \helpref{wxTreeEvent}{wxtreeevent} \item \helpref{wxTreeItemData}{wxtreeitemdata} @@ -465,7 +463,7 @@ as possible to the C++ spec over time. \end{itemize} %---------------------------------------------------------------------- -\section{Where to go for help}\label{wxphelp} +\subsection{Where to go for help}\label{wxphelp} Since wxPython is a blending of multiple technologies, help comes from multiple sources. See @@ -474,10 +472,9 @@ various sources of help, but probably the best source is the wxPython-users mail list. You can view the archive or subscribe by going to -\urlref{http://lists.sourceforge.net/mailman/listinfo/wxpython-users}{http://lists.sourceforge.net/mailman/listinfo/wxpython-users} +\urlref{http://lists.wxwindows.org/mailman/listinfo/wxpython-users}{http://lists.wxwindows.org/mailman/listinfo/wxpython-users} Or you can send mail directly to the list using this address: -wxpython-users@lists.sourceforge.net - +wxpython-users@lists.wxwindows.org