Fork of https://github.com/OneDeadKey/arsenik containing my own dragon config
|
11 tháng trước cách đây | |
---|---|---|
img | 11 tháng trước cách đây | |
kanata | 11 tháng trước cách đây | |
qmk | 11 tháng trước cách đây | |
.gitignore | 11 tháng trước cách đây | |
LICENSE | 1 năm trước cách đây | |
README.md | 11 tháng trước cách đây |
Configure your keyboard (even if it is not programmable) with a beginner-friendly, Miryoku-like approach to minimize finger movements!
You can choose your options:
Bring the keys to your fingers, rather than moving your fingers to the keys!
This is how modern ergonomic keyboards work — e.g. Planck, Atreus, Corne, Ferris… The goal here is to propose an approach that works with any keyboard, including your laptop’s.
Unlike Miryoku which requires 6 thumb keys, Arsenik has been designed to work with standard ANSI/ISO/laptop keyboards, leveraging the spacebar and the two Alt/Cmd keys.
Adjusting to compact keyboard layouts isn’t easy, but Arsenik is designed for a step-by-step approach.
If you’re new to mod-taps, we suggest to start by adding the “layer-tap” option where only the thumbs are affected:
Having Backspace and Enter under the thumbs is enough to reduce the pinky fatigue very significantly. And using the Symbol and Navigation layer further reduces hand and finger movements.
When you are familiar with mod-taps, it’s time to enable them on the homerow with the “hrm” variants:
This is a very basic variant of the Miryoku principle: one layer on each thumb key, and symmetrical modifiers on the homerow.
It uses 4 layers (instead of 3 for Arsenik), which makes it a natural fit for 34-key keyboards like the Ferris.
This Navigation layer has a few empty slots on purpose, so you can add our own keys or layers.
In Symbol mode, pressing the left thumb key brings up the NumRow layer:
Even on keyboards that do have a physical number row, this NumRow
layer can be interesting to use in order to minimize finger movements further
more. And it makes it easier to mix symbols with numbers (e.g. [0]
).
Non-programmable keyboards are supported through kanata.
The QMK implementation is a bit different:
In fact, this is what I ended up with for my beloved Ferris in the first place, and Arsenik/Selenium is an attempt to fit most of this magic into my laptop keyboard.
# from the `qmk_firmware` root:
make ferris/0_2/bling:1dk:flash
Other desktop implementations (kmonad, keyd…) would be nice to see as well.
Programmable keyboards should be trivial to configure with QMK, ZMK, Kaleidoscope, etc.