IIICC VS miryoku

Case was designed by my friend when I released my IIICC, been working on it since.

I would use 2x I2C expander. This way you have 8x8 matrix on each expander and on top of that you can easily add more modules in the future. Just use more expanders. Here you have an example of 3 split keyboard based on I2C expanders.

For a working I2C expander based keyboards you can check my IIIC and Chordie. Sadly you can't get away from writing your own matrix scanning as there's no easy way to make reading I2C expander states in QMK. MCP23017 and MCP23018 have the same register addresses so there's no problem with moving the code between those two.

You can check my code for IIICC. I am scanning 3 I2C expanders to combine the data into one scan result.

Encoders change states following Gray code. There's a moment where A and B pins are all connected to C thus why you are having such issues. Check data sheet for the Output Table. To make it work you will have process those keys on your own and encode it the same way it's done with rotary encoders in QMK. It's easy actually. You can check my code here.

My IIICC is one of them. For making it work you have to write your custom matrix scanning. Take a look at my src it's all there. Let me know if you have any questions.

The IIICC is a three piece split by u/kbjunky (git, easyeda).

You can find it here: https://github.com/kbjunky/IIICC

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.

I’ve learned a lot from Seniply and Miryoku, both designed to take advantage of small keyboards. They both default to Colemak-DH, which is good.