[Pythoncard-users] need opinions on two changes for 0.8

[Kevin A. <al...@se...>]

It looks like the next release of wxPython is very close to being=20
ready. For those of you that want to test it and the version of=20
PythonCard that is in cvs, you can find wxPython 2.5.2 test candidates=20=

at:

http://starship.python.net/crew/robind/wxPython/preview/

2.5.2.4 is the most recent build as of this morning, but there will=20
likely be a 2.5.2.5 or 2.5.2.6 depending on issues people report to the=20=

wxPython-dev mailing list before the final 2.5.2 release.

Once that is available I plan to do a PythonCard 0.8 release, so I=20
would appreciate comments from anyone working from cvs that wants to=20
identify bugs or any other issues they find. PythonCard 0.8 requires=20
wxPython 2.5.2.x as a minimum!

The two issues I want comments on are whether to leave the BitmapCanvas=20=

draw operations as separate x, y and width, height args or to use=20
tuples (x, y) and (width, height). What's in cvs right now are tuple=20
versions, but since wxPython switched back to separate args after the=20
2.5.1.5 outcry, my inclination on odd days is to go ahead and switch=20
back as well since it matches the wxPython arg list and is probably=20
simpler for people to remember. On even days I think using tuples is=20
more consistent since it matches the init args for components, but the=20=

wxPython API uses both forms for a lot of different methods. As a brief=20=

example, here's drawLine as used in the doodle sample with separate=20
args followed by tuple args. If nobody replies I'll go ahead and revert=20=

all the sample, BitmapCanvas, etc. before 0.8 is released.

event.target.drawLine(self.x, self.y, x, y)=00

event.target.drawLine((self.x, self.y), (x, y))=00

The second issue is that for a long time I've been thinking about just=20=

using the wx.lib.dialogs function wrappers for system dialogs instead=20
of the ones in PythonCard.dialog. I wrote most of the code in=20
wx.lib.dialogs last year, so it has the same goal as the current=20
PythonCard dialog code, which is to make all system dialogs function=20
calls. However, the arg lists are changed, mostly for the better, and=20
the result is a class instead of a dict. What I plan to do is leave the=20=

PythonCard.dialog module in place, but just import the appropriate=20
functions from wx.lib.dialogs or provide thin wrappers where PythonCard=20=

still needs some special handling such as the result returned by the=20
fontDialog. This change will impact every sample and tool that uses=20
system dialogs as well as the documentation Dan Shafer wrote, so I=20
don't want to switch if everyone is going to complain and I have to=20
switch all the code back. Again, if there aren't a lot of dissents,=20
I'll make the change later this week. Anyone that is interested in the=20=

changes, should just look at the wx.lib.dialogs.py code in wxPython=20
2.4.2.4 or later.

ka=