steno VS qmk_firmware

What I've experimented in the past (none of these lasted very long for me, but hopefully inspirations for you): - stenophone: back front - fistion: back front - clawor - musk (it feels okay pseudo typing on it in a jacket's pocket)

The one feature I’m looking forward to is having the dictionary built in. The Black Pill used here supports adding memory chip; I just need to buy one and figure out how to flash crides/steno firmware on it.

I haven't actually posted to Reddit for a while (other than comments that is), and I thought I should. I've been daily driving these 2 boards for a bit, the Fissure v3.2 and the Fusion. Both boards are fully BLE, and of course following my tradition on using the embedded steno engine.

Simple (and buggy) steno engine on my keyboard

You can actually run the code needed for steno completely in firmware. Check out https://github.com/crides/steno.

Fwiw, that’s a thing, though it’s still in progress. (This says QMK, but there’s def also ZMK work somewhere in there as well.)

Separate wireless controller, see the glue code at [0]

[0]: https://github.com/qmk/qmk_firmware/compare/master...nuphy-s...

If you have a keyboard that runs QMK firmware[0] with the VIA[1] feature enabled[2], then there is a convenient testing app available from the same place you customize your keys [3].

[0] https://qmk.fm/

I made a layout that I'm happy with. Spanish is my native language, so it has characters like the accents and 'ñ', but it's meant to be used for programming as well. Visual Studio uses a lot of Ctrl and Ctrl + Shift shortcuts, so I left them in the same place as the default Corne layout so I can press them both with my pinkie finger. Perhaps some of the ideas are useful to you.

Also, it would be possible to do this for the RP2040. However, it needs some work to get working. but for example: https://github.com/qmk/qmk_firmware/pull/20999

Ok, it's an ST7735, not too different from the ST7789. You should be able to get running by looking at their files in the QMK repo and going from there. You should also check their resources page.

UPDATE: after fluffing around a little bit, I have manged to fix this code: https://github.com/qmk/qmk_firmware/blob/master/keyboards/lily58/keymaps/bongocat_wpm_responsive/keymap.c and flash it successfully - it seems not to be working correctly as the cat is only hanging there and does not respond to the wmp count. If anybody spots anything wrong in the code please let me know!(C is not my language but I am a programmer, I am gonna get at it again over the weekend if I have time left)

For Seniply I've found this implementation for a_dux keyboard: QMK