I'm trying to run something along the lines of https://app.shemza.digital/brightsign_debug on an HD222. I have a few variations of similar webgl things that will be exhibited in early January and I need to figure out whether this is workable, or to source other hardware.
For testing, I've reassigned `console.log` et al. to something that outputs to HTML.
It's normally built with Vite, which pretty much mandates that the entry point to the code is a `<script type="module">`, but I'm not sure if the player on the device supports that (I updated the firmware to 7.1.113 which seems to be the latest for that device). I managed to use esbuild (targeting chrome65 which I read should be similar to what the device is running, although that may not be true of the firmware I’m on) to make a version that imports without `type="module"`, but it still doesn’t seem to be working on the BrightSign. I added something to log when it gets into my main module, but it never reaches that point.
The graphics I'm rendering are quite simple, but at times involve rather a lot of three-js meshes, so there's a chance that the rendering gets a bit bogged down to the point where it wouldn’t be suitable - I haven’t been able to assess that yet. I also use WebRTC for relaying small amounts of data from users in realtime (no video or audio etc). It looks as though there is no `RTCPeerConnection` in this environment. In retrospect, I could probably have only used WebSockets, but I’m not inclined to re-write too much code when it’s not entirely clear how much more work would then still be needed, or whether it’d play smoothly. The thing I linked to doesn’t use WebRTC, anyway (but the actual thing I'm exhibiting does).