<body>
<div class="document" id="building-wxpython-2-5-for-development-and-testing">
<h1 class="title">Building wxPython 2.5 for Development and Testing</h1>
-<p>This file describes how I build wxWindows and wxPython while doing
+<p>This file describes how I build wxWidgets and wxPython while doing
development and testing, and is meant to help other people that want
to do the same thing. I'll assume that you are using either a CVS
-snapshot from <a class="reference" href="http://wxwindows.org/snapshots/">http://wxwindows.org/snapshots/</a>, a checkout from CVS, or
+snapshot from <a class="reference" href="http://wxWidgets.org/snapshots/">http://wxWidgets.org/snapshots/</a>, a checkout from CVS, or
one of the released wxPythonSrc-2.5.* tarballs. I'll also assume that
you know your way around your system, the compiler, etc. and most
importantly, that you know what you are doing! ;-)</p>
<h1><a name="building-on-unix-like-systems-e-g-linux-and-os-x">Building on Unix-like Systems (e.g. Linux and OS X)</a></h1>
<p>These platforms are built almost the same way while in development
so I'll combine the descriptions about their build process here.
-First we will build wxWindows and install it to an out of the way
+First we will build wxWidgets and install it to an out of the way
place, then do the same for wxPython.</p>
<ol class="arabic">
-<li><p class="first">Create a build directory in the main wxWindows dir, and configure
-wxWindows. If you want to have multiple builds with different
+<li><p class="first">Create a build directory in the main wxWidgets dir, and configure
+wxWidgets. If you want to have multiple builds with different
configure options, just use different subdirectories. I normally
put the configure command in a script named ".configure" in each
build dir so I can easily blow away everything in the build dir and
--disable-monolithic \
--enable-debug \
--enable-geometry \
+ --enable-sound --with-sdl \
+ --enable-display \
</pre>
<p>On OS X of course you'll want to use --with-mac instead of
--with-gtk. For GTK2 and unicode add:</p>
-<blockquote>
-<p>--enable-gtk2 --enable-unicode </p>
-</blockquote>
+<pre class="literal-block">
+--enable-gtk2 \
+--enable-unicode \
+</pre>
<p>Notice that I used a prefix of /opt/wx/2.5. You can use whatever
path you want, such as a path in your HOME dir or even one of the
standard prefix paths such as /usr or /usr/local if you like, but
using /opt this way lets me easily have multiple versions and ports
-of wxWindows "installed" and makes it easy to switch between them,
-without impacting any versions of wxWindows that may have been
+of wxWidgets "installed" and makes it easy to switch between them,
+without impacting any versions of wxWidgets that may have been
installed via an RPM or whatever. For the rest of the steps below
be sure to also substitute "/opt/wx/2.5" with whatever prefix you
choose for your build.</p>
<p>If you want to use the image and zlib libraries included with
-wxWindows instead of those already installed on your system, (for
+wxWidgets instead of those already installed on your system, (for
example, to reduce dependencies on 3rd party libraries) then you
can add these flags to the configure command:</p>
<pre class="literal-block">
--with-zlib=builtin \
</pre>
</li>
-<li><p class="first">To build and install wxWindows you could just use the "make"
-command but there are other libraries besides the main wxWindows
+<li><p class="first">To build and install wxWidgets you could just use the "make"
+command but there are other libraries besides the main wxWidgets
libs that also need to be built so again I make a script to do it
all for me so I don't forget anything. This time it is called
".make" (I use the leading ". so when I do <tt class="literal"><span class="pre">rm</span> <span class="pre">-r</span> <span class="pre">*</span></tt> in my build
.make install
</pre>
<p>When it's done you should have an installed set of files under
-/opt/wx/2.5 containing just wxWindows. Now to use this version of
-wxWindows you just need to add /opt/wx/2.5/bin to the PATH and set
+/opt/wx/2.5 containing just wxWidgets. Now to use this version of
+wxWidgets you just need to add /opt/wx/2.5/bin to the PATH and set
LD_LIBRARY_PATH (or DYLD_LIBRARY_PATH on OS X) to /opt/wx/2.5/lib.</p>
</li>
<li><p class="first">I also have a script to help me build wxPython and it is checked in
-to the CVS as wxWindows/wxPython/b, but probably don't want to use
+to the CVS as wxWidgets/wxPython/b, but probably don't want to use
it as it's very cryptic and expects that you want to run SWIG, so
if you don't have the latest patched up version of SWIG then you'll
probably get stuck. So I'll just give the raw commands instead.</p>
wxPython programs to run the setup.py commands below. I'll be
using python2.3.</p>
<p>Make sure that the first wx-config found on the PATH is the one you
-installed above, and then change to the wxWindows/wxPython dir and
+installed above, and then change to the wxWidgets/wxPython dir and
run the this command:</p>
<pre class="literal-block">
cd wxPython
setup.py command line to disable the building of the glcanvas
module.</p>
<p>When the setup.py command is done you should have fully populated
-wxPython and wx packages locally in wxWindows/wxPython/wxPython and
+wxPython and wx packages locally in wxWidgets/wxPython/wxPython and
.../wx, with all the extension modules (<tt class="literal"><span class="pre">*.so</span></tt> files) located in the
wx package.</p>
</li>
PYTHONPATH to the wxPython dir in the CVS tree. For example:</p>
<pre class="literal-block">
export LD_LIBRARY=/opt/wx/2.5/lib
-export PYTHONPATH=/myprojects/wxWindows/wxPython
-cd /myprojects/wxWindows/wxPython/demo
+export PYTHONPATH=/myprojects/wxWidgets/wxPython
+cd /myprojects/wxWidgets/wxPython/demo
python2.3 demo.py
</pre>
<p>OS X NOTE: You need to use "pythonw" on the command line to run
used. The Python executable that comes from PythonLabs and the
wxPython extensions that I distribute are built with MSVC 6 with all
the Service Packs applied.</p>
-<p>If you want to build a debugable version of wxWindows and wxPython you
+<p>If you want to build a debugable version of wxWidgets and wxPython you
will need to have also built a debug version of Python and any other
extension modules you need to use. You can tell if you have them
already if there is a _d in the file names, for example python_d.exe
version is fine, and you can use the regular python executables with
it.</p>
<p>Just like the unix versions I also use some scripts to help me build
-wxWindows, but I use some non-standard stuff to do it. So if you want
+wxWidgets, but I use some non-standard stuff to do it. So if you want
to use them too you'll need to get a copy or 4DOS or 4NT from
<a class="reference" href="http://www.jpsoft.com/">http://www.jpsoft.com/</a> and also a copy of unix-like cat and sed
programs. You can also do by hand what my scripts are doing, but
there are a lof steps involved and I won't be going into details
-here. There is a copy of my build scripts in wxWindowswxPythondistribmsw</p>
+here. There is a copy of my build scripts in wxWidgetswxPythondistribmsw</p>
<ol class="arabic">
-<li><p class="first">Set an environment variable to the root of the wxWindows source
+<li><p class="first">Set an environment variable to the root of the wxWidgets source
tree:</p>
<pre class="literal-block">
-set WXWIN=e:\projects\wxWindows
+set WXWIN=e:\projects\wxWidgets
</pre>
</li>
<li><p class="first">Copy setup0.h to setup.h</p>
wxUSE_GLCANVAS 1
wxUSE_POSTSCRIPT 1
wxUSE_AFM_FOR_POSTSCRIPT 0
+wxUSE_DISPLAY 1
</pre>
</li>
<li><p class="first">Make a %WXWIN%BIN directory and add it to the PATH. My build
-scripts will copy the wxWindows DLLs there.</p>
+scripts will copy the wxWidgets DLLs there.</p>
</li>
<li><p class="first">Change to the %WXWIN%buildmsw directory and copy my build scripts
there.</p>
</li>
-<li><p class="first">Use the .make.btm command to build wxWindows. It needs one
+<li><p class="first">Use the .make.btm command to build wxWidgets. It needs one
command-line parameter which controls what kind of build(s) to do.
Use one of the following:</p>
<pre class="literal-block">
.make hybrid clean
</pre>
</li>
-<li><p class="first">When that is done it will have built the main wxWindows DLLs and
+<li><p class="first">When that is done it will have built the main wxWidgets DLLs and
also some of the contribs DLLs. There should be a ton of DLLs in
%WXDIR%bin and lots of lib files and other stuff in
%WXDIR%libvc_dll.</p>
with this version when you want to, and use the installed release
version the rest of the time. If you ever do want to install the
development verison please refer to INSTALL.txt.</p>
-<p>Change to the wxWindowswxPython dir and run the this command,
+<p>Change to the wxWidgetswxPython dir and run the this command,
makeing sure that you use the version of python that you want to
build for (if you have more than one on your system):</p>
<pre class="literal-block">
<pre class="literal-block">
USE_SWIG=1 SWIG=e:\projects\SWIG-cvs\swig.exe
</pre>
-<p>If you built a Unicode version of wxWindows and want to also build
+<p>If you built a Unicode version of wxWidgets and want to also build
the Unicode version of wxPython then add this flag:</p>
<pre class="literal-block">
UNICODE=1
</pre>
-<p>If you have a debug version of Python and wxWindows and want to
+<p>If you have a debug version of Python and wxWidgets and want to
build a debug version of wxPython too, add the --debug flag to the
command line. You should then end up with a set of <tt class="literal"><span class="pre">*_d.pyd</span></tt>
files in the wx package and you'll have to run <tt class="literal"><span class="pre">python_d.exe</span></tt> to
use them. The debug and hybrid(release) versions can coexist.</p>
<p>When the setup.py command is done you should have fully populated
-wxPython and wx packages locally in wxWindows/wxPython/wxPython and
-wxWindows/wxPython/wx, with all the extension modules (<tt class="literal"><span class="pre">*.pyd</span></tt>
+wxPython and wx packages locally in wxWidgets/wxPython/wxPython and
+wxWidgets/wxPython/wx, with all the extension modules (<tt class="literal"><span class="pre">*.pyd</span></tt>
files) located in the wx package.</p>
</li>
<li><p class="first">To run code with the development verison of wxPython, just set the
PYTHONPATH to the wxPython dir in the CVS tree. For example:</p>
<pre class="literal-block">
-set PYTHONPATH=e:\projects\wxWindows\wxPython
-cd e:\projects\wxWindows\wxPython
+set PYTHONPATH=e:\projects\wxWidgets\wxPython
+cd e:\projects\wxWidgets\wxPython
python demo.py
</pre>
</li>
</div>
<hr class="footer" />
<div class="footer">
-Generated on: 2004-02-27 00:27 UTC.
+Generated on: 2004-03-12 19:55 UTC.
</div>
</body>
</html>
<body>
<div class="document" id="changes-txt-for-wxpython">
<h1 class="title">CHANGES.txt for wxPython</h1>
-<div class="section" id="x">
-<h1><a name="x">2.5.1.x</a></h1>
+<div class="section" id="id1">
+<h1><a name="id1">2.5.1.1</a></h1>
<p>(See also the MigrationGuide.txt file for details about some of the
big changes that have happened in this release and how you should
adapt your code.)</p>
+<p>The wxWindows project and library is now known as wxWidgets. Please
+see <a class="reference" href="http://www.wxwindows.org/name.htm">http://www.wxwindows.org/name.htm</a> for more details. This won't
+really affect wxPython all that much, other than the fact that the
+wxwindows.org domain name will be changing to wxwidgets.org, so mail
+list, CVS, and etc. addresses will be changing. We're going to try
+and smooth the transition as much as possible, but I wanted you all to
+be aware of this change if you run into any issues.</p>
<p>Many, many little fixes, changes and additions done as part of the move
-to wxWindows 2.5 that I have forgotten about.</p>
+to wxWidgets 2.5 that I have forgotten about.</p>
<p>Added wxMirrorDC.</p>
<p>Added wxIconLocation</p>
-<p>Added Python wrappers for the new wxVScrolledWindow, wxVListBox, and
-wxHtmlListBox classes.</p>
+<p>Added Python wrappers and demos for the new wxVScrolledWindow,
+wxVListBox, and wxHtmlListBox classes.</p>
<p>Added wrappers for wxBookCtrl and wxListbook. wxNotebook now derives
from wxBookCtrl.</p>
<p>Added Gordon Williams' PyPlot module to the library, available as the
<p>I made a small but important change in the code that aquires the
Python Global Interpreter Lock to try and prevent deadlocks that can
happen when there are nested attempts to aquire the GIL.</p>
-<p>The RPMs will now install menu items on Mandrake in
-Applications/Development/Tools for PyCrust, XRCed, etc. They are also
-installing icons and <tt class="literal"><span class="pre">*.desktop</span></tt> items in the generic KDE and GNOME
-locations, but I don't know yet if they are resulting in menu items on
-non-Mandrake systems. (It didn't automatically do it on my RH-9 build
-box but I didn't chase it very far...) If you have ideas for how to
-improve the .spec file to work better and/or on more distros please
-send me a patch.</p>
-<p>The RPMs are now built on a RH-9 box, and I have tested installing
-them also on my main Mandrake 9.2 box.</p>
+<p>The RPMs will now install menu items on Mandrake Linux in
+Applications/Development/Tools for PyCrust, XRCed, etc. The RPMs are
+also installing icons and <tt class="literal"><span class="pre">*.desktop</span></tt> items in the generic KDE and
+GNOME locations, but I don't know yet if they are resulting in menu
+items on non-Mandrake systems. (It didn't automatically do it on my
+RH-9 build box but I didn't chase it very far...) If you have ideas
+for how to improve the .spec file to work better and/or on more
+distros please send me a patch.</p>
+<p>The RPMs are now built on a fairly generic RH-9 box, and I have tested
+installing them also on my main Mandrake 9.2 box.</p>
<p>There are some big changes in the OS X disk image. The actual
Installer package now <em>only</em> installs the wxMac dynlibs, wxPython
-extension modules and pacakges, and also the command-line tool
+extension modules and Python pacakges, and also the command-line tool
scripts. The remaining items (demo, samples, and application bundles
for the Demo, PyCrust and XRCed) are now top-level items in the disk
image (.dmg file) that users can just drag and drop to wherever they
different API.</p>
<p>Updated the AnalogClockWindow with many enhancements from E. A. Tacão.</p>
<p>wxMac now has wx.ToggleButton!</p>
-<p>wx.stc.StyledTextCtrl has been update to version 1.58 of Scintilla.</p>
+<p>wx.stc.StyledTextCtrl has been updated to version 1.58 of Scintilla.</p>
<p>To help with the wx.stc.StyledTextCtrl performance issues on wxMac
-I've added a SetUseAntiAliasing method (and GetUseAntiAliasing) too
+I've added a SetUseAntiAliasing method (and GetUseAntiAliasing too)
that will turn off the use of antialiased fonts in the wxSTC, allowing
it to bypass the slow text measuring routines and use the fast and
-simple one instead. By default the setting is turned off. When run
-on OSX The Py* apps have a new item on the Options menu for
-controlling this setting if you would like to experiment with it.</p>
+simple one instead. By default the setting is turned off (on wxMac
+only.) When run on OSX the Py* apps have a new item on the Options
+menu for controlling this setting if you would like to experiment with
+it.</p>
+<p>Updated wx.lib.calendar with many fixes and enhancements from Joerg
+"Adi" Sieker.</p>
+<p>Added wx.Display and wx.VideoMode.</p>
+<p>AppleEvents can be handled by overriding wx.App methods MacOpenFile,
+MacPrintFile, MacNewFile, and MacReopenApp.</p>
+<p>Added wx.PlatformInfo which is a tuple containing strings that
+describe the platform and build options of wxPython. See the
+MigrationGuide for more details.</p>
</div>
-<div class="section" id="id1">
-<h1><a name="id1">2.4.2.4</a></h1>
+<div class="section" id="id2">
+<h1><a name="id2">2.4.2.4</a></h1>
<p>Use wxSTC in the demo for displaying the soucre code of the samples.</p>
<p>Lots of bug fixes and such from the wxWindows folks.</p>
<p>Added wxPython.lib.newevent from Miki Tebeka. Its usage is
<p>Added wxMaskedNumCtrl.</p>
<p>Added Chris Barker's FloatCanvas.</p>
</div>
-<div class="section" id="id2">
-<h1><a name="id2">2.4.1.2</a></h1>
+<div class="section" id="id3">
+<h1><a name="id3">2.4.1.2</a></h1>
<p>Added wxScrolledPanel from Will Sadkin</p>
<p>Added SetShape method to top level windows (e.g. wxFrame.)</p>
<p>Changed wxSWIG to not generate Python code using apply, (since it will
and Spacers can be specified with a wxSize (or 2-tuple) parameter</p>
<p>Added wxCursorFromBits.</p>
</div>
-<div class="section" id="id3">
-<h1><a name="id3">2.4.0.7</a></h1>
+<div class="section" id="id4">
+<h1><a name="id4">2.4.0.7</a></h1>
<p>Gave up on generating a warning upon the use of the old true/false or
TRUE/FALSE values.</p>
<p>Fixed wxGenericTreeCtrl (used on wxGTK and wxMac for wxTreeCtrl) so
<p>Updated pycolourchooser.</p>
<p>Updated to 0.9b of PyCrust.</p>
</div>
-<div class="section" id="id4">
-<h1><a name="id4">2.4.0.4</a></h1>
+<div class="section" id="id5">
+<h1><a name="id5">2.4.0.4</a></h1>
<p>Added missing wxRect methods</p>
<p>Add OOR support for wxApp objects too.</p>
<p>Added wxCursorFromImage, which works on wxMSW and wxGTK so far.</p>
<p>Fixed typemaps for wxGridCellCoordsArray.</p>
<p>Updated to the 0.9a version of PyCrust</p>
</div>
-<div class="section" id="id5">
-<h1><a name="id5">2.4.0.2</a></h1>
+<div class="section" id="id6">
+<h1><a name="id6">2.4.0.2</a></h1>
<p>Several bug fixes.</p>
<p>Added wxIntCtrl from Will Sadkin.</p>
<p>Added wxPyColourChooser by Michael Gilfix.</p>
</div>
-<div class="section" id="id6">
-<h1><a name="id6">2.4.0.1</a></h1>
+<div class="section" id="id7">
+<h1><a name="id7">2.4.0.1</a></h1>
<p>No major new features since 2.3.4.2, mostly bug fixes and minor
enhancements.</p>
<p>Added function wrappers for the common dialogs from Kevin Altis. See
wxPython/lib/dialogs.py for more details.</p>
</div>
-<div class="section" id="id7">
-<h1><a name="id7">2.3.4.2</a></h1>
+<div class="section" id="id8">
+<h1><a name="id8">2.3.4.2</a></h1>
<p>Various bug fixes.</p>
</div>
-<div class="section" id="id8">
-<h1><a name="id8">2.3.4.1</a></h1>
+<div class="section" id="id9">
+<h1><a name="id9">2.3.4.1</a></h1>
<p>Updated XRCed and wxTimeCtrl contribs.</p>
<p>Show a couple new wxGrid features in the demo.</p>
<p>Several bug fixes in wxWindows.</p>
HTMLHelp viewer does. Changed how the wxPythonDocs tarball is built
and added a script to launch the doc viewer.</p>
</div>
-<div class="section" id="id9">
-<h1><a name="id9">2.3.3.1</a></h1>
+<div class="section" id="id10">
+<h1><a name="id10">2.3.3.1</a></h1>
<p>Added wxSplashScreen.</p>
<p>Added wxGenericDirCtrl.</p>
<p>Added wxMultiChoiceDialog.</p>
<p>Added wxPython.lib.mixins.rubberband module from Robb Shecter.</p>
<p>Added wxTimeCtrl from Will Sadkin.</p>
</div>
-<div class="section" id="id10">
-<h1><a name="id10">2.3.2.1</a></h1>
+<div class="section" id="id11">
+<h1><a name="id11">2.3.2.1</a></h1>
<p>Changed (again) how the Python global interpreter lock is handled as
well as the Python thread state. This time it works on SMP machines
without barfing and is also still compatible with Python debuggers.</p>
<p>Added some patches from library contributors.</p>
</div>
-<div class="section" id="id11">
-<h1><a name="id11">2.3.2</a></h1>
+<div class="section" id="id12">
+<h1><a name="id12">2.3.2</a></h1>
<p>Added EVT_HELP, EVT_HELP_RANGE, EVT_DETAILED_HELP,
EVT_DETAILED_HELP_RANGE, EVT_CONTEXT_MENU, wxHelpEvent,
wxContextMenuEvent, wxContextHelp, wxContextHelpButton, wxTipWindow,
wxPython/contrib/dllwidget and wxPython/demo/dllwidget for more
details.</p>
</div>
-<div class="section" id="id12">
-<h1><a name="id12">2.3.1</a></h1>
+<div class="section" id="id13">
+<h1><a name="id13">2.3.1</a></h1>
<p>Added EVT_GRID_EDITOR_CREATED and wxGridEditorCreatedEvent so the user
code can get access to the edit control when it is created, (to push
on a custom event handler for example.)</p>
<p>Fixed img2py to work correctly with Python 2.1.</p>
<p>Added enhanced wxVTKRenderWindow by Prabhu Ramachandran</p>
</div>
-<div class="section" id="id13">
-<h1><a name="id13">2.3.0</a></h1>
+<div class="section" id="id14">
+<h1><a name="id14">2.3.0</a></h1>
<p>Removed initial startup dependency on the OpenGL DLLs so only the
glcanvasc.pyd depends on them, (on wxMSW.)</p>
<p>Changed wxFont, wxPen, wxBrush to not implicitly use the
by having smaller functional apps to play with. They can be found in
wxPython/samples.</p>
</div>
-<div class="section" id="id14">
-<h1><a name="id14">2.2.6</a></h1>
+<div class="section" id="id15">
+<h1><a name="id15">2.2.6</a></h1>
<p>No changes happened in the Python wrappers for this release, only
changes and fixes in the wxWindows library.</p>
</div>
-<div class="section" id="id15">
-<h1><a name="id15">2.2.5</a></h1>
+<div class="section" id="id16">
+<h1><a name="id16">2.2.5</a></h1>
<p>New typemaps for wxString when compiling for Python 2.0 and beyond
that allow Unicode objects to be passed as well as String objects. If
a Unicode object is passed PyString_AsStringAndSize is used to convert
</div>
<hr class="footer" />
<div class="footer">
-Generated on: 2004-02-27 00:27 UTC.
+Generated on: 2004-03-12 19:55 UTC.
</div>
</body>
</html>
<div class="section" id="installing-on-unix-like-systems-not-os-x">
<h1><a name="installing-on-unix-like-systems-not-os-x">Installing on Unix-like Systems (not OS X)</a></h1>
<ol class="arabic">
-<li><p class="first">When building wxWindows you need to decide if you want it to be a
+<li><p class="first">When building wxWidgets you need to decide if you want it to be a
private copy only accessed by wxPython, or if you would like it to
be installed in a stanard location such as /usr. Or perhaps you
-already have a version of wxWindows installed on your system (such
+already have a version of wxWidgets installed on your system (such
as from an RPM) and you want wxPython to use that version too. If
so then you'll want to ensure that the flags and options used to
build the installed version are compatible with wxPython.</p>
</li>
-<li><p class="first">If you do decide to build and install your own wxWindows then there
+<li><p class="first">If you do decide to build and install your own wxWidgets then there
are a few tweaks to the configure flags described in BUILD.txt that
you will probably want to make. Instead of --enable-debug use
this configure flag:</p>
<pre class="literal-block">
--enable-optimize \
</pre>
-<p>Normally I also use the following flag in order to have wxWindows
+<p>Normally I also use the following flag in order to have wxWidgets
runtime assertions turned into Python exceptions where possible.
It does add extra code to the build but probably not enough to
worry about it. However if you want to get as lean a build as
<blockquote>
<p>--enable-debug_flag </p>
</blockquote>
-<p>If you are building a private copy of wxWindows (IOW, not installed
+<p>If you are building a private copy of wxWidgets (IOW, not installed
in a standard library location) then it can be kind of a hassle to
always have to set the LD_LIBRARY_PATH variable so wxPython can
-find the wxWindows shared libraries. You can hard code the library
+find the wxWidgets shared libraries. You can hard code the library
path into the binaries by using the rpath option when configuring
-wxWindows. For example:</p>
+wxWidgets. For example:</p>
<pre class="literal-block">
--enable-rpath=/opt/wx/2.5/lib \
</pre>
instructions above, except for a few small, but important details:</p>
<ol class="arabic simple">
<li>The --enable-rpath configure option is not needed since the path to
-the wxWindows dylibs will automatically be encoded into the
+the wxWidgets dylibs will automatically be encoded into the
extension modules when they are built. If you end up moving the
-wxWindows dynlibs to some other location (such as inside the .app
+wxWidgets dynlibs to some other location (such as inside the .app
bundle of your applicaiton for distribution to other users,) then
you will need to set DYLD_LIBRARY_PATH to this location so the
dylibs can be found at runtime.</li>
<div class="section" id="installing-on-windows">
<h1><a name="installing-on-windows">Installing on Windows</a></h1>
<ol class="arabic">
-<li><p class="first">Build wxWindows and wxPython as described in BUILD.txt. If you
+<li><p class="first">Build wxWidgets and wxPython as described in BUILD.txt. If you
would rather have a version without the code that turns runtime
assertions into Python exceptions, then use "release" instead of
-"hybrid" when building wxWindows and add "FINAL=1" to the setup.py
+"hybrid" when building wxWidgets and add "FINAL=1" to the setup.py
command line.</p>
</li>
<li><p class="first">Install wxPython like this:</p>
python setup.py install
</pre>
</li>
-<li><p class="first">Copy the wxWindows DLLs to the wx package directory so they can be
+<li><p class="first">Copy the wxWidgets DLLs to the wx package directory so they can be
found at runtime by the extension modules without requiring that
they be installed on the PATH:</p>
<pre class="literal-block">
</div>
<hr class="footer" />
<div class="footer">
-Generated on: 2004-02-27 00:27 UTC.
+Generated on: 2004-03-12 19:55 UTC.
</div>
</body>
</html>
<div class="section" id="wxname-change">
<h1><a name="wxname-change">wxName Change</a></h1>
<p>The <strong>wxWindows</strong> project and library is now known as
-<strong>wxWidgets</strong>. Please see <a class="reference" href="http://lists.wxwidgets.org/cgi-bin/ezmlm-cgi?13:mss:3:200402:eebaopdhchfoagmnideo">here</a> for more details.</p>
+<strong>wxWidgets</strong>. Please see <a class="reference" href="http://www.wxwindows.org/name.htm">here</a> for more details.</p>
<p>This won't really affect wxPython all that much, other than the fact
that the wxwindows.org domain name will be changing to wxwidgets.org,
so mail list, CVS, and etc. addresses will be changing. We're going
<div class="section" id="module-initialization">
<h1><a name="module-initialization">Module Initialization</a></h1>
<p>The import-startup-bootstrap process employed by wxPython was changed
-such that wxWindows and the underlying gui toolkit are <strong>not</strong>
+such that wxWidgets and the underlying gui toolkit are <strong>not</strong>
initialized until the wx.App object is created (but before wx.App.OnInit
is called.) This was required because of some changes that were made
to the C++ wxApp class.</p>
Insert, Prepend, and etc.) methods any longer. Just use Add and the
wrappers will figure out what to do.</p>
</div>
+<div class="section" id="platforminfo">
+<h1><a name="platforminfo">PlatformInfo</a></h1>
+<p>Added wx.PlatformInfo which is a tuple containing strings that
+describe the platform and build options of wxPython. This lets you
+know more about the build than just the __WXPORT__ value that
+wx.Platform contains, such as if it is a GTK2 build. For example,
+instead of:</p>
+<pre class="literal-block">
+if wx.Platform == "__WXGTK__":
+ ...
+</pre>
+<p>you should do this:</p>
+<pre class="literal-block">
+if "__WXGTK__" in wx.PlatformInfo:
+ ...
+</pre>
+<p>and you can specifically check for a wxGTK2 build by looking for
+"gtk2" in wx.PlatformInfo. Unicode builds are also detectable this
+way. If there are any other platform/toolkit/build flags that make
+sense to add to this tuple please let me know.</p>
+<p>BTW, wx.Platform will probably be deprecated in the future.</p>
+</div>
<div class="section" id="other-stuff">
<h1><a name="other-stuff">Other Stuff</a></h1>
<p>Instead of over a dozen separate extension modules linked together
there are compatibility aliases for much of the above items.</p>
<p>The wxWave class has been renamed to wxSound, and now has a slightly
different API.</p>
+<p>Instead of a very small 20x20 the default window size is now a more
+reasonable size, (currently 400x250 but that may change...) If you
+don't specify a size, and the window/control class does not have any
+definition of it's own "best size" (most controls do) then the new
+default will be used. If you have code that accidentally depends on
+the smaller size then things will look a bit odd. To work around this
+just give those windows an explicit size when created.</p>
</div>
</div>
<hr class="footer" />
<div class="footer">
-Generated on: 2004-02-27 23:30 UTC.
+Generated on: 2004-03-12 19:55 UTC.
</div>
</body>
</html>
</div>
<hr class="footer" />
<div class="footer">
-Generated on: 2004-02-27 00:27 UTC.
+Generated on: 2004-03-12 19:55 UTC.
</div>
</body>
</html>
<dd>to 2.5 that require changes to your
applications</dd>
</dl>
-<p>licence/* Text of the wxWindows license.</p>
+<p>licence/* Text of the wxWidgets license.</p>
</blockquote>
<p>--
Robin Dunn
</div>
<hr class="footer" />
<div class="footer">
-Generated on: 2004-02-27 00:27 UTC.
+Generated on: 2004-03-12 19:55 UTC.
</div>
</body>
</html>
</div>
<hr class="footer" />
<div class="footer">
-Generated on: 2004-02-27 00:27 UTC.
+Generated on: 2004-03-12 19:55 UTC.
</div>
</body>
</html>
</div>
<hr class="footer" />
<div class="footer">
-Generated on: 2004-02-27 00:27 UTC.
+Generated on: 2004-03-12 19:55 UTC.
</div>
</body>
</html>
</div>
<hr class="footer" />
<div class="footer">
-Generated on: 2004-02-27 00:27 UTC.
+Generated on: 2004-03-12 19:55 UTC.
</div>
</body>
</html>
</div>
<hr class="footer" />
<div class="footer">
-Generated on: 2004-02-27 00:27 UTC.
+Generated on: 2004-03-12 19:55 UTC.
</div>
</body>
</html>
</div>
<hr class="footer" />
<div class="footer">
-Generated on: 2004-02-27 00:27 UTC.
+Generated on: 2004-03-12 19:55 UTC.
</div>
</body>
</html>
projects / wxWidgets.git / commitdiff
