* mitosis:datagrok: improved tenkey layout; changelog + more in README
* mitosis:datagrok enable audio!
* mitosis:datagrok: underscore on right shift, rearrange some symbols
* mitosis:datagrok: add more descriptions to readme
* mitosis:datagrok: abuse space cadet to get equivalent of RSFT_T(KC_UNDS)
pull/3403/head
Michael F. Lamb7 years agocommitted byDrashna Jaelre
- Emphasis on momentary modifiers, all usable from either hand, arranged
- Emphasis on momentary modifiers, all usable from either hand, arranged symmetrically, but left/right distinguishable by the OS.
symmetrically, but distinguishable left/right by the OS. Shift, Red
Shift, Red ("Lower"), Blue ("Raise"), Super ("Windows"), Meta ("Alt"), Hyper (actually Henkan/Muhenkan).
("Lower"), Blue ("Raise"), Super ("Windows"), Meta ("Alt"), Hyper.
I'm going for a [Space Cadet](https://en.wikipedia.org/wiki/Space-cadet_keyboard) aesthetic;
I want a keyboard that can (even just in theory) make use of all the bucky bits my operating system can support.
- Red and Blue are used to momentary-enable (like a shift key) one of three layers:
- Red and Blue are used to momentary-enable (like a shift key) one of three layers:
@ -14,80 +11,211 @@
- Blue: Numbers layer
- Blue: Numbers layer
- "Purple" (both Red and Blue): Functions layer
- "Purple" (both Red and Blue): Functions layer
- The base layer is QWERTY. A slight variant of [Workman][] may be toggled-on.
- The base layer is QWERTY.
A slight variant of [Workman][] may be toggled using `Red`+`Blue`+`Z`.
- Emphasis on minimizing hand travel, so as not to lose orientation with
- Minimize hand travel, so as not to lose orientation with home row.
homerow.
- Paired programming symbols (braces, brackets, parentheses) are arranged
symmetrically in the symbols layer.
- `?` and `!` are moved to take the place of `<` and `>`. Rationale: unmodded
- `?` and `!` are moved to take the place of `<` and `>`. Rationale: unmodded
and shifted keys should be for prose, while symbols useful for programming
and shifted keys should be for prose, while symbols useful for programming
should be colocated on their own layer.
should be colocated on their own layer.
- No OS keymap modification required.
- Key positions chosen for mnemonics.
For example, you can distinguish between alphanumeric numerals and keypad numerals, but they occupy the same key positions.
## Design notes
## Layout Images
- **I use an 8Mhz Pro Micro.** If you want to use this keymap with the standard
16Mhz Pro Micro specified in the Mitosis design:
- Remove the lines in `rules.mk` mentioning `F_CPU` and `F_USB`.
Base layer. Notes:
- Remove the lines in `config.h` mentioning `SERIAL_UART_BAUD`.
- customized comma and period, which have exclamation point and question mark on their shift layer.
- tap right-shift for underscore
- Workman layout
- I'm learning a new physical key placement, so I might as well go all out
Red layer. Intended for common navigation and programming symbols. Notes:
and use an optimal non-QWERTY layout.
- symmetric layout of paired braces/brackets/slashes for easier memorization
- arrows placed directly on home position
- I like the way Workman feels and some of its advantages over Colemak.
Unfortunately, it was designed using a weighting system based on a
standard column-staggered keyboard so is probably not as optimal as one
Blue layer. Intended for "number pad." Notes:
could achieve on an ergonomic board like the Mitosis. Maybe run an
- Keycodes generated for numbers, enter key, and mathematical symbols are from the alphanumeric keys, not keypad. This way they are not influenced by the state of Num Lock. If you want to send the keypad equivalents, just use Red and Blue modifiers simultaneously.
optimizer routine after I determine good values for key difficulty on the
Michael F. Lamb
7 years ago
committed by