Added some Motif wxGLCanvas support; some more Motif bugs cured; print dialogs

[wxWidgets.git] / utils / wxPython / README.txt

diff --git a/utils/wxPython/README.txt b/utils/wxPython/README.txt
index 3244f861e6aae33b87252c7467084a97a3c22804..6ab54cdad197a243f3bbf07299608b947c6f6f63 100644 (file)
--- a/utils/wxPython/README.txt
+++ b/utils/wxPython/README.txt
@@ -10,7 +10,7 @@ extremly cool object oriented language.  It's easier than Perl and
 nearly as powerful.  It runs on more platforms than Java, and by some
 reports, is even faster than Java with a JIT compiler!
 
 nearly as powerful.  It runs on more platforms than Java, and by some
 reports, is even faster than Java with a JIT compiler!
 

-So why would you wan to use wxPython over just C++ and wxWindows?
+So why would you want to use wxPython over just C++ and wxWindows?

 Personally I prefer using Python for everything.  I only use C++ when
 I absolutly have to eek more performance out of an algorithm, and even
 then I ususally code it as an extension module and leave the majority
 Personally I prefer using Python for everything.  I only use C++ when
 I absolutly have to eek more performance out of an algorithm, and even
 then I ususally code it as an extension module and leave the majority


@@ -32,7 +32,8 @@ Python.  For example, some methods that return mutliple values via
 argument pointers in C++ will return a tuple of values in Python.
 These differences have not been documented yet so if something isn't
 working the same as described in the wxWindows documents the best
 argument pointers in C++ will return a tuple of values in Python.
 These differences have not been documented yet so if something isn't
 working the same as described in the wxWindows documents the best

-thing to do is to scan through the wxPython sources.
+thing to do is to scan through the wxPython sources, especially the .i
+files, as that is where the interfaces for wxPython are defined.

 
 Currently this extension module is designed such that the entire
 application will be written in Python.  I havn't tried it yet, but I
 
 Currently this extension module is designed such that the entire
 application will be written in Python.  I havn't tried it yet, but I


@@ -41,20 +42,81 @@ application will cause problems.  However there is a plan to support
 this in the future.
 
 
 this in the future.
 
 

+What's new in 0.5.0
+-------------------
+Changed the import semantics from "from wxPython import *" to "from
+wxPython.wx import *"  This is for people who are worried about
+namespace pollution, they can use "from wxPython import wx" and then
+prefix all the wxPython identifiers with "wx."
+
+Added wxTaskbarIcon for wxMSW.
+
+Made the events work for wxGrid.
+
+Added wxConfig.
+
+Added wxMiniFrame for wxGTK, (untested.)
+
+Changed many of the args and return values that were pointers to gdi
+objects to references to reflect changes in the wxWindows API.
+
+Other assorted fixes and additions.
+
+
+
+
+What's new in 0.4.2
+-------------------
+
+wxPython on wxGTK works!!!  Both dynamic and static on Linux and
+static on Solaris have been tested.  Many thanks go to Harm
+<H.v.d.Heijden@phys.tue.nl> for his astute detective work on tracking
+down a nasty DECREF bug.  Okay so I have to confess that it was just a
+DSM (Dumb Stupid Mistake) on my part but it was nasty none the less
+because the behavior was so different on different platforms.
+
+
+The dynamicly loaded module on Solaris is still segfaulting, so it
+must have been a different issue all along...
+
+
+
+What's New in 0.4
+-----------------
+
+1. Worked on wxGTK compatibility.  It is partially working.  On a
+Solaris/Sparc box wxPython is working but only when it is statically
+linked with the Python interpreter.  When built as a dyamically loaded
+extension module, things start acting weirdly and it soon seg-faults.
+And on Linux both the statically linked and the dynamically linked
+version segfault shortly after starting up.
+
+2. Added Toolbar, StatusBar and SplitterWindow classes.
+
+3. Varioius bug fixes, enhancements, etc.
+
+

 
 Build Instructions
 ------------------
 I used SWIG (http://www.swig.org) to create the source code for the
 extension module.  This enabled me to only have to deal with a small
 
 Build Instructions
 ------------------
 I used SWIG (http://www.swig.org) to create the source code for the
 extension module.  This enabled me to only have to deal with a small

-amount of code an only have to bother with the exceptional issues.
+amount of code and only have to bother with the exceptional issues.

 SWIG takes care of the rest and generates all the repetative code for
 me.  You don't need SWIG to build the extension module as all the
 SWIG takes care of the rest and generates all the repetative code for
 me.  You don't need SWIG to build the extension module as all the

-generated C++ code is included in the src directory.
+generated C++ code is included under the src directory.
+
+I added a few minor features to SWIG to control some of the code
+generation.  If you want to playaround with this the patches are in
+wxPython/SWIG.patches and they should be applied to the 1.1p5 version
+of SWIG.  These new patches are documented at
+http://starship.skyport.net/crew/robind/python/#swig, and they should
+also end up in the 1.2 version of SWIG.

 
 wxPython is organized as a Python package.  This means that the
 directory containing the results of the build process should be a
 subdirectory of a directory on the PYTHONPATH.  (And preferably should
 
 wxPython is organized as a Python package.  This means that the
 directory containing the results of the build process should be a
 subdirectory of a directory on the PYTHONPATH.  (And preferably should

-be named wxPython.)  You can control where the bulid process will dump
+be named wxPython.)  You can control where the build process will dump

 wxPython by setting the TARGETDIR makefile variable.  The default is
 $(WXWIN)/utils/wxPython, where this README.txt is located.  If you
 leave it here then you should add $(WXWIN)/utils to your PYTHONPATH.
 wxPython by setting the TARGETDIR makefile variable.  The default is
 $(WXWIN)/utils/wxPython, where this README.txt is located.  If you
 leave it here then you should add $(WXWIN)/utils to your PYTHONPATH.


@@ -65,8 +127,9 @@ PYTHONPATH, such as the site-packages directory on Unix systems.
 Win32
 -----
 
 Win32
 -----
 

-1. Build wxWindows with USE_RESOURCE_LOADING_IN_MSW set to 1 in
-include/wx/msw/setup.h so icons can be loaded dynamically.
+1. Build wxWindows with wxUSE_RESOURCE_LOADING_IN_MSW set to 1 in
+include/wx/msw/setup.h so icons can be loaded dynamically.  While
+there, make sure wxUSE_OWNER_DRAWN is also set to 1.

 
 2. Change into the $(WXWIN)/utils/wxPython/src directory.
 
 
 2. Change into the $(WXWIN)/utils/wxPython/src directory.
 


@@ -78,7 +141,7 @@ above.
 
 5. If it builds successfully, congratulations!  Move on to the next
 step.  If not then you can try mailing me for help.  Also, I will
 
 5. If it builds successfully, congratulations!  Move on to the next
 step.  If not then you can try mailing me for help.  Also, I will

-always have a pre-built win32 version of this module at
+always have a pre-built win32 version of this extension module at

 http://starship.skyport.net/crew/robind/python.
 
 6. Change to the $(WXWIN)/utils/wxPython/tests directory.
 http://starship.skyport.net/crew/robind/python.
 
 6. Change to the $(WXWIN)/utils/wxPython/tests directory.


@@ -97,15 +160,11 @@ version of Python either from the command line or from a shortcut.
 Unix
 ----
 
 Unix
 ----
 

-NOTE:  I don't have wxPython working yet with wxGTK, so if you aren't
-using Win32 you can skip the rest of this file and check back in a
-week or so.
-
-

 1. Change into the $(WXWIN)/utils/wxPython/src directory.
 
 2. Edit Setup.in and ensure that the flags, directories, and toolkit
 1. Change into the $(WXWIN)/utils/wxPython/src directory.
 
 2. Edit Setup.in and ensure that the flags, directories, and toolkit

-options are correct.  See the above commentary about TARGETDIR.
+options are correct.  See the above commentary about TARGETDIR.  There
+are a few sample Setup.in.[platform] files provided.

 
 3. Run this command to generate a makefile:
 
 
 3. Run this command to generate a makefile:
 


@@ -127,7 +186,10 @@ module:
 
 
 ------------------------
 
 
 ------------------------

-8/8/1998
+10/20/1998

 
 Robin Dunn
 
 Robin Dunn

-robind@earthling.net
+robin@alldunn.com
+
+
+