_/qmk_firmware
1
0
Fork 0
Code Releases Activity
qmk_firmware/keyboards/minidox/keymaps/norman/readme.md
Torben Hoffmann d3f3da5112 Norman layout for the minidox keyboard (#5747) 
* Norman layout with Lower and Raise layers working

* Add keymap_extra def for Norman layout
* Re-org'ed the modifiers as explained in the Readme
* Corrected colour legend for KLE that the Readme links to

* Use #pragma once in header file

* Use pragma once and move user config to config.h

* Move definitions to the right file and correct link in Readme

* Move def of NM_COLN to the logical place in header file

* Add sendstring_norman.h for when the laptop layout is not QWERTY

* Update quantum/keymap_extras/sendstring_norman.h

Co-Authored-By: lehoff <torben.lehoff@gmail.com>
2019-05-09 22:12:11 -07:00

2.1 KiB
Raw Blame History

Minidox Norman Layout by LeHoff

Based on the QWERTY layout created by Khitsule. lehoff

KLE link

Layers

Layer Legend
Base Top left (black)
Lower Bottom right (red)
Raise Top right (orange)
Adjust Front print

Features

  • Raise/lower layers focus first on one-handed use
  • Numpad on right hand with raise layer
  • Navigation on left hand with lower layer (ESDF)
    • D refers to desktop left/right on Win 10 (win+ctrl+left/right)
  • Heavy use of hold/tap dual function keys - from left to right:
    • Cmd/Enter
    • Raise/Esc
    • Shift/Backspace
    • Ctrl/Space
    • Lower/Tab
    • Alt/Enter

Modifier Placement Rationale

There are several major driving forces at play:

  • I use MacOS.

  • I'm Danish so the Alt and Shift-Alt layers in MacOS simply have to work.

  • I use Vim for coding.

  • I use org-mode in Emacs to keep track of my time.

  • Space is on the right hand side because I almost exclusively use my right hand thumb for space.

  • Cmd is on the left since I often use Cmd+click to open a link in a new tab in Safari.

  • Due to my usage of Vim Esc got a spot on the modifier row.

  • Tab is on the right to enable easy navigation between winows with Cmd+Tab.

  • Shift is on the left since org-mode uses Ctrl+arrows to manipulate task state quickly, and since the arrow keys are activated using Lower (which has been moved to the right) and S, E, T, and D, it works well that way.

  • Ctrl is on the right since Ctrl+<0-9> is used in MacOS to switch between spaces.

  • Enter is on both sides since Enter is often used together with all of the modifiers. E.g., Cmd+Enter to send mails in most situations, but Ctrl+Enter is used in Emacs to create a new task in org-mode.

This means that arrows and digits are being modified from the other hand, which could be bad for gaming, so if you're into that you might want to re-think a few things, but in that case you are probably using a Windows machine and then there are other constraints you have to deal with.