utils/wxPython/distrib/SelfInst-README.txt

   1 wxPython README
   2 ---------------
   3
   4 Welcome to the wonderful world of wxPython!
   5
   6 Now that you have installed the Win32 extension module, you can try it
   7 out by going to the [install dir]\wxPython\demo directory and typing:
   8
   9     python test1.py
  10
  11 There are also some other sample files there for you to play with and
  12 learn from.
  13
  14 If you selected to install the documentation then point your browser
  15 to [install dir]\wxPython\docs\index.htm and you will then be looking
  16 at the docs for wxWindows.  For the most part you can use the C++ docs
  17 as most classes and methods are used identically.  Where there are
  18 differences they are documented with a "wxPython Note."
  19
  20
  21
  22 Getting Help
  23 ------------
  24
  25 Since wxPython is a blending of multiple technologies, help comes from
  26 multiple sources.  See the http://alldunn.com/wxPython for details on
  27 various sources of help, but probably the best source is the
  28 wxPython-users mail list.  You can view the archive or subscribe by
  29 going to
  30
  31        http://starship.python.net/mailman/listinfo/wxpython-users
  32
  33 Or you can send mail directly to the list using this address:
  34
  35        wxpython-users@starship.python.net
  36
  37
  38
  39
  40 What's new in 2.0b5
  41 -------------------
  42 Well obviously the numbering scheme has changed.  I did this to
  43 reflect the fact that this truly is the second major revision of
  44 wxPython, (well the third actually if you count the one I did for
  45 wxWindows 1.68 and then threw away...) and also that it is associated
  46 with the 2.0 version of wxWindows.
  47
  48 I have finally started documenting wxPython.  There are several pages
  49 in the wxWindows documentation tree specifically about wxPython, and I
  50 have added notes within the class references about where and how wxPython
  51 diverges from wxWindows.
  52
  53 Added wxWindow_FromHWND(hWnd) for wxMSW to construct a wxWindow from a
  54 window handle.  If you can get the window handle into the python code,
  55 it should just work...  More news on this later.
  56
  57 Added wxImageList, wxToolTip.
  58
  59 Re-enabled wxConfig.DeleteAll() since it is reportedly fixed for the
  60 wxRegConfig class.
  61
  62 As usual, some bug fixes, tweaks, etc.
  63
  64
  65
  66 What's new in 0.5.3
  67 -------------------
  68 Added wxSashWindow, wxSashEvent, wxLayoutAlgorithm, etc.
  69
  70 Various cleanup, tweaks, minor additions, etc. to maintain
  71 compatibility with the current wxWindows.
  72
  73
  74
  75 What's new in 0.5.0
  76 -------------------
  77 Changed the import semantics from "from wxPython import *" to "from
  78 wxPython.wx import *"  This is for people who are worried about
  79 namespace pollution, they can use "from wxPython import wx" and then
  80 prefix all the wxPython identifiers with "wx."
  81
  82 Added wxTaskbarIcon for wxMSW.
  83
  84 Made the events work for wxGrid.
  85
  86 Added wxConfig.
  87
  88 Added wxMiniFrame for wxGTK.
  89
  90 Changed many of the args and return values that were pointers to gdi
  91 objects to references to reflect changes in the wxWindows API.
  92
  93 Other assorted fixes and additions.
  94
  95
  96
  97
  98 What's new in 0.4.2
  99 -------------------
 100
 101 wxPython on wxGTK works!!!  Both dynamic and static on Linux and
 102 static on Solaris have been tested.  Many thanks go to Harm
 103 <H.v.d.Heijden@phys.tue.nl> for his astute detective work on tracking
 104 down a nasty DECREF bug.  Okay so I have to confess that it was just a
 105 DSM (Dumb Stupid Mistake) on my part but it was nasty none the less
 106 because the behavior was so different on different platforms.
 107
 108
 109 The dynamicly loaded module on Solaris is still segfaulting, so it
 110 must have been a different issue all along...
 111
 112
 113
 114 What's New in 0.4
 115 -----------------
 116
 117 1. Worked on wxGTK compatibility.  It is partially working.  On a
 118 Solaris/Sparc box wxPython is working but only when it is statically
 119 linked with the Python interpreter.  When built as a dyamically loaded
 120 extension module, things start acting weirdly and it soon seg-faults.
 121 And on Linux both the statically linked and the dynamically linked
 122 version segfault shortly after starting up.
 123
 124 2. Added Toolbar, StatusBar and SplitterWindow classes.
 125
 126 3. Varioius bug fixes, enhancements, etc.
 127
 128
 129
 130 ----------------
 131 Robin Dunn
 132 robin@alldunn.com
 133
 134
 135