13
Mar 09

Fujitsiu LT C-500 touchscreen in Ubuntu

Just as a small note to anyone trying to get this to work, the fpit driver has a bug in every version of ubuntu up to and including hardy; upgrade to intrepid and you get fully a functional touchscreen again, using this xorg.conf:

Section "InputDevice"
    Identifier     "touchscreen"
    Driver         "fpit"
    Option         "Device"    "/dev/ttyS1"
    Option        "BaudRate"    "9600"
    Option        "MaximumXPosition"    "4096"
    Option        "MaximumYPosition"    "4096"
    Option        "MinimumXPosition"    "0"
    Option        "MinimumYPosition"    "0"
    Option        "Passive"
    Option        "SendCoreEvents"
    Option        "TrackRandR" "true"
EndSection

Just don’t try using KDE4 unless slow-motion work sounds appealing 😀 XFCE is reasonable though, so Xubuntu is an option (and what I’m running on it right now).

Now, on with the PyQT4 coding…


07
Jan 09

Kada2.py output

Ray asked to see what the output of the kada2 script I’ve been working on looks like – only problem is that I’ve been using a real datafile for development, so it has people’s names in it. To avoid any shoutyness, one quick python script to read in the members.kda file and write it back out to test.kda with all the names changed to John Smith; then a quick run with this file as the members.kda file and some imagemagick conversions and viola, the current kada.py output. Continue reading →


06
Jan 09

ReportLab

As I mentioned before, after writing a python script to read in Kada’s data files on the rifle club shooters’ scores and calculate new ladders, the next step is output that’s a bit fancier than the straight ASCII text dump:

Novice Air Ladder
- - - - - - - - - - - - - - - -

 1         Joe D'Plumber    45  91.833    94
 2         Joe D'Plumber    36  87.500    91
 3         Joe D'Plumber    18  87.167    92
 4         Joe D'Plumber    16  85.833    91
 5         Joe D'Plumber    26  85.167    92
 6         Joe D'Plumber    31  81.167    87
          Tito D'Builder     2  76.000    76  *
 7         Joe D'Plumber     7  74.000    82
          Tito D'Builder     2  69.000    75  *
          Tito D'Builder     2  67.000    68  *
          Tito D'Builder     2  66.000    70  *
          Tito D'Builder     1  64.000    64  *
 8         Joe D'Plumber    10  63.167    78
          Tito D'Builder     1  62.000    62  *
 9         Joe D'Plumber     4  61.750    76
          Tito D'Builder     2  61.500    72  *
          Tito D'Builder     1  60.000    60  *
          Tito D'Builder     2  55.500    71  *
          Tito D'Builder     2  55.000    58  *
10         Joe D'Plumber     3  53.667    62
          Tito D'Builder     1  52.000    52  *
          Tito D'Builder     1  50.000    50  *
          Tito D'Builder     1  49.000    49  *

This does the basic job that the original system did (actually, it does a bit more – the asterisks mark out those shooters who haven’t yet shot enough cards to get on the ladder, but they’re still listed as an incentive for them to shoot more cards – the current system doesn’t do this). It’s not really doing all that can be done, however, and it’s certainly not all that fancy-looking. Especially in a scripting language, where the whole point is to do fancy stuff quickly through toolkits. So, what I wanted was PDF output (because these are printed off and posted up in the club), graphics like logos and so on, but also some graphs and charts with some meaningful data.

One of the graphs I wanted to include was one of Edward Tufte’s many good ideas, sparklines. Small graphs which summarise the state of play of a variable in an easy to read, inline format (meaning that it’s in the flow of the text itself as if english had suddenly become a pictographic language for a moment. They seemed perfect to show a high-level view of how the shooters were doing over the course of the year. Also, it would be nice to display the various breakdowns and analysis of membership (by gender, experience, college year, etc) in a graphical form – there’s nothing wrong with the raw data, but it’s almost always easier and faster to take in analysis that has a graphical expression. So pie charts and such would be an improvement. Continue reading →