vial-gui VS miryoku

> 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/

I've seen https://github.com/manna-harbour/miryoku but it doesn't appear to be easily modified.

A 75% keyboard still require quite a lot of wrist movement, which is not ideal in your situation. It's better to learn to use layers, you could still have all the function keys and such with a 36 or 34 keys. With with such a small keyboard you don't need to move your wrist while typing. A Corne or even a Ferris Sweep can do the job with a proper keymap, like Miryoku.

If you prefer to have semicolon on Base you'd substitute custom Base, Nav, and Sym layers, swapping semicolon and slash, with https://github.com/manna-harbour/miryoku/discussions/85.

The Miryoku layout [1] has a dedicated number layer which turns the left half into a number pad. Practical (once you get used to it) and portable.

[1] https://github.com/manna-harbour/miryoku

It's understandable if some people would prefer a larger layout. I wouldn't argue people should be using smaller keyboards.

It's "I don't mind moving my hand to hit the key" vs "I don't mind holding down some Fn key to hit the key". (Or with F1-F12 on Macbooks, you need to both hold down a Fn key and move your hand).

For an example of "36 keys ... how", I think the popular miryoku layout is fascinating. https://github.com/manna-harbour/miryoku/tree/master/docs/re... -- Often, mnemonics for particular keys aren't all that complicated.

Except for those who use Miryoku, which is not optimized for software development, probably every single person here will have its own custom keymap.

The keyboard on the other desk is a wireless Corne low profile kit I built up a while back using a couple nice!nano controllers and their low power display too. For general typing I don't have much of a problem going back and forth between the two, but the Corne is only 34 keys and I use a complex layout called Miryoku to get access to most symbols and functions I have by default on my 360.