By hiding the sensor libraries behind a class, the user is stuck with what it provides them. What if they want to put the device into sleep mode? What if they want quaternions instead of Euler angles? We can't write wrapper functions for all those things - that compounds the heck out of the code size issue. The user should have direct access to the libraries if they want it.
The "if they want it" part is tricky, and I'm not sure what the best way to go about that in particular would be yet. I'm beginning to think C-style straight functions in a Balloonduino namespace will be a better solution than an OOP object.
By hiding the sensor libraries behind a class, the user is stuck with what it provides them. What if they want to put the device into sleep mode? What if they want quaternions instead of Euler angles? We can't write wrapper functions for all those things - that compounds the heck out of the code size issue. The user should have direct access to the libraries if they want it.
The "if they want it" part is tricky, and I'm not sure what the best way to go about that in particular would be yet. I'm beginning to think C-style straight functions in a Balloonduino namespace will be a better solution than an OOP object.