[Feature Request] Documentation of how the device and device drivers work

[divStar]

Hello!

I'd be interested in some documentation on how the device and device driver work together. I am the dude, who wants to port it somehow to MacOS, though I don't have much knowledge of Mac development, I have developed applications (usually server ones) in multiple languages over the last 14 years.

I also want to thank you in advance for making this device - I am no 3D designer or such, but I can imagine quite a few use cases outside of it, too, e.g. for music production or video editing (as you pointed out in one of your awesome videos).

While your readme for the end user is awesome, I think this repository and device deserve a bit of technical description (perhaps along with some diagrams to back it up and make it more understandable) on how it actually works and how the device interoperates with the device driver.

I am sure you have tons of work on your hands, so I certainly don't expect all the description to be present.

Looking at the process, I do not understand why we have to upload the changes using Arduino IDE. Is there no way to upload the file on your own or does it recompile a generated script before it uploads it to the device?

Also wouldn't it perhaps be easier if it had some EEPROM or minimal amount of other storage to store the profiles?

On the other hand perhaps the device could just provide a driver, that registered to it, with bare sensor values and the driver would map it according to the mappings a user set?

This way the device wouldn't necessarily store compiled profiles, but on the other hand remapping sensors to values would be a piece of cake and it wouldn't require changes to the device firmware.