qmk_firmware VS keyboards

I agree that reduced finger movement is a crucial step in achieving typing efficiency. This is nicely solved by mod tap modifiers in QMK/ZMK[1] where key acts as a char when tapped and as a layer while pressed.

[1]: https://github.com/qmk/qmk_firmware/blob/master/docs/mod_tap...

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)

QMK and VIA out-of-the-box \o/

which doesn't aspire confidence in that happening since even though boards like the JRIS65 and JRIS75 tout "QMK/VIA" support, there are no entries in both, the qmk/firmware repo and the the-via/keyboards repo, and no PRs were raised in both to add support for them. Since the source code for those boards wasn't anywhere to be found, that in of itself was a violation of the GPL 2.0/3.0 License, which QMK and VIA abide by.

for any issues with VIA, you should open issues here: https://github.com/the-via/keyboards/issues

My firmware has the `VIA_ENABLE = yes` on its rules.mk (on my keymap folder), and there's also the via folder on the project which also has it enabled. Using the official preonic keymaps.json on the Design tab of VIA also doesn't work. That makes me think that I'm missing some kind of board identification on my code? QMK Toolbox recognizes the device as a Preonic.

QMK and Need your firmware In the documentation https://docs.qmk.fm/#/keycodes\_basic this is the KC_CAPS_LOCK or KC_CAPS key For ease of copy-paste, look for text mentioning these words and turning on the indication in the firmware of other keyboards on https://github.com/qmk/qmk\_firmware/tree/master/keyboards https://github.com/the-via/keyboards you can start with Keychron keyboards

Create an Android app for https://github.com/the-via/keyboards

Hi y'all. This basically a little PSA that's meant to compliment u/cosmic_c 's post about adding support for the GMMK 2. Although that PR was for the 96% ANSI variant of the GMMK 2, my PR adds support for the ISO variant of the 96%, and both variants (ANSI and ISO) for the 65% version.

The JSON you should use for the design tab to verify is this one. If you can't download it just copy/paste the code into a txt file then change the extension to .json and load it up.

Source.