I wanted to check in what progress has been made on getting QMK up and running on the Pocket Reform.
If some one’s working on it, I’m willing to contribute. If no one’s working on it, I’m willing to get the party started.
I don’t know the QMK system, but I’m a slow-but-thorough coder, and I’ll make it happen if help is needed on this!
At the moment I have not heard of anyone working on making the pocket keyboard compatible with QMK. If you’ve had a chance to check out the source you’ve probably noticed the pocket keyboard has a few unusual feature requirements compared to the average QMK compatible keyboard - the keyboard is responsible for rendering the small OLED interface, and talking to the system controller to display information like battery status - as well as send the command to power the pocket on or off.
All should be theoretically possible, but might be more involved than QMKs regular board setup process which is normally through configuration files that define pinouts and mappings, with code for defining custom input hooks.
QMK support would be great, being able to launch QMK VIA or the other configuration tools to customize the layout or RGB backlight without reflashing the board is very convenient.
Huh. Sounds far more involved than I initially thought, which explains why this hasn’t been done yet.
I’ll reach out to folks who know more and see what I can learn.
Thanks for laying this all out for me!
maybe it would be easier to port qmk features into pocket keyboard firmware. For example, @abbreviatedman what features are you using? I believe the most obvious would be to define more than two layers?
You do not need a custom firmware for more than two layers. I’m using the Neo2 keyboard layout which gives me six layers on any keyboard (including the pocket) without modifying the firmware.
I mean adding layers in QMK is pretty easy and kind of abstracted from the main code. While in pocket firmware you have to touch more places to add something like raise/lower or second hyper key.
Also it would be nice to have some more generic caps. For example I’d rather have something like circle and triangle instead of AGR or =+ with -_.