I am deploying m8WebDisplay to a raspberryPi-based environment as an alternative to the rPi/m8c stack. I find m8WebDisplay to be more straightforward to customize, and it's browser level abstractions greatly simplify integration with the host. This way, one is not searching for how to get Alsa to play with m8c, but just how to get alsa to work with chrome.
One barrier I ran into, is that the webgl renderer wouldn't work on chromium/aarch64. It failed in a strange way, the "#connect" button wouldn't show up. So I implemented these changes so the initial URL i setup for the chromium kiosk would default to displayType=old. I also implemented support for specifying the keymap via urlparam as well. Settings specified here will selectively overwrite the default keymap. Additionally, I added a setting to automatically skip the info screen.
My rPi chromium instance can be thus pointed to something like:
I am deploying m8WebDisplay to a raspberryPi-based environment as an alternative to the rPi/m8c stack. I find m8WebDisplay to be more straightforward to customize, and it's browser level abstractions greatly simplify integration with the host. This way, one is not searching for how to get Alsa to play with m8c, but just how to get alsa to work with chrome.
One barrier I ran into, is that the webgl renderer wouldn't work on chromium/aarch64. It failed in a strange way, the "#connect" button wouldn't show up. So I implemented these changes so the initial URL i setup for the chromium kiosk would default to
displayType=old. I also implemented support for specifying the keymap via urlparam as well. Settings specified here will selectively overwrite the default keymap. Additionally, I added a setting to automatically skip the info screen.My rPi chromium instance can be thus pointed to something like: