]> git.saurik.com Git - wxWidgets.git/blob - utils/wxPython/CHANGES.txt
browsedb.cpp browsedb.h dbbrowse.cpp dbbrowse.h dbbrowse.rc
[wxWidgets.git] / utils / wxPython / CHANGES.txt
1 CHANGES.txt for wxPython
2
3 ----------------------------------------------------------------------
4
5 What's new in 2.1.13
6 --------------------
7 Skipped a version number to match what has been released for wxGTK.
8
9 Updated wxMVCTree and added a demo for it, also fixed layout on GTK
10 and some flicker problems.
11
12 Added a wrapper class for the Visualization ToolKit (or VTK) in the
13 wxPython.lib.vtk module. (http://www.kitware.com/)
14
15 Fixed wxTreeCtrl.SetItemImage and GetItemImage to recognise the new
16 "which" parameter.
17
18 Added wxPython.lib.spashscreen from Mike Fletcher.
19
20 Added wxPython.lib.filebrowsebutton also from Mike Fletcher.
21
22 Renamed wxTreeCtrl.GetParent to GetItemParent to avoid a name clash
23 with wxWindow.GetParent.
24
25 Added wxIntersectRect to compute the intersection of two wxRect's.
26 It is used like this:
27
28 intersect = wxIntersectRect(rect1, rect2)
29
30 If r1 and r2 don't intersect then None is returned, otherwise the
31 rectangle representing the intersection is returned.
32
33 Some bug fixes for Clipboard and Drag-n-Drop.
34
35 Rotated text!!! WooHoo! (See wxDC.DrawRotatedText())
36
37 Added a set of Generic Buttons to the library. These are simple
38 window classes that look and act like native buttons, but you can have
39 a bit more control over them. The bezel width can be set in addition
40 to colours, fonts, etc. There is a ToggleButton as well as Bitmap
41 versions too. They should also serve as a good example of how to
42 create your own classes derived from wxControl.
43
44 The C++ wxToolBar classes have been redone, and so have the wxPython
45 wrappers. There have been slight modifications to some of the methods
46 but shouldn't impact anybody too much. I took the opportunity to add
47 support for setting user data on each toolbar tool. The new AddTool
48 methods look like this:
49
50 def AddTool(ID,
51 bitmap,
52 pushedBitmap = wxNullBitmap,
53 toggle = FALSE,
54 clientData = NULL,
55 shortHelpString = "",
56 longHelpString = "")
57
58 def AddSimpleTool(ID,
59 bitmap,
60 shortHelpString = "",
61 longHelpString = "",
62 toggle=FALSE)
63
64
65 There are also coresponding InsertTool and InsertSimpleTool methods
66 that additionally take an integer position as the first parameter.
67
68 Added a wrapper for the new PCX and TIFF ImageHandlers.
69
70 wxRect now simulates attributes named left, right, top and bottom.
71
72 Removed all non wx stuff from the glcanvas module since DA's PyOpenGL
73 is better and compatible with the wxGLCanvas. You can get it at
74 http://starship.python.net:9673/crew/da/Code/PyOpenGL.
75
76 Added some missing EVT_ functions.
77
78 Added Dirk Holtwic's editor classes to the wxPython.lib.editor
79 package.
80
81 Changed all the "LIST" parameter names to "choices" to match the docs.
82
83 More fixes for the wxFloatBar, and it now works on wxGTK even better
84 than wxMSW! (The feat is accomplished by using the wxTB_DOCKABLE
85 style flag instead of trying to float it ourselves.)
86
87
88
89
90 What's new in 2.1.11
91 --------------------
92 Skipped a few version numbers so wxMSW, wxGTK and wxPython are all
93 syncronized.
94
95 wxImage.SetData now makes a copy of the image data before giving it to
96 wxImage. I mistakenly thought that wxImage would copy the data
97 itself.
98
99 Fixed wxMSW's notebook so the pages get their size set as they are
100 being added. This should remove the need for our
101 wxNotebook.ResizeChildren hack.
102
103 wxPanels now support AutoLayout, and wxNotebooks and wxSplitterWindows
104 no longer tell their children to Layout() themselves. This will
105 probably only effect you if you have a wxWindow with AutoLayout inside
106 a notebook or splitter. If so, either change it to a wxPanel or add
107 an EVT_SIZE handler that calls Layout().
108
109 Fixed deadlock problem that happened when using threads.
110
111 Added new HTML printing classes.
112
113 Added wxWindow.GetHandle
114
115 Apparently wxMouseEvent.Position has been depreciated in wxWindows as
116 it is no longer available by default. You can use GetPositionTuple
117 (returning a tuple with x,y) instead, or GetPosition (returning a
118 wxPoint.)
119
120 Added wxPostEvent function that allows events to be posted and then
121 processed later. This is a thread-safe way to interact with the GUI
122 thread from other threads.
123
124 Added Clipboard and Drag-and-Drop classes.
125
126 Added wxFontEnumerator.
127
128 Many updates to wxMenu, wxMenuBar.
129
130 wxPyEvent and wxPyCommandEvent derived classes now give you the actual
131 Python object in the event handler instead of a new shadow.
132
133 Added a Calendar widget from Lorne White to the library.
134
135 Made some fixes to the wxFloatbar. It still has some troubles on
136 wxGTK...
137
138 Added an MVC tree control from Bryn Keller to the library.
139
140
141
142
143 What's new in 2.1.5
144 -------------------
145 This is a quick bug-fix release to take care of a few nasties that
146 crept in at the last minute before 2.1.4 was called done. No new
147 major features.
148
149
150
151 What's new in 2.1.4
152 --------------------
153
154 This release is NOT syncronized with a snapshot release of wxGTK or
155 wxMSW. For MSW this isn't much of a problem since you can get the
156 binaries from the web site. For other platforms you'll have to build
157 wxGTK from CVS. (See http://web.ukonline.co.uk/julian.smart/wxwin/cvs.htm)
158 To get the same set of sources from CVS that I used, checkout using
159 the wxPy-2-1-4 tag.
160
161 Now back to what's new...
162
163 Much more support for event-less callbacks and add-on modules.
164
165 Created add-on module with wxOGL classes.
166
167 Added wxWindow.GetChildren(). Be careful of this. It returns a *copy*
168 of the list of the window's children. While you are using the list if
169 anything changes in the real list (a child is deleted, etc.) then the
170 list you are holding will suddenly have window references to garbage
171 memory and your app will likely crash. But if you are careful it works
172 great!
173
174 Added a bunch of new and missing methods to wxTreeCrtl. The
175 SortChildren method is now supported, but currently only for the
176 default sort order.
177
178 Added typemaps for wxSize, wxPoint, wxRealPoint, and wxRect that allow
179 either the actual objects or Python sequence values to be used. For
180 example, the following are equivallent:
181
182 win = wxWindow(parent, size = wxSize(100, 100))
183 win = wxWindow(parent, size = (100, 100))
184
185 Super-charged the wxHtml module. You can now create your own tag
186 handlers and also have access to the parser and cell classes. There
187 is a tag handler in the library at wxPython.lib.wxpTag that
188 understands the WXP tag and is able to place wxPython windows on HTML
189 pages. See the demo for an example.
190
191 A bunch of the methods of wxMenuBar were previously ifdef'd out for
192 wxGTK. Added them back in since the methods exist now.
193
194 Wrapped the wxHtmlHelpController and related classes.
195
196 Wrapped the C++ versions of wxSizer and friends. The Python-only
197 versions are still in the library, but depreciated. (You will get a
198 warning message if you try to use them, but the warning can be
199 disabled.) The usage of the C++ versions is slightly different, and
200 the functionality of wxBorderSizer is now part of wxBoxSizer. I have
201 added a few methods to wxSizer to try and make the transition as
202 smooth as possible, I combined all Add methods into a single method
203 that handles all cases, added an AddMany method, etc. One step I did
204 not take was to make the default value of flag in the Add method be
205 wxGROW. This would have made it more backward compatible, but less
206 portable to and from wxWin C++ code. Please see the docs and demo for
207 further details.
208
209 Added wxPyEvent and wxPyCommandEvent classes, derived from wxEvent and
210 wxCommandEvent. Each of them has SetPyData and GetPyData methods that
211 accept or return a single Python object. You can use these classes
212 directly or derive from them to create your own types of event objects
213 that can pass through the wxWindows event system without loosing their
214 Python parts (as long as they are stored with SetPyData.) Stay tuned
215 for more info and examples in future releases.
216
217 Added wxPython.lib.grids as an example of how to derive a new sizer
218 from the C++ sizers. In this module you will find wxGridSizer and
219 wxFlexGridSizer. wxGridSizer arrainges its items in a grid in which
220 all the widths and heights are the same. wxFlexgridSizer allows
221 different widths and heights, and you can also specify rows and/or
222 columns that are growable. See the demo for a couple examples for how
223 to use them.
224
225 Added the wxValidator class, and created a class named wxPyValidator
226 that should be used for the base class of any Python validators. See
227 the demo for an example. Please note that you MUST implement a Clone
228 method in your validator classes because of the way some things work
229 in the underlying C++ library. I did not add wxTextValidator because
230 of some issues of how it transfers data to and from a wxString, which
231 in wxPython is automatically translated to and from Python strings, so
232 there would never be a concrete wxString that would hang around long
233 enough for the validator to do its job. On the other hand, it should
234 be real easy to duplicate the functionality of wxTextValidator in a
235 pure Python class derived from wxPyValidator.
236
237 I've finally added a feature that has been on my list for close to two
238 years! Ever wondered what that zero is for when you create your app
239 object? Well now you can leave it out or explicitly set it to a true
240 value. This value now controls what is to be done with sys.stdout and
241 sys.stderr. A false value leaves them alone, and a true value sets
242 them to an instance of wxPyOnDemandOutputWindow. (On windows the
243 default is true, on unix platforms the default is false.) This class
244 creates a frame containing a wxTextCtrl as soon as anything is written
245 to sys.stdout or sys.stderr. If you close the window it will come
246 back again the next time something is written. (You can call
247 app.RestoreStdio to turn this off.) If you would rather that the stdio be
248 redirected to a file, you can provide a second parameter to your app
249 object's constructor that is a filename. If you want to use your own
250 class instead of wxPyOnDemandOutputWindow you can either implement
251 RedirectStdio() in you app class or change the value of
252 wxApp.outputWindowClass like this:
253
254 class MyApp(wxApp):
255 outputWindowClass = MyClass
256
257 def OnInit(self):
258 frame = MyFrame()
259 self.SetTopWindow(frame)
260 return true
261
262 Please see the implementation of wxPyOnDemandOutputWindow and wxApp in
263 wx.py for more details. A few words of caution: if you are running
264 your app in a debugger, changing sys.stdout and sys.stderr is likely
265 to really screw things up.
266
267 Added wxCaret. Unfortunately it's author has still not documented it
268 in the wxWindows docs...
269
270 Some new 3rd party contributions in wxPython.lib. PyShell, in
271 shell.py is an interesting implementaion of an interactive Python
272 shell in wxWindows. floatbar.py has a class derived from wxToolBar
273 that can sense mouse drags and then reparent itself into another
274 frame. Moving the new frame close to where it came from puts the tool
275 bar back into the original parent. (Unfortunately there is currently
276 a bug in wxGTK's wxFrame.SetToolBar so the FloatBar has some
277 problems...)
278
279
280
281
282 What's new in 2.1b3
283 --------------------
284
285 This release is syncronized with release 2.1 snapshot 9 of wxWindows.
286
287 Switched to using SWIG from CVS (see http://swig.cs.uchicago.edu/cvs.html)
288 for some of the new features and such. Also they have encorporated my
289 patches so there is really no reason to stick with the current (very
290 old) release... This version of SWIG gives the following new
291 features:
292
293 1. Keyword arguments. You no longer have to specify all the
294 parameters with defaults to a method just to specify a
295 non-default value on the end. You can now do this instead:
296
297 win = wxWindow(parent, -1, style = mystyle)
298
299 2. There is now an an equivalence between Python's None and C++'s
300 NULL. This means that any methods that might return NULL will
301 now return None and you can use none where wxWindows might be
302 expecting NULL. This makes things much more snake-ish.
303
304
305 There is a new build system based on a new Python program instead of
306 raw makefiles. Now wxPython builds are virtually the same on MSW or
307 Unix systems. See the end of this file for new build instructions and
308 see distrib/build.py for more details.
309
310 wxDC.Bilt now includes the useMask parameter, and has been split into
311 two different versions. wxDC.BlitXY is like what was there before and
312 takes raw coordinants and sizes, and the new wxDC.Blit is for the new
313 interface using wxPoints and a wxSize.
314
315
316
317
318
319 What's new in 2.1b2
320 --------------------
321
322 Added the missing wxWindow.GetUpdateRegion() method.
323
324 Made a new change in SWIG (update your patches everybody) that
325 provides a fix for global shadow objects that get an exception in
326 their __del__ when their extension module has already been deleted.
327 It was only a 1 line change in .../SWIG/Modules/pycpp.cxx at about
328 line 496 if you want to do it by hand.
329
330 It is now possible to run through MainLoop more than once in any one
331 process. The cleanup that used to happen as MainLoop completed (and
332 prevented it from running again) has been delayed until the wxc module
333 is being unloaded by Python.
334
335 I fixed a bunch of stuff in the C++ version of wxGrid so it wouldn't
336 make wxPython look bad.
337
338 wxWindow.PopupMenu() now takes a wxPoint instead of x,y. Added
339 wxWindow.PopupMenuXY to be consistent with some other methods.
340
341 Added wxGrid.SetEditInPlace and wxGrid.GetEditInPlace.
342
343 You can now provide your own app.MainLoop method. See
344 wxPython/demo/demoMainLoop.py for an example and some explaination.
345
346 Got the in-place-edit for the wxTreeCtrl fixed and added some demo
347 code to show how to use it.
348
349 Put the wxIcon constructor back in for GTK as it now has one that
350 matches MSW's.
351
352 Added wxGrid.GetCells
353
354 Added wxSystemSettings static methods as functions with names like
355 wxSystemSettings_GetSystemColour.
356
357 Removed wxPyMenu since using menu callbacks have been depreciated in
358 wxWindows. Use wxMenu and events instead.
359
360 Added alternate wxBitmap constructor (for MSW only) as
361 wxBitmapFromData(data, type, width, height, depth = 1)
362
363 Added a helper function named wxPyTypeCast that can convert shadow
364 objects of one type into shadow objects of another type. (Like doing
365 a down-cast.) See the implementation in wx.py for some docs.
366
367 Fixed wxImage GetData and SetData to properly use String objects for
368 data transfer.
369
370 Added access methods to wxGridEvent.
371
372 New Makefile/Setup files supporting multiple dynamic extension modules
373 for unix systems.
374
375 Fixes for the wxGLCanvas demo to work around a strange bug in gtk.
376
377 SWIG support routines now compiled separately instead of being bundled
378 in wx.cpp.
379
380
381
382
383
384 What's new in 2.1b1
385 --------------------
386 Fixed wxComboBox.SetSelection so that it actually sets the selected
387 item. (Actually just removed it from wxPython and let it default to
388 wxChoice.SetSelection which was already doing the right thing.)
389
390 Added the Printing Framework.
391
392 Switched back to using the wxWindows DLL for the pre-built Win32
393 version. The problem was needing to reinitialize static class info
394 data after loading each extension module.
395
396 Lots of little tweaks and additions to reflect changes to various
397 wxWindows classes.
398
399 Fixed a bug with attaching objects to tree items. Actually was a
400 symptom of a larger problem with not obtaining the interpreter lock
401 when doing any Py_DECREFs.
402
403 wxSizer and friends. Sizers are layout tools that manage a colection
404 of windows and sizers. Different types of sizers apply different
405 types of layout algorithms. You saw it here first! These classes are
406 not even in the wxWindows C++ library yet!
407
408
409
410 What's new in 2.0b9
411 -------------------
412 Bug fix for ListCtrl in test4.py (Was a missing file... DSM!)
413
414 Bug fix for occassional GPF on Win32 systems upon termination of a
415 wxPython application.
416
417 Added wxListBox.GetSelections returning selections as a Tuple.
418
419 Added a wxTreeItemData that is able to hold any Python object and be
420 associated with items in a wxTreeCtrl. Added test pytree.py to show
421 this feature off.
422
423 Added wxSafeYield function.
424
425 OpenGL Canvas can be optionally compiled in to wxPython.
426
427 Awesome new Demo Framework for showing off wxPython and for learning
428 how it all works.
429
430 The pre-built Win32 version is no longer distributing the wxWindows
431 DLL. It is statically linked with the wxWindows library instead.
432
433 Added a couple missing items from the docs.
434
435 Added wxImage, wxImageHandler, wxPNGHandler, wxJPEGHandler,
436 wxGIFHandler and wxBMPHandler.
437
438 Added new methods to wxTextCtrl.
439
440 Fixed some problems with how SWIG was wrapping some wxTreeCtrl
441 methods.
442
443
444
445 What's new in 2.0b8
446 -------------------
447 Support for using Python threads in wxPython apps.
448
449 Several missing methods from various classes.
450
451 Various bug fixes.
452
453
454
455 What's new in 2.0b7
456 -------------------
457 Added DLG_PNT and DLG_SZE convienience methods to wxWindow class.
458
459 Added missing constructor and other methods for wxMenuItem.
460
461
462
463 What's new in 2.0b6
464 -------------------
465 Just a quickie update to fix the self-installer to be compatible with
466 Python 1.5.2b2's Registry settings.
467
468
469 What's new in 2.0b5
470 -------------------
471 Well obviously the numbering scheme has changed. I did this to
472 reflect the fact that this truly is the second major revision of
473 wxPython, (well the third actually if you count the one I did for
474 wxWindows 1.68 and then threw away...) and also that it is associated
475 with the 2.0 version of wxWindows.
476
477 I have finally started documenting wxPython. There are several pages
478 in the wxWindows documentation tree specifically about wxPython, and I
479 have added notes within the class references about where and how wxPython
480 diverges from wxWindows.
481
482 Added wxWindow_FromHWND(hWnd) for wxMSW to construct a wxWindow from a
483 window handle. If you can get the window handle into the python code,
484 it should just work... More news on this later.
485
486 Added wxImageList, wxToolTip.
487
488 Re-enabled wxConfig.DeleteAll() since it is reportedly fixed for the
489 wxRegConfig class.
490
491 As usual, some bug fixes, tweaks, etc.
492
493
494
495 What's new in 0.5.3
496 -------------------
497 Added wxSashWindow, wxSashEvent, wxLayoutAlgorithm, etc.
498
499 Various cleanup, tweaks, minor additions, etc. to maintain
500 compatibility with the current wxWindows.
501
502
503
504 What's new in 0.5.0
505 -------------------
506 Changed the import semantics from "from wxPython import *" to "from
507 wxPython.wx import *" This is for people who are worried about
508 namespace pollution, they can use "from wxPython import wx" and then
509 prefix all the wxPython identifiers with "wx."
510
511 Added wxTaskbarIcon for wxMSW.
512
513 Made the events work for wxGrid.
514
515 Added wxConfig.
516
517 Added wxMiniFrame for wxGTK.
518
519 Changed many of the args and return values that were pointers to gdi
520 objects to references to reflect changes in the wxWindows API.
521
522 Other assorted fixes and additions.
523
524
525
526
527 What's new in 0.4.2
528 -------------------
529
530 wxPython on wxGTK works!!! Both dynamic and static on Linux and
531 static on Solaris have been tested. Many thanks go to Harm
532 <H.v.d.Heijden@phys.tue.nl> for his astute detective work on tracking
533 down a nasty DECREF bug. Okay so I have to confess that it was just a
534 DSM (Dumb Stupid Mistake) on my part but it was nasty none the less
535 because the behavior was so different on different platforms.
536
537 The dynamicly loaded module on Solaris is still segfaulting, so it
538 must have been a different issue all along...
539
540
541
542 What's New in 0.4
543 -----------------
544
545 1. Worked on wxGTK compatibility. It is partially working. On a
546 Solaris/Sparc box wxPython is working but only when it is statically
547 linked with the Python interpreter. When built as a dyamically loaded
548 extension module, things start acting weirdly and it soon seg-faults.
549 And on Linux both the statically linked and the dynamically linked
550 version segfault shortly after starting up.
551
552 2. Added Toolbar, StatusBar and SplitterWindow classes.
553
554 3. Varioius bug fixes, enhancements, etc.
555
556 ----------------------------------------------------------------------