From: Patrick T. <tul...@cs...> - 2003-03-12 06:25:09
|
> > BTW, I grabbed the CVS snapshot and had to fetch the latest wxpython > > (the version that's part of Debian testing doesn't support all the > > features you're using). Just an FYI for the readme. > > I'll probably do a seperate developer readme/pages at some point. > wxpython 2.3 and 2.4 work for me. Are Debian REALLY behind on > wxpython? Yep. wxpython 2.2 is the version available in Debian testing (unstable has 2.3 and 2.4 in it). Dunno if the holdup is some dependency or a slow maintainer... For the archive, if others need to upgrade wxpython getting and installing the source wasn't difficult. It even includes the wxWindows distro and is generally nicely put together: http://prdownloads.sourceforge.net/wxpython/wxPythonSrc-2.4.0.4.tar.gz > > Also, a couple of the button graphics seem to be missing from the > > CVS repository. (They just show up as "?" onscreen.) > > That is correct. Ah, a todo item then... > I use Redhat 8.0 and the cable shows up as /dev/usb/ttyUSB0. RH doesn't > use devfs so it is really hard to tell what is actually connected. I > was thinking of parsinng the dmesg stuff to figure out something pretty > to display to the user! On my box its probably going to show up as /dev/ttyUSB1 (no intervening 'usb'). Amusingly it will probably show up in a different place depending on if my USB Visor is plugged in or not.... I should probably wait until I actually get a cable before making pronouncements, though. :) -Pat ----- ----- ---- --- --- -- - - - - - Pat Tullmann tul...@cs... "Forty-Two." -- Deep Thought |