SI Simple / News: Recent posts

Release 0.8 contains support for direct download from the unit. It was briefly released but has been recaptured as it crashed with the second unit we tested it with.

Watch this space.

And if you hadn't figured, the release numbering has gone to pot.

0.5 Support import and internal edit of course data
Support import from file or web of SI names list
0.6 Support direct read of master/printer unit
0.7 Build with static libraries
0.8 Linux build

Project has now been migrated from wxWidgets to Qt.

Making pretty good progress on reading the download box directly, which will simplify things for users. Will integrate this into the Qt branch once the work is well-encapsulated, at the moment its spread all over a small test application.

Thinking about moving the project from wxWidgets to Qt before getting into developing the part that will read the download device.

Qt has resolved the two issues I didn't like - licensing and the custom drawing of controls. It has a development environment (including GUI editor) that works cross-platform. I guess its not as Gnome friendly as wxWidgets, but I can live with that.

Having a problem with wxdev-c++ - my .wxform file for main dialog fails parsing on one of my installations. May have to fall back to an earlier version of wxdev-c++, or rebuild parts of the interface from (almost) scratch.

Pretty good progress - almost al of the SIDResults functionality has been reproduced, but I got side-tracked adding an IOF XML export function so that the program could be used with WinSplits and RouteGadget.

Will finish off the functionality that allows results to be maniulated and make a Windows release for use in the real world.

I've been using Ken Hanson's excellent TCL program SIDResults for some SI processing, but I hae a couple of requirements I'm strugling with using my limited TCL skills:
1) Make it a little more flexible (handle the inevitable runners who forget to clear etc etc)
2) Make it do the upload from the SI unit (requires some serial IO)

I'm also seeing some small differences between the TCL script running on different TCL interpreters.... read more