[virtuald]

Originally Posted by byteit101

wow! you must have had time before the season to learn the code,

Actually, the key here is to just have zero life for 6 weeks. Reading WPILib helps a lot too.

and a very good programming team! we learned about it in the season. I would consider our team good (we have 6 people), even though 1 hardly ever comes, 2 barely know about coding this years control system, 1 knows some C++, but would have a hard time modifing our code, 1 knows most of the code, and I know all the code (I programmed most of the actual robot code) for a total of 2 1/4 people (productivity soars!)

We have two people on our programming team: me and a student who knows C to some degree, but struggles with OOP and classes. Unfortunately I did 95% of the coding in the last 2 weeks of the build season due to our robot not being assembled until 2 days before shipping. However, he *did* create/code a really neat way of controlling the robot -- using the gyro, we use the joystick to move the robot relative to the field (ie, pointing the joystick up makes it go north, pointing east goes east... etc).

My goal for the offseason is to use the code and help him (and others who might be interested, since he will be a senior next year) to learn more about OOP and such.

I would be interested to see your code, it sounds a bit much, but very OOPy sounding.

Its OOP in very much the same style that WPILib uses. The code is very straightforward code too, it only took 3 hours to implement the primary framework for it.

WPILib Test Harness GUI? like a fake cRIO? that would be cool && usefull!

Bingo. At the moment the driver station interface works quite well, and there is some support for motors and such. I've been putting in stubs for other stuff, my goal is to release it and see what others think, and possibly set up a sourceforge project for it. I've found it extremely useful for finding things like uninitialized variables and bad pointers, and for creating the driver station LCD user interface.