45591ee443
* Layout macro refactor - Renamed KC_KEYMAP to LAYOUT_kc - Renamed KEYMAP to LAYOUT - moved LAYOUT above LAYOUT_kc (Hoping this encourages users to use LAYOUT.) - updated layout macro name in info.json - white space changes for readability * Keymap refactor: default Default keymap now uses `#include QMK_KEYBOARD_H` and LAYOUT macro (from KC_KEYMAP/LAYOUT_kc). Keymap was also refactored to use process_record_user function instead of deprecated action_get_macro from TMK. Also moved LONGPRESS_DELAY and LAYER_TOGGLE_DELAY definitions to config.h. * Keymap refactor: dcompact - Changed chimera_ortho.h include for QMK_KEYBOARD_H - Updated layout name on keymap layers * Coding conventions fix in default keymap * Keymap refactor: gordon - Changed chimera_ortho.h include for QMK_KEYBOARD_H - Removed redundant includes of action_layer.h and process_tap_dance.h (superseded by QMK_KEYBOARD_H) - Removed redundant definitions for KC_NO and KC_TRNS - Updated layout name on keymap layers |
||
|---|---|---|
| .. | ||
| config.h | ||
| keymap.c | ||
| README.md | ||
| rules.mk | ||
DCompact Layout
Dvorak, Layered, Mouse-Enabled, Compact -- Plover coming soon!?!~
See the layout source for the actual layout
Goals
The following are the goals kept in mind when designing the DCompact layout:
- Provide minimal travel distance when typing English or coding
- Consistent muscle memory translation from standard QWERTY
- Stateless typing experience
- OS-agnostic features, macros, and key placement
- Minimize dependence on mouse usage
These are generally all met or balanced within reason. This layout is not intended at all to be a familiar layout for much of anyone (except maybe those who already type in Dvorak) -- this is meant to amplify the best parts of having limited, ortholinear keys with layering.
As Reference Material
If you're reading this hoping to find reference material to implement your own layout, then please feel free to copy over this layout and make edits where you see fit. I removed a lot of the features I felt extraneous to my usage and simplified style where I felt needed. This would hopefully mean that my code should feel like a good base to develop from for those new to QMK.
Remember that settings defined in the layout directory override and merge with those in the keyboard folder
Relevant Links
Contact
Maintainer: Dan