aboutsummaryrefslogtreecommitdiff
path: root/layouts/community/ergodox/algernon/readme.md
diff options
context:
space:
mode:
Diffstat (limited to 'layouts/community/ergodox/algernon/readme.md')
-rw-r--r--layouts/community/ergodox/algernon/readme.md23
1 files changed, 10 insertions, 13 deletions
diff --git a/layouts/community/ergodox/algernon/readme.md b/layouts/community/ergodox/algernon/readme.md
index 4c1fb15ff..03b094edb 100644
--- a/layouts/community/ergodox/algernon/readme.md
+++ b/layouts/community/ergodox/algernon/readme.md
@@ -34,13 +34,13 @@ Some of the things in the layout only work when one uses [Spacemacs][spacemacs]
34 34
35## Base layer 35## Base layer
36 36
37[![Base layer](https://i.imgur.com/q1MDvq4.png)](http://www.keyboard-layout-editor.com/#/gists/28f7eb305fdbff943613e1dc7aa9e82b) 37[![Base layer](https://github.com/algernon/ergodox-layout/raw/master/images/base-layer.png)](http://www.keyboard-layout-editor.com/#/gists/28f7eb305fdbff943613e1dc7aa9e82b)
38 38
39At its core, this is a Dvorak layout, with some minor changes. The more interesting parts are how certain keys behave: 39At its core, this is a Dvorak layout, with some minor changes. The more interesting parts are how certain keys behave:
40 40
41* The number row is the same as in the [ADORE](#adore-layer) layer. The function keys are on the **Media** layer. 41* The number row is the same as in the [ADORE](#adore-layer) layer. The function keys are on the **Media** layer.
42* 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. 42* 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.
43* 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. 43* The `GUI` key is special, because while a single tap works as usual, when double-tapped, it turns the number row into an application selector, and when triple tapped, it runs an application selector program on the host.
44* 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. 44* 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.
45* The **Media** and **Hun** layer keys are one-shot, the **STENO** key is a toggle. 45* The **Media** and **Hun** layer keys are one-shot, the **STENO** key is a toggle.
46* The **Fx** key is one-shot, and activates the **Media** layer, along with a one-shot `Alt`. 46* The **Fx** key is one-shot, and activates the **Media** layer, along with a one-shot `Alt`.
@@ -57,12 +57,12 @@ At its core, this is a Dvorak layout, with some minor changes. The more interest
57 - `LEAD d` toggles logging keypress positions to the HID console. 57 - `LEAD d` toggles logging keypress positions to the HID console.
58 - `LEAD t` toggles time travel. Figuring out the current `date` is left as an exercise to the reader. 58 - `LEAD t` toggles time travel. Figuring out the current `date` is left as an exercise to the reader.
59 - `LEAD u` enters the [Unicode symbol input](#unicode-symbol-input) mode. 59 - `LEAD u` enters the [Unicode symbol input](#unicode-symbol-input) mode.
60 60
61The symbols on the front in the image above have the same color as the key that activates them, with the exception of the **Arrow** layer, which is just black on the front. 61The symbols on the front in the image above have the same color as the key that activates them, with the exception of the **Arrow** layer, which is just black on the front.
62 62
63## ADORE layer 63## ADORE layer
64 64
65[![ADORE layer](https://i.imgur.com/r3LnQAA.png)](http://www.keyboard-layout-editor.com/#/gists/45681a17453d235925b6028dd83bf12a) 65[![ADORE layer](https://github.com/algernon/ergodox-layout/raw/master/images/adore-layer.png)](http://www.keyboard-layout-editor.com/#/gists/45681a17453d235925b6028dd83bf12a)
66 66
67My experimental layout, that I keep tweaking. No full description here, because things are very much in flux. 67My experimental layout, that I keep tweaking. No full description here, because things are very much in flux.
68 68
@@ -70,7 +70,7 @@ Note that the **HUN** layer does not work well with ADORE: it still has the same
70 70
71## Steno layer 71## Steno layer
72 72
73[![Steno layer for Plover](https://i.imgur.com/PgifhBF.png)](http://www.keyboard-layout-editor.com/#/gists/401ef9a84369e47c57f9aedcf0a0d667) 73[![Steno layer for Plover](https://github.com/algernon/ergodox-layout/raw/master/images/steno-layer.png)](http://www.keyboard-layout-editor.com/#/gists/401ef9a84369e47c57f9aedcf0a0d667)
74 74
75This 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. 75This 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.
76 76
@@ -110,7 +110,7 @@ Included with the firmware is a small tool that can parse these logs, and create
110 110
111The generated heatmap looks somewhat like this: 111The generated heatmap looks somewhat like this:
112 112
113 ![Heatmap](https://i.imgur.com/tly9XSy.png) 113 ![Heatmap](https://github.com/algernon/ergodox-layout/raw/master/images/heatmap.png)
114 114
115## Layer notification 115## Layer notification
116 116
@@ -118,7 +118,7 @@ There is a very small tool in `tools/layer-notify`, that listens to the HID cons
118 118
119# Building 119# Building
120 120
121To 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: 121To 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 `layouts/community/algernon_master`, or symlinked there. One way to achieve that is this:
122 122
123 [algernon:ez-layout]: https://github.com/algernon/ergodox-layout 123 [algernon:ez-layout]: https://github.com/algernon/ergodox-layout
124 [qmk]: https://github.com/qmk/qmk_firmware 124 [qmk]: https://github.com/qmk/qmk_firmware
@@ -127,14 +127,14 @@ To make my workflow easier, this layout is maintained in [its own repository][al
127$ git clone https://github.com/qmk/qmk_firmware.git 127$ git clone https://github.com/qmk/qmk_firmware.git
128$ cd qmk_firmware 128$ cd qmk_firmware
129$ git clone https://github.com/algernon/ergodox-layout.git \ 129$ git clone https://github.com/algernon/ergodox-layout.git \
130 keyboards/ergodox/keymaps/algernon-master 130 layouts/community/ergodox/algernon_master
131$ make keyboard=ergodox keymap=algernon-master 131$ make ergodox_ez-algernon_master
132``` 132```
133 133
134From 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): 134From 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):
135 135
136``` 136```
137$ make keyboard=ergodox keymap=algernon 137$ make ergodox_ez-algernon
138``` 138```
139 139
140## Using on Windows 140## Using on Windows
@@ -144,6 +144,3 @@ The keymap default to forcing NKRO, which seems to upset Windows, and except the
144# License 144# License
145 145
146The 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. 146The 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.
147
148![nav-n-media-layer.png](https://i.imgur.com/AReX8C9.png)
149![hun-layer.png](https://i.imgur.com/uPGBl9J.png) \ No newline at end of file