If you’ve followed my New Remote Camera Robot efforts, you will realize that the main sticking point is the joystick itself.
Doing a web search returns two classes of results - actually three if you count the MDN, (Mozilla Development Network), articles.
Joystick demos that take a joystick and return a web page showing what the joystick is doing.
“Virtual” joystick software - not unlike the nipple.js that is currently installed in the existing Remote Camera Robot demo. These packages usually take either/both touch or mouse input and make it into a “virtual joystick”
At first glance, you would think that the joystick demos would be the fast track to getting a working joystick. And that would be true IF it wasn’t so cluttered up with ancillary code to create the web page and display the results.
The virtual joystick packages also look good - they already do what I want. They return events and/or values that represent movements of the virtual joystick. You’d think that all you have to do is substitute a real joystick for the virtual representation, and you’re done!
Nope. That code is so convoluted that it makes a Minoan maze look like a simple hallway and I’ve seen both American and Russian bureaucracy that’s less complicated.
Sigh. . . .
Guess I need to get a sharpener for my unicorn horn 'eh?