Zachary J. Fields

To answer your previous question. Yes those code paths get executed, but in the static callbacks of FirmataClass.h. https://github.com/firmata/arduino/blob/master/Firmata.h#L153 https://github.com/firmata/arduino/blob/master/Firmata.h#L154

I have rebased this branch on top of the recent `FIRMWARE_VERSION` update. Thus, resolving any obvious, or known, merge conflicts and making it more "cherry-pick"-able when v3.0.0 comes around.

Does this seem worth prototyping? I may do it either way, but didn't get a good read on your level of interest from your last post.

No. The latest version does a good job of laying the foundation, but the bits can be packed WAY tighter. Right now you are at 50% efficiency, and we can...

Based on the recent bug #363 this would definitely break compatibility with existing clients an will need to wait for v3.0.0

Sorry for the ultra-terse description - it was 5am (a little past my bedtime ;-)). The parser callback only provides a signal when it sees the `0xF9`, not the version...

@soundanalogous I think they would belong as private members to `FirmataMarshaller`. `void FirmataMarshaller::sendAnalog(uint8_t pin, uint16_t value)` Here, you would need the ability to pack the `value` parameter efficiently, and having...

As an example... `sendPinStateQuery` is missing from `FirmataMarshaller`

@soundanalogous I would love your input on this list.

I think it would be good to move STRING_DATA and REPORT_FIRMWARE out of FirmataParser and up into FirmataClass. This would allow for the elimination of the callbacks that belong to...