jordan
/
qmk_firmware
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
master
rgb_matrix
planck_rev6
error_log_cleanup
info_json_docs
info_json_updates
keycode_versioning
readme-update
cb2x1800
new_project_fix
moxygen
clueboard_hotswap
handwire
twi2c
arm_audio_fixes
xmega_support
audio_out
gb_port
clueboard_1
info_json_populate
pjrc_hid
subvendor_ids
stm32l476
docs
matrix_update
ps2avrgb
travis_phases
dz_support
make_autocomplete
hid_api
clueboard_arm
sid
keyboards_json
keyboard_identifiers
pp_definitions
teensy_lc_synth
eeprom_update
process_keycode_update
b6_b7_audio
example_keyboards
preonic-1.0
planck-4.0
preonic-2.0
planck-5.0
planck-4.2
planck-4.1
ergodox_ez-161205
0.6.9
0.6.8
0.6.7
0.6.6
0.6.5
0.6.4
0.6.3
0.6.20
0.6.2
0.6.19
0.6.18
0.6.17
0.6.16
0.6.15
0.6.14
0.6.13
0.6.12
0.6.11
0.6.10
0.6.1
0.6.0
0.5.99
0.5.98
0.5.97
0.5.96
0.5.95
0.5.94
0.5.93
0.5.92
0.5.91
0.5.90
0.5.9
0.5.89
0.5.88
0.5.87
0.5.86
0.5.85
0.5.84
0.5.83
0.5.82
0.5.81
0.5.80
0.5.8
0.5.79
0.5.78
0.5.77
0.5.76
0.5.75
0.5.74
0.5.73
0.5.72
0.5.71
0.5.70
0.5.7
0.5.69
0.5.68
0.5.67
0.5.66
0.5.65
0.5.64
0.5.63
0.5.62
0.5.61
0.5.60
0.5.6
0.5.59
0.5.58
0.5.57
0.5.56
0.5.55
0.5.54
0.5.53
0.5.52
0.5.51
0.5.50
0.5.5
0.5.49
0.5.48
0.5.47
0.5.46
0.5.45
0.5.44
0.5.43
0.5.42
0.5.41
0.5.40
0.5.4
0.5.39
0.5.38
0.5.37
0.5.36
0.5.35
0.5.34
0.5.33
0.5.32
0.5.31
0.5.30
0.5.3
0.5.29
0.5.28
0.5.27
0.5.264
0.5.263
0.5.262
0.5.261
0.5.260
0.5.26
0.5.259
0.5.258
0.5.257
0.5.256
0.5.255
0.5.254
0.5.253
0.5.252
0.5.251
0.5.250
0.5.25
0.5.249
0.5.248
0.5.247
0.5.246
0.5.245
0.5.244
0.5.243
0.5.242
0.5.241
0.5.240
0.5.24
0.5.239
0.5.238
0.5.237
0.5.236
0.5.235
0.5.234
0.5.233
0.5.232
0.5.231
0.5.230
0.5.23
0.5.229
0.5.228
0.5.227
0.5.226
0.5.225
0.5.224
0.5.223
0.5.222
0.5.221
0.5.220
0.5.22
0.5.219
0.5.218
0.5.217
0.5.216
0.5.215
0.5.214
0.5.213
0.5.212
0.5.211
0.5.210
0.5.21
0.5.209
0.5.208
0.5.207
0.5.206
0.5.205
0.5.204
0.5.203
0.5.202
0.5.201
0.5.200
0.5.20
0.5.2
0.5.199
0.5.198
0.5.197
0.5.196
0.5.195
0.5.194
0.5.193
0.5.192
0.5.191
0.5.190
0.5.189
0.5.188
0.5.187
0.5.186
0.5.185
0.5.184
0.5.183
0.5.182
0.5.181
0.5.180
0.5.179
0.5.178
0.5.177
0.5.176
0.5.175
0.5.174
0.5.173
0.5.172
0.5.171
0.5.170
0.5.17
0.5.169
0.5.168
0.5.167
0.5.166
0.5.165
0.5.164
0.5.163
0.5.162
0.5.161
0.5.160
0.5.16
0.5.159
0.5.158
0.5.157
0.5.156
0.5.155
0.5.154
0.5.153
0.5.152
0.5.151
0.5.150
0.5.15
0.5.149
0.5.148
0.5.147
0.5.146
0.5.145
0.5.144
0.5.143
0.5.142
0.5.141
0.5.140
0.5.14
0.5.139
0.5.138
0.5.137
0.5.136
0.5.135
0.5.134
0.5.133
0.5.132
0.5.131
0.5.130
0.5.13
0.5.129
0.5.128
0.5.127
0.5.126
0.5.125
0.5.124
0.5.123
0.5.122
0.5.121
0.5.120
0.5.12
0.5.119
0.5.118
0.5.117
0.5.116
0.5.115
0.5.114
0.5.113
0.5.112
0.5.111
0.5.110
0.5.11
0.5.109
0.5.108
0.5.107
0.5.106
0.5.105
0.5.104
0.5.103
0.5.102
0.5.101
0.5.100
0.5.10
0.5.1
0.5.0
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'c20bf83afd'
${ noResults }
qmk_firmware/keyboards/ergodox/keymaps/algernon
History
Gergely Nagy 29f64d7a93 tap-dance: Major rework, to make it more reliable 
This reworks how the tap-dance feature works: instead of one global
state, we have a state for each tap-dance key, so we can cancel them
when another tap-dance key is in flight. This fixes #527.

Since we have a state for each key, we can avoid situation where a keyup
would mess with our global state. This fixes #563.

And while here, we also make sure to fire events only once, and this
fixes #574.

There is one breaking change, though: tap-dance debugging support was
removed, because dumping the whole state would increase the firmware
size too much. Any keymap that made use of this, will have to be
updated (but there's no such keymap in the repo).

Also, there's a nice trick used in this rework: we need to iterate
through tap_dance_actions in a few places, to check for timeouts, and so
on. For this, we'd need to know the size of the array. We can't discover
that at compile-time, because tap-dance gets compiled separately. We'd
like to avoid having to terminate the list with a sentinel value,
because that would require updates to all keymaps that use the feature.
So, we keep track of the highest tap-dance code seen so far, and iterate
until that index.

Signed-off-by: Gergely Nagy <algernon@madhouse-project.org>
 		8 years ago
..
images ergodox: Update my keymap to v1.5 8 years ago
tools Initial structure for Ergodox as subprojects 9 years ago
COPYING Initial structure for Ergodox as subprojects 9 years ago
Makefile ergodox: Update my keymap to v1.5 8 years ago
config.h Initial structure for Ergodox as subprojects 9 years ago
keymap.c tap-dance: Major rework, to make it more reliable 8 years ago
readme.md ergodox: Update my keymap to v1.5 8 years ago

readme.md

algernon's layout

This 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.

Some of the things in the layout only work when one uses Spacemacs and GNOME under Linux. Your mileage may vary.

Table of Contents

Layouts

Base layer

Base layer

At its core, this is a Dvorak layout, with some minor changes. The more interesting parts are how certain keys behave:

  • 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.
  • 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.
  • 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.
  • 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.
  • The Media and Hun layer keys are one-shot, the STENO key is a toggle.
  • 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.
  • Tapping the : key once yields :, tapping it twice yields ;.
  • The Lead key allows me to type in a sequence of keys, and trigger some actions:
    • LEAD u enters unicode input mode, by sending the GTK+ key sequence that does this.
    • LEAD l uses the unicode input method to enter a λ.
    • LEAD s does a lot of magic to type in a shruggie: ¯\_(ツ)_/¯
    • LEAD y types \o/.
    • LEAD w m maximises the currently focused window.
    • LEAD a makes the ADORE layer the default.
    • LEAD v prints the firmware version, the keyboard and the keymap.
    • LEAD d toggles logging keypress positions to the HID console.
    • LEAD t toggles time travel. Figuring out the current date is left as an exercise to the reader.
    • LEAD LEAD u enters the [Unicode symbol input][#unicode-symbol-input] mode.

ADORE layer

ADORE layer

While 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, 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.

Based 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.

Hungarian layer

Hungarian layer

On 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.

Navigation and media layer

Navigation and media layer

This layer is primarily for navigating with the cursor or the mouse, and some media things.

Steno layer

Steno layer for Plover

This is to be used with Plover, nothing really fancy here. The STENO key toggles the layer on and off, and sends the toggle command to Plover too.

LED states

The 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.

For the layers, the following rules apply:

  • When the 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.
  • When the Hungarian layer is active, the green and blue LEDs are on.
  • When the Navigation and media layer is active, the red and green ones are on.
  • For the Steno layer, all LEDs will be turned on.

Unless 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.

Special features

Unicode Symbol Input

Once in the Unicode Symbol Input mode, one is able to type in symbol names, press Enter or Space, and get the Unicode symbol itself back. When in the mode, a capital U is printed first. Once the sequence is finished, all of it is erased by sending enough Backspace taps, and the firmware starts the OS-specific unicode input sequence. Then, it looks up the symbol name, and enters the associated code. If it is not found, it will just replay the pressed keycodes.

The currently supported symbols are:

  • snowman: ☃
  • kiss: 😙
  • rofl: 🤣
  • poop: 💩

This is an experimental feature, and may or may not work reliably.

Tools

Heatmap

When 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.

Included with the firmware is a small tool that can parse these logs, and create a heatmap that one can import into 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.

The generated heatmap looks somewhat like this:

Heatmap

Building

To make my workflow easier, this layout is maintained in its own repository. To build it, you will need the 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:

$ git clone https://github.com/jackhumbert/qmk_firmware.git
$ cd qmk_firmware
$ git clone https://github.com/algernon/ergodox-layout.git \
            keyboards/ergodox/keymaps/algernon-master
$ make keyboard=ergodox keymap=algernon-master

From 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):

$ make keyboard=ergodox keymap=algernon

Using on Windows

The 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.

Changelog

v1.5 - 2016-08-12

  • The 1HAND layer has been removed.
  • A Delete key is now available on the right thumb cluster.
  • The ADORE layer received a major update, see the layout image above.
  • It is now possible to enable automatic logging for the ADORE layer, by setting the ADORE_AUTOLOG makefile variable to yes when compiling the keymap. It is off by default.
  • The ~ key and the Media Next/Prev key have been swapped on the base layer.
  • On the ARROW layer, Backspace has been replaced by Enter.
  • There is some experimental support for entering Unicode symbols.

v1.4 - 2016-07-29

  • When toggling the key logging on or off, the LEDs will do a little dance.
  • The keylogger is now optional, but enabled by default. Use KEYLOGGER_ENABLE=no on the make command line to disable it.
  • The TAB/ARRW key was turned into a tap-dance key, allowing one to toggle the ARROW layer on by double-tapping, and as such, avoid the need to hold the key.
  • The -/_ key was turned into a tap-dance key too.
  • There is now a way to travel time with the keyboard, toggle the feature on by hitting LEAD t.

v1.3 - 2016-07-06

  • Added support for logging keys, by pressing LEAD d. Also included is a tool to generate a heatmap out of the logs.
  • The arrow and navigation keys were rearranged again, and now require an additional key being held to activate. See the base layer for an image that shows where arrows are.
  • The experimental layer has been redone, and is now called ADORE, and as such, can be enabled by LEAD a now.
  • Switching between Dvorak and ADORE is now persisted into EEPROM, and survives a reboot.

v1.2 - 2016-06-22

  • The forced NKRO mode can be easily toggled off at compile-time, to make the firmware compatible with certain operating systems.
  • The :; key has changed behaviour: to access the ; symbol, the key needs to be double-tapped, instead of shifted.
  • The = and \ keys were swapped, = moved to the home row, on both the base and the experimental layers.
  • The arrow and navigation keys were redone, they are now more accessible, but the navigation keys require an extra tap to access.
  • The Emacs layer is gone, replaced by a simplified navigation and media layer.
  • LEAD v types the firmware version, and the keymap version.
  • On the experimental layer, the L and Q, and the K and G keys were swapped.
  • The Steno layer gained a few more # and * keys, to make it easier on my fingers.

v1.1 - 2016-06-14

  • The keyboard starts in NKRO mode, bootmagic and other things are disabled.
  • A Steno layer was added, to be used with Plover.
  • An experimental layer was added, something halfway between Dvorak and Capewell-Dvorak. A work in progress.
  • LEAD y types \o/.
  • Some keys on the Base layer have been moved around:
    • ? moved to the left pinky, left of Q.
    • = shifted one row down, but F11 stayed where it was.
    • - on the left half was replaced by Tab.
    • Tab's original position is taken by a Media Next/Media Prev key.
    • : now inputs ; when shifted.
  • ESC cancels the Hungarian layer too, not just modifiers.

v1.0 - 2016-05-26

Initial version.

License

The 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.