Okay, been poking at the Windows version of MapperGUI 2.99-beta and the newer incarnations of Python and wxPython.
1) I can't use Python 2.4 on the Windows
side. I'm still running on Windows 98
, and Python 2.4 extensions require MSC 7.1 & .NET SDK to be compiles. .NET SDK requires Win2000/WinXP/etc. Not an option for Windows 98. So, Windows version of MapperGUI is being tested with Python 2.3; I can't build a binary dist for Python 2.4. Beta testers, if you have the .NET 1.1 SDK and want to build the extension libs for the Windows version of MapperGUI 2.99 using Python 2.4, go for it! I just can't do it or test it myself, so my
binary distros will be Python 2.3 based.
2) On Windows
, wxPython 220.127.116.11-ansi with Python 2.3 has some flaked-out sizing bugs on the notetab controls, and looks like crap. Don't use wxPython 18.104.22.168 with Python 2.3 on Windows 98
with MapperGUI 2.99-beta. I have no idea how some other combo, like wxPython 22.214.171.124 with Python 2.4 on Windows XP, might work. Can't test it either, for reasons mentioned above. I'm testing with wxPython 126.96.36.199, which is the version I happened to have installed for the last while. It looks fine. If you find some earlier or later version of wxPython that doesn't turn into a pumpkin on the notetab controls, I'd like to know about it. If everything works peachy-keen on Windows XP, I'd like to know about it.
3) PIL 1.1.5 seems to work okay in both Windows and Linux with whatever version of Python & wxPython.
4) Using the latest everything on Linux (Python 2.4.1, wxPython-188.8.131.52, PIL 1.1.5) works fine. Looks good, builds extension libs okay, etc. I like Linux.
View this post on my blog