Workman VS qmk_configurator

Just to add a bit of data to the ergonomics claims (of which I find many people are skeptical):

https://workmanlayout.org/#tests-using-popular-books

Now, this is a site extolling the virtues of yet another layout, so feel free to take it with a grain of salt, but the methodology seems sound to me. (Though I used Workman in the past, I've since moved to Colemak due to a combination of it being built-in to Apple OSs and my dislike of the "ly" digram being on the same finger in Workman, plus some other factors.)

Even though Dvorak is the "least efficient" of the three QWERTY alternatives measured, it's still over a 40% reduction in finger travel distance compared to QWERTY. "Distance traveled" is obviously not the sole factor in ergonomics, but it's equally obviously a big one.

Workman [0] was designed to be used on an ortho keyboard, though it is also usable on a normal keyboard. I suppose it's tricky to design for many modern features as they are not yet standardised between keyboards.

[0] https://workmanlayout.org/

Just take a look at the test results that the author of workman keyboard layout made: https://workmanlayout.org/

You might also find https://web.archive.org/web/20130512065149/http://www.andong... interesting. The theory is that since you only ever have a space after a comma, you can use it as a dead key, and just have ", " output ", ". That then frees all the other letter combos to be whatever key you want.

There are other keyboard layouts out there with the same concept too: https://github.com/workman-layout/Workman/tree/master/mac#wo...

The layout used is Workman US (programmer variant).

In my experience it does become harder to type on staggered keyboards unless you're continuing to do it regularly. You may need to relearn to do that. Same deal with continuing QWERTY usage.

VIA is proprietary and not really an official QMK thing (QMK is free software). There is also Vial[0] which is free software if you want a GUI, and the QMK configurator[1] web app (but this lacks some features like enabling mouse keys or NKRO).

Lastly I want to add that Workman[2] may be preferable to Colemak Mod-DH. Rather than an attempt to fix major issues in Colemak like Mod-DH, it's a whole new layout that avoided the issues from the start. I have also heard from some that it had ortholinear and columnar stagger boards in mind with its design.

I type on a Pinky4[3] keyboard that I assembled from a kit. More keys than your keyboard, but a similar idea. I was coming from a 60% and wanted a similar amount of keys. I've been quite happy with it.

[0] https://get.vial.today/

[1] https://config.qmk.fm/#/

[2] https://workmanlayout.org/

[3] https://github.com/tamanishi/Pinky4

read these thoughts behind the invention of workman layout

I was checking miryoku to use it when I get the Defy, or at least try it. But I don't quite get the part of "workman as alphas". I saw workman, but which ones are the alphas? The numbers?

Handedness? Not sure what do you mean by that. I'm using the config.qmk.fm website for the key configuration

I'm using https://config.qmk.fm/ to create a firmware for Iris rev.7 including mouse keys, and then use QMK toolbox on MacOs to flash the firmware, but while everything else works in all layers, the mouse keys do not move the cursor at all. Any ideas?

How can I use https://config.qmk.fm/ to map certain specific keys such as € or @, that are not direct or available in the framework ?

"documentation": "\"This file is a QMK Configurator export. You can import this at . It can also be used directly with QMK's source code.\n\nTo setup your QMK environment check out the tutorial: \n\nYou can convert this file to a keymap.c using this command: `qmk json2c {keymap}`\n\nYou can compile this keymap using this command: `qmk compile {keymap}`\"\n",

I didn't want to really start another thread because the question I have is so similar I think. I was somehow able to use config.qmk.fm to map a really generic colemak-dh keymap, I read the qmk noob section so I looked up how to use github/git completely lost, I have the Corne 3x6 I didn't build it I purchased it secondhand so Ive been doing some research on ergonomic mapping Miryoku generally seems to be a solid choice

I'd recommend you jump on QMK configurator, select the Charybdis of desired size, and start making your layers 😉

My keyboard was working fine prior to flashing. I have a solderable dz60 (ATMEGA32U4). I tried to flash it with firmware downloaded from config.qmk.fm (selected dz60 as keyboard). It said successful on qmk toolbox, but my caps lock light is stuck on and no button presses work. The esc + plugin option to reset stopped working, so I had to take the pcb out to press the reset button. Still not working after flashing with default firmware downloaded from config.qmk.fm. I tried flashing it with dz60 via firmware, and it gets recognized in via now, but still not working. After hours of troubleshooting of it not working, I flashed it with dz60rgb_v2 just to see what happens, and then very few of the keys work after a few presses (but they're mismapped), and the caps lock light goes off. I've tried the keyboard on different devices, and on both of them it gets recognized as a keyboard, but the caps lock light is still stuck on and no presses register.

Let's suppose that the issue is the diode orientation. I'm a total QMK newbie -- how could I swap between ROW2COL and COL2ROW at the firmware level? On the QMK Github I see instructions for modifying the appropriate headers. But when I generate my config from config.qmk.fm I only get a single .hex file. Thanks again!

Probably the easiest way to do it by clicking buttons is to use config.qmk.fm.

For non-ez keyboards, a similar tool is the QMK Configurator. See this documentation page or the video tutorial for an overview.