The Gadgeteer Light discussion this weekend ( http://www.tinyclr.com/forum/21/6726/ ) has me thinking a lot about the process that GHI has been using to develop it’s Gadgeteer modules and some frustrations I’ve been holding back. GHI, of course, has done an outstanding job at designing the hardware for modules but I must admit that I’m less than impressed at many of the driver interfaces that ship with the hardware. For example, do we really need a dozen different methods in the Multicolor LED module that all basically accomplish the same thing? A single SetRgb() could eliminate most of the other methods (I understand that the on-module MCU causes most of this). The Joystick module data is basically useless without always applying some trig… So, why not do it in the driver?
What I would like to see GHI implement is a beta phase for modules where we (the community) can work with GHI to define the software interfaces for modules before they are officially released and you have to start worrying about supporting old APIs. Whatcha think?