@eeropic You can’t claim the Interfaxes because they are exclusively claimed by the OS. In addition to this there is also a blocklist for various devices in the chromium source: https://t.co/DAEeJL2rUc
The WebHID API allows you to interact with so many devices. Some examples I build to control hardware build into your (newer) mac:
Force Trackpad: https://t.co/kcnlOrW5Mt
Keyboard Backlight: https://t.co/XT3hMWGH9Z
Ambient Light Sensor: https://t.co/VStS4dtNMj
Over the weekend @FWeinb added battery support too! The simulator really shines here, making it much faster to test battery status rendering and behaviors than is possible on hardware.
🎉🆕Thanks to @FWeinb, the Moddable SDK now has an M5Paper simulator!
Quickly develop, refine, and test your project's UX on your computer before deploying to M5Paper. The simulator supports touch screen, buttons, network, and more! #Moddable#JavaScript#ePaper#ESP32#M5Stack
@mjackson@jlongster Thought about that one too. But than again combine that with a FS storage API and you make IDB just overhead. (e.g webkitFileSystem)
@quicksave2k It did work, but it stoped since macOS 12 no idea why 🤷♂️. Code is a huge mess, nerver used swift before might put it on GitHub but no idea how useful this is 😅.
@tomayac This is all running inside the native extension handler. I am using the web extension to inject a script in the user context and communicate from there (via the content/background page) with the native part of the extension. I posted some more details as replies to the tweet.
It would be great to be able to programatically open a popup from within the content/background page without a user interaction. Currently I have to resort to injecting an iframe into the current page for the bluetooth device chooser.
Natively backed object are currently only cleared when the tab is reloaded. This should be done using a FinalizationRegistry.
There might be a memory limit for a native handler, never hit.
The bluetooth tree (event bubbling) isn’t worth it I think. (https://t.co/UgLx8sufiK)