Refactor! Change those apples into oranges, maybe a tangerine.

110108_1873[1] I've done a lot of code churn and learned a ton about the IMU (I normally call it my gyro) and how I should design the overall system.  I need it to be fast but still have it properly object oriented if I do choose to do use the code in a different area.

The 'old' Debugger application had some of the source mixed between the form and the objects.  The new code will be done like this:

ImuData class -> Imu class which has a ReportProgress delegate in it.

I also have a Skateboard class which will have the Imu and AmpFlow motor controller class.  The skateboard class will have a ReportProgress delegate too.  Why do this?  I was thinking about having a Phidget LED controller board since I need a deadman switch.  I can then get a two'fer for the hardware.  It gives me visual feedback on the current status along with provides the sensor information.

SO why redo the code?  I wasn't happy with the NameSpace, a lot of the variable names, class names, and about 25% of where the code was located.  Due to this, I figured it was easier to just create a new project and do the faster approach.  It also lets me take a step back and see the forest from the trees.

No comments posted yet.

Post a Comment

Please add 3 and 6 and type the answer here: