vial-gui VS keyboards

> made the customization much more comfy, without the need of recompile the fw

Get someone to write a profile for https://get.vial.today/ support.

> add a damn service to print easily custom keycaps

https://www.wasdkeyboards.com/custom-text-cherry-mx-keycaps....

> please STOP making cherry, OSA etc profiles

They are making them because people keep buying them. Turns out most people actually like typing on them.

Less drastic than reflashing could be to reset to factory defaults. Note that this will wipe out any Via/Vial configuration and other configuration (e.g., RGB mode, RGB colour settings, and NKRO setting).

At all possible? Yes, but probably not from Via. I don't know about Vial (it requires special versions of the keyboard firmware).

This is the second one I’ve built but it’s for someone else, this is too many keys for me lol. The case is printed in a super nice matte green then it uses Boba U4Ts that sound and feel super nice. The keycaps are just a placeholder while I test the board, I’m certain they’ll put something that matches. The board is fully compatible with Vial and runs on a USB-C Pro Micro.

VIA doesn't have any support for configuring tap-dances, nor does the QMK Configurator. Your two options are either using VIAL https://get.vial.today/. Or utilizing the feature directly in QMK source code https://docs.qmk.fm/#/feature_tap_dance.

This firmware update will make it compatible with open source software called Vial... https://get.vial.today/

This was my exact scenario, and I ended up flashing my keyboard with Vial QMK. It’s a Via-like interface that allows you to edit additional QMK settings like the tap-hold timings.

resources I've tried: https://docs.qmk.fm/#/newbs_getting_started https://get.vial.today/

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.