Regarding the newly added API mode, it provides open web inference JS calls #322
Description
Based on the latest 2.0 branch, I developed drive_web_api.c locally and provided additional JavaScript API calls, allowing me to render through other web visualizations. After all, rendering and data are not bound together. I have successfully experimented with developing JavaScript and using Three.js for rendering, achieving the same effect as the demo.
But my main concern is that as you iterate, I also need to update the API. Should we consider making the API for web JS calls a universal feature?
The main objective is to develop an API for JavaScript calls, enabling more possibilities for visual development without being bound to raylib
