aboutsummaryrefslogtreecommitdiff
path: root/keyboards/ergodox_ez/keymaps/algernon/readme.md
diff options
context:
space:
mode:
Diffstat (limited to 'keyboards/ergodox_ez/keymaps/algernon/readme.md')
-rw-r--r--keyboards/ergodox_ez/keymaps/algernon/readme.md207
1 files changed, 83 insertions, 124 deletions
diff --git a/keyboards/ergodox_ez/keymaps/algernon/readme.md b/keyboards/ergodox_ez/keymaps/algernon/readme.md
index 6b7e8fa2e..2312dc59e 100644
--- a/keyboards/ergodox_ez/keymaps/algernon/readme.md
+++ b/keyboards/ergodox_ez/keymaps/algernon/readme.md
@@ -1,27 +1,28 @@
1<!-- -*- mode: markdown; fill-column: 8192 -*- -->
2
1algernon's layout 3algernon's layout
2======================= 4=======================
3 5
4This is an unconventional layout for the ErgoDox EZ. For more details about the 6This is an unconventional layout for the ErgoDox EZ. For more details about the history of the layout, see my [blog posts about my ErgoDox journey][blog-ergodox].
5history of the layout, see my
6[blog posts about my ErgoDox journey][blog-ergodox].
7 7
8 [blog-ergodox]: https://asylum.madhouse-project.org/blog/tags/ergodox/ 8 [blog-ergodox]: https://asylum.madhouse-project.org/blog/tags/ergodox/
9 9
10Some of the things in the layout only work when one uses Spacemacs and GNOME 10Some of the things in the layout only work when one uses Spacemacs and GNOME under Linux. Your mileage may vary.
11under Linux. Your mileage may vary.
12 11
13## Table of Contents 12## Table of Contents
14 13
15* [Layouts](#layouts) 14* [Layouts](#layouts)
16 - [Base layer](#base-layer) 15 - [Base layer](#base-layer)
17 - [Experimental layer](#experimental-layer) 16 - [ADORE layer](#adore-layer)
18 - [Hungarian layer](#hungarian-layer) 17 - [Hungarian layer](#hungarian-layer)
19 - [Navigation and media layer](#navigation-and-media-layer) 18 - [Navigation and media layer](#navigation-and-media-layer)
20 - [One-handed layer](#one-handed-layer) 19 - [One-handed layer](#one-handed-layer)
21 - [Steno layer](#steno-layer) 20 - [Steno layer](#steno-layer)
22 - [LED states](#led-states) 21 - [LED states](#led-states)
22* [Tools](#tools)
23 - [Heatmap](#heatmap)
23* [Building](#building) 24* [Building](#building)
24 - [Using on Windows](#using-on-windows) 25 - [Using on Windows](#using-on-windows)
25* [Changelog](#changelog) 26* [Changelog](#changelog)
26* [License](#license) 27* [License](#license)
27 28
@@ -31,133 +32,98 @@ under Linux. Your mileage may vary.
31 32
32[![Base layer](images/base-layer.png)](http://www.keyboard-layout-editor.com/#/gists/28f7eb305fdbff943613e1dc7aa9e82b) 33[![Base layer](images/base-layer.png)](http://www.keyboard-layout-editor.com/#/gists/28f7eb305fdbff943613e1dc7aa9e82b)
33 34
34At its core, this is a Dvorak layout, with some minor changes. The more 35At its core, this is a Dvorak layout, with some minor changes. The more interesting parts are how certain keys behave:
35interesting parts are how certain keys behave: 36
36 37* The keys on the number row double as function keys, when held for a bit longer than an usual tap. This allows me to use the function keys without having to switch layers.
37* The keys on the number row double as function keys, when held for a bit longer 38* The `Shift`, `Alt`, and `Control` modifiers are one-shot. When tapped, they are considered active for the next key press only. When double tapped, they toggle on, until a third, single tap sometime later. When held, they act as expected. My usual pattern is that I use these for the next keypress only, so this behaviour is perfect. If I need them held, I'll just double-tap.
38 than an usual tap. This allows me to use the function keys without having to 39* The `GUI` key is special, because when I double-tap it, it sends `GUI + w`, which pops up an application selector. It also switches to a one-shot layer, where the number row on the left half turns into app selector macros, for the most common things I usually want to switch to. Otherwise it behaves as on a normal layout.
39 switch layers. 40* The `ESC` key also doubles as a one-shot cancel key: if tapped while any of the one-shot modifiers are in-flight (as in, single-tapped, and not expired yet), it cancels all one-shot modifiers. It also cancels the **Hun** layer, if active. Otherwise it sends the usual keycode.
40* The `Shift`, `Alt`, and `Control` modifiers are one-shot. When tapped, they 41* The **Media** and **Hun** layer keys are one-shot, the **1Hand** and **STENO** keys are toggles.
41 are considered active for the next key press only. When double tapped, they 42* When holding any of the **Arrow** layer keys, the arrow layer activates while the layer key is held. Tapping the key produces the normal key.
42 toggle on, until a third, single tap sometime later. When held, they act as
43 expected. My usual pattern is that I use these for the next keypress only, so
44 this behaviour is perfect. If I need them held, I'll just double-tap.
45* The `GUI` key is special, because when I double-tap it, it sends `GUI + w`,
46 which pops up an application selector. It also switches to a one-shot layer,
47 where the number row on the left half turns into app selector macros, for the
48 most common things I usually want to switch to. Otherwise it behaves as on a
49 normal layout.
50* The `ESC` key also doubles as a one-shot cancel key: if tapped while any of
51 the one-shot modifiers are in-flight (as in, single-tapped, and not expired
52 yet), it cancels all one-shot modifiers. It also cancels the **Hun** layer, if
53 active. Otherwise it sends the usual keycode.
54* The **Media**, **Arrow**, and **Hun** layer keys are one-shot, the **1Hand**
55 and **STENO** keys are toggles.
56* Toggling the **Arrow** layer toggles between the cursor arrows and the paging
57 keys on the bottom row.
58* Tapping the `:` key once yields `:`, tapping it twice yields `;`. 43* Tapping the `:` key once yields `:`, tapping it twice yields `;`.
59* The **Lead** key allows me to type in a sequence of keys, and trigger some 44* The **Lead** key allows me to type in a sequence of keys, and trigger some actions:
60 actions: 45 - `LEAD u` enters unicode input mode, by sending the GTK+ key sequence that does this.
61 - `LEAD u` enters unicode input mode, by sending the GTK+ key sequence that
62 does this.
63 - `LEAD l` uses the unicode input method to enter a `λ`. 46 - `LEAD l` uses the unicode input method to enter a `λ`.
64 - `LEAD s` does a lot of magic to type in a shruggie: `¯\_(ツ)_/¯` 47 - `LEAD s` does a lot of magic to type in a shruggie: `¯\_(ツ)_/¯`
65 - `LEAD y` types `\o/`. 48 - `LEAD y` types `\o/`.
66 - `LEAD w m` maximises the currently focused window. 49 - `LEAD w m` maximises the currently focused window.
67 - `LEAD e` makes the [experimental layer](#experimental-layer) the default. 50 - `LEAD a` makes the [ADORE layer](#adore-layer) the default.
68 - `LEAD v` prints the firmware version, the keyboard and the keymap. 51 - `LEAD v` prints the firmware version, the keyboard and the keymap.
52 - `LEAD d` toggles logging keypress positions to the HID console.
69 53
70## Experimental layer 54## ADORE layer
71 55
72[![Experimental layer](images/experimental-layer.png)](http://www.keyboard-layout-editor.com/#/gists/6ff50bf71248e05aab5b3fec4fae3d08) 56[![ADORE layer](images/adore-layer.png)](http://www.keyboard-layout-editor.com/#/gists/45681a17453d235925b6028dd83bf12a)
73 57
74While using the standard Dvorak layout, I encountered a number of 58While using the standard Dvorak layout, I encountered a number of inconveniences, and on this layer, I am playing with ideas to make the layout feel better. Initially, it was based on [Capewell-Dvorak][cpd], but that too, had shortcomings I was not happy with. So now this is something inbetween, with own observations thrown in. How it works out in the long run remains to be seen.
75inconveniences, and on this layer, I am playing with ideas to make the layout
76feel better. Initially, it was based on [Capewell-Dvorak][cpd], but that too,
77had shortcomings I was not happy with. So now this is something inbetween, with
78own observations thrown in. How it works out in the long run remains to be seen.
79 59
80 [cpd]: http://www.michaelcapewell.com/projects/keyboard/layout_capewell-dvorak.htm 60 [cpd]: http://www.michaelcapewell.com/projects/keyboard/layout_capewell-dvorak.htm
61
62Based on a week and a half of typing, the keys were rearranged, and the home row neatly spelled out **ADORE**, that gave the layout its name.
81 63
82## Hungarian layer 64## Hungarian layer
83 65
84[![Hungarian layer](images/hun-layer.png)](http://www.keyboard-layout-editor.com/#/gists/b160f6ec90d58c127c114c89f66e9dc9) 66[![Hungarian layer](images/hun-layer.png)](http://www.keyboard-layout-editor.com/#/gists/b160f6ec90d58c127c114c89f66e9dc9)
85 67
86On this layer, the accented characters are at the same position as their base 68On this layer, the accented characters are at the same position as their base variant. For some, which can have other diatribes, the long one is on top, short's on bottom. Tapping any of the accented characters takes us back to the base layer.
87variant. For some, which can have other diatribes, the long one is on top,
88short's on bottom. Tapping any of the accented characters takes us back to the
89base layer.
90 69
91## Navigation and media layer 70## Navigation and media layer
92 71
93[![Navigation and media layer](images/nav-n-media-layer.png)](http://www.keyboard-layout-editor.com/#/gists/c59c453f9fe1a3238ba1494e7e5c6892) 72[![Navigation and media layer](images/nav-n-media-layer.png)](http://www.keyboard-layout-editor.com/#/gists/c59c453f9fe1a3238ba1494e7e5c6892)
94 73
95This layer is primarily for navigating with the cursor or the mouse, and some 74This layer is primarily for navigating with the cursor or the mouse, and some media things.
96media things.
97 75
98## One-handed layer 76## One-handed layer
99 77
100[![One-handed layer](images/one-handed-layer.png)](http://www.keyboard-layout-editor.com/#/gists/edff2495135955b8963198dace7f7ece) 78[![One-handed layer](images/one-handed-layer.png)](http://www.keyboard-layout-editor.com/#/gists/edff2495135955b8963198dace7f7ece)
101 79
102The one-handed layer is used in situations where the right hand is occupied, by 80The one-handed layer is used in situations where the right hand is occupied, by mousing around, for example. Tapping the `OTHER` key switches which side is active. For the most part, keys remain in their usual position. When the right half is active, keys are mirrored to the left half.
103mousing around, for example. Tapping the `OTHER` key switches which side is
104active. For the most part, keys remain in their usual position. When the right
105half is active, keys are mirrored to the left half.
106 81
107The differences are as follows: 82The differences are as follows:
108 83
109* The `ESC` key has been moved to the bottom row, so the `OTHER` key is easier 84* The `ESC` key has been moved to the bottom row, so the `OTHER` key is easier to tap.
110 to tap. 85* Most keys on the thumb cluster now have dual uses, and these do not change when switching sides:
111* Most keys on the thumb cluster now have dual uses, and these do not change 86 - The `Space`/`Backspace` key sends `Space` on tap, `Backspace` when held for longer than a normal tap.
112 when switching sides:
113 - The `Space`/`Backspace` key sends `Space` on tap, `Backspace` when held
114 for longer than a normal tap.
115 - The `Enter`/`Shift` key sends `Enter` on short-tap, `Shift` on long-tap. 87 - The `Enter`/`Shift` key sends `Enter` on short-tap, `Shift` on long-tap.
116* The `Apps`/`BASE` key can be used to go back to the base layer, by 88* The `Apps`/`BASE` key can be used to go back to the base layer, by long-tapping it. A short-tap will send the `App` key, as usual.
117 long-tapping it. A short-tap will send the `App` key, as usual.
118 89
119## Steno layer 90## Steno layer
120 91
121[![Steno layer for Plover](images/steno-layer.png)](http://www.keyboard-layout-editor.com/#/gists/401ef9a84369e47c57f9aedcf0a0d667) 92[![Steno layer for Plover](images/steno-layer.png)](http://www.keyboard-layout-editor.com/#/gists/401ef9a84369e47c57f9aedcf0a0d667)
122 93
123This is to be used with [Plover](http://www.openstenoproject.org/plover/), 94This is to be used with [Plover](http://www.openstenoproject.org/plover/), nothing really fancy here. The **STENO** key toggles the layer on and off, and sends the toggle command to Plover too.
124nothing really fancy here. The **STENO** key toggles the layer on and off, and
125sends the toggle command to Plover too.
126 95
127## LED states 96## LED states
128 97
129The primary purpose of the LEDs is to show the modifier status, a secondary, to 98The primary purpose of the LEDs is to show the modifier status, a secondary, to show which layer is active. Each modifier, `Shift`, `Alt` and `Control` each have their designated LEDs: the *red*, *green* and *blue*, respectively. When a modifier is in a one-shot state, the respective LED will turn on with a dimmer light. If the modifier is toggled on, the brightness of the LED turns full.
130show which layer is active. Each modifier, `Shift`, `Alt` and `Control` each
131have their designated LEDs: the *red*, *green* and *blue*, respectively. When a
132modifier is in a one-shot state, the respective LED will turn on with a dimmer
133light. If the modifier is toggled on, the brightness of the LED turns full.
134 99
135For the layers, the following rules apply: 100For the layers, the following rules apply:
136 101
137* When the [Experimental layer](#experimental-layer) is toggled on, LEDs will 102* When the [ADORE layer](#adore-layer) is toggled on, LEDs will light up from left to right in a sequence, then turn off. When the layer is toggled off, the LEDs light up and turn off in the other direction. No LEDs are on while the layer is active.
138 light up from left to right in a sequence, then turn off. When the layer is 103* When the [Hungarian layer](#hungarian-layer) is active, the *green* and *blue* LEDs are on.
139 toggled off, the LEDs light up and turn off in the other direction. No LEDs 104* When the [Navigation and media layer](#navigation-and-media-layer) is active, the *red* and *green* ones are on.
140 are on while the layer is active. 105* When the [One-handed layer](#one-handed-layer) is active, the *green* LED is on and bright, and either the *red* or the *blue* one is going to slowly blink, depending on the currently active side.
141* When the [Hungarian layer](#hungarian-layer) is active, the *green* and *blue*
142 LEDs are on.
143* When the [Navigation and media layer](#navigation-and-media-layer) is active,
144 the *red* and *green* ones are on.
145* When the [One-handed layer](#one-handed-layer) is active, the *green* LED is
146 on and bright, and either the *red* or the *blue* one is going to slowly
147 blink, depending on the currently active side.
148* For the [Steno layer](#steno-layer), all LEDs will be turned on. 106* For the [Steno layer](#steno-layer), all LEDs will be turned on.
149 107
150Unless noted otherwise, the layers use a dim light for the LEDs, while modifiers 108Unless noted otherwise, the layers use a dim light for the LEDs, while modifiers use a stronger one, and modifiers override any layer preferences. For example, when on the one-handed layer, with the left side active (*red* light blinking), if `Shift` is on, the *red* light will be constantly on.
151use a stronger one, and modifiers override any layer preferences. For example, 109
152when on the one-handed layer, with the left side active (*red* light blinking), 110# Tools
153if `Shift` is on, the *red* light will be constantly on. 111
112## Heatmap
113
114When the keypress logging functionality is enabled (by `LEAD d`), the keyboard will output a line every time a key is pressed, containing the position of the key in the matrix. This allows one to collect this information, and build analytics over it, such as a heat map, including dead keys too.
115
116Included with the firmware is a small tool that can parse these logs, and create a heatmap that one can import into [KLE][kle]. To use it, simply point `tools/log-to-heatmap.py` to a base layout file (one is included in the `tools/` directory), and the key position log. The latter one can create by running `hid-listen`, and redirecting its output to a file.
117
118 [kle]: http://www.keyboard-layout-editor.com/
119
120The generated heatmap looks somewhat like this:
121
122 ![Heatmap](images/heatmap.png)
154 123
155# Building 124# Building
156 125
157To make my workflow easier, this layout is maintained in 126To make my workflow easier, this layout is maintained in [its own repository][algernon:ez-layout]. To build it, you will need the [QMK][qmk] firmware checked out, and this repo either checked out to something like `keyboards/ergodox_ez/algernon-master`. One way to achieve that is this:
158[its own repository][algernon:ez-layout]. To build it, you will need the
159[QMK][qmk] firmware checked out, and this repo either checked out to something
160like `keyboards/ergodox_ez/algernon-master`. One way to achieve that is this:
161 127
162 [algernon:ez-layout]: https://github.com/algernon/ergodox-layout 128 [algernon:ez-layout]: https://github.com/algernon/ergodox-layout
163 [qmk]: https://github.com/jackhumbert/qmk_firmware 129 [qmk]: https://github.com/jackhumbert/qmk_firmware
@@ -170,9 +136,7 @@ $ git clone https://github.com/algernon/ergodox-layout.git \
170$ make KEYBOARD=ergodox_ez KEYMAP=algernon-master 136$ make KEYBOARD=ergodox_ez KEYMAP=algernon-master
171``` 137```
172 138
173From time to time, updates may be submitted back to the QMK repository. If you 139From time to time, updates may be submitted back to the QMK repository. If you are reading it there, you can build the firmware like any other firmware included with it (assuming you are in the root directory of the firmware):
174are reading it there, you can build the firmware like any other firmware
175included with it (assuming you are in the root directory of the firmware):
176 140
177``` 141```
178$ make KEYBOARD=ergodox_ez KEYMAP=algernon 142$ make KEYBOARD=ergodox_ez KEYMAP=algernon
@@ -180,43 +144,40 @@ $ make KEYBOARD=ergodox_ez KEYMAP=algernon
180 144
181## Using on Windows 145## Using on Windows
182 146
183The keymap default to forcing NKRO, which seems to upset Windows, and except the 147The keymap default to forcing NKRO, which seems to upset Windows, and except the modifiers, none of them work. If you experience this problem, recompile the firmware with `FORCE_NKRO=no` added to the `make` command line.
184modifiers, none of them work. If you experience this problem, recompile the
185firmware with `FORCE_NKRO=no` added to the `make` command line.
186 148
187# Changelog 149# Changelog
188 150
151## v1.3 - 2016-07-06
152
153* Added support for logging keys, by pressing `LEAD d`. Also included is a tool to generate a [heatmap](#heatmap) out of the logs.
154* The arrow and navigation keys were rearranged again, and now require an additional key being held to activate. See the [base layer](#base-layer) for an image that shows where arrows are.
155* The **experimental** layer has been redone, and is now called [ADORE](#adore-layer), and as such, can be enabled by `LEAD a` now.
156* Switching between Dvorak and ADORE is now persisted into EEPROM, and survives a reboot.
157
189## v1.2 - 2016-06-22 158## v1.2 - 2016-06-22
190 159
191* The forced NKRO mode can be easily toggled off at compile-time, to make the 160* The forced NKRO mode can be easily toggled off at compile-time, to make the firmware compatible with [certain operating systems](#using-on-windows).
192 firmware compatible with [certain operating systems](#using-on-windows). 161* The `:;` key has changed behaviour: to access the `;` symbol, the key needs to be double-tapped, instead of shifted.
193* The `:;` key has changed behaviour: to access the `;` symbol, the key needs to 162* The `=` and `\` keys were swapped, `=` moved to the home row, on both the [base](#base-layer) and the **experimental** layers.
194 be double-tapped, instead of shifted. 163* The arrow and navigation keys were redone, they are now more accessible, but the navigation keys require an extra tap to access.
195* The `=` and `\` keys were swapped, `=` moved to the home row, on both the 164* The **Emacs** layer is gone, replaced by a simplified [navigation and media](#navigation-and-media-layer) layer.
196 [base](#base-layer) and the [experimental](#experimental-layer) layers.
197* The arrow and navigation keys were redone, they are now more accessible, but
198 the navigation keys require an extra tap to access.
199* The **Emacs** layer is gone, replaced by a simplified
200 [navigation and media](#navigation-and-media-layer) layer.
201* `LEAD v` types the firmware version, and the keymap version. 165* `LEAD v` types the firmware version, and the keymap version.
202* On the [experimental](#experimental-layer) layer, the `L` and `Q`, and the `K` 166* On the **experimental** layer, the `L` and `Q`, and the `K` and `G` keys were swapped.
203 and `G` keys were swapped. 167* The [Steno](#steno-layer) layer gained a few more `#` and `*` keys, to make it easier on my fingers.
204* The [Steno](#steno-layer) layer gained a few more `#` and `*` keys, to make it
205 easier on my fingers.
206 168
207## v1.1 - 2016-06-14 169## v1.1 - 2016-06-14
208 170
209* The keyboard starts in NKRO mode, bootmagic and other things are disabled. 171* The keyboard starts in NKRO mode, bootmagic and other things are disabled.
210* A [Steno](#steno-layer) layer was added, to be used with Plover. 172* A [Steno](#steno-layer) layer was added, to be used with Plover.
211* An [experimental](#experimental-layer) layer was added, something halfway 173* An **experimental** layer was added, something halfway between Dvorak and Capewell-Dvorak. A work in progress.
212 between Dvorak and Capewell-Dvorak. A work in progress.
213* `LEAD y` types `\o/`. 174* `LEAD y` types `\o/`.
214* Some keys on the [Base](#base-layer) layer have been moved around: 175* Some keys on the [Base](#base-layer) layer have been moved around:
215 - `?` moved to the left pinky, left of `Q`. 176 - `?` moved to the left pinky, left of `Q`.
216 - `=` shifted one row down, but `F11` stayed where it was. 177 - `=` shifted one row down, but `F11` stayed where it was.
217 - `-` on the left half was replaced by `Tab`. 178 - `-` on the left half was replaced by `Tab`.
218 - `Tab`'s original position is taken by a `Media Next`/`Media Prev` key. 179 - `Tab`'s original position is taken by a `Media Next`/`Media Prev` key.
219 - `:` now inputs `;` when shifted. 180 - `:` now inputs `;` when shifted.
220* `ESC` cancels the [Hungarian](#hungarian-layer) layer too, not just modifiers. 181* `ESC` cancels the [Hungarian](#hungarian-layer) layer too, not just modifiers.
221 182
222## v1.0 - 2016-05-26 183## v1.0 - 2016-05-26
@@ -225,6 +186,4 @@ Initial version.
225 186
226# License 187# License
227 188
228The layout, being a derivative of the original TMK firmware which is under the 189The layout, being a derivative of the original TMK firmware which is under the GPL-2+, this layout is under the GPL as well, but GPL-3+, rather than the older version.
229GPL-2+, this layout is under the GPL as well, but GPL-3+, rather than the older
230version.