Drashna Jaelre
b05c0e46c6
* Add default value for IS_COMMAND for COMMAND feature * Cleanup and consistency * Update Templates to reflect change * Fix IS_COMMAND in template * Fix IS_COMMAND define * Use consistent IS_COMMAND block in templates * Remove unnecessary `#undef IS_COMMAND` directives * Fix compile issue on orthodox * Reomve IS_COMMAND option for newer boards * Remove all existing definitions of IS_COMMAND if they use default LSHIFT and RSHIFT setting * Remove a couple of additional IS_COMMAND defines * Remove remaining redundant IS_COMMAND definitions * Remove #undef IS_COMMAND from orthodox:drashna and whitefox:konstantin * Remove multiple empty lines in modified config.h files * Update additional boards * Reomve IS_COMMAND from newer boards * Update Alice keyboard * Remove IS_COMMAND from additional boards Jan 24th edition |
6 years ago | |
---|---|---|
.. | ||
keymaps/default | Remove unused fn_actions[] and action_function() in default keymaps (#4829) | 6 years ago |
config.h | Adds a default value for IS_COMMAND for COMMAND feature (#4301) | 6 years ago |
readme.md | Fixed dead links (#2451) | 7 years ago |
rules.mk | Updates bootloader settings, adds file size check (#2029) | 7 years ago |
traveller.c | adding traveller keyboard | 9 years ago |
traveller.h | adding traveller keyboard | 9 years ago |
readme.md
traveler keyboard firmware
Traveller Specific Info
The traveller is a varient on the atreus keyboard. Like the Atreus, it is designed to be a good compromise between size and ergonomics.
key differences are
- an additional column for each pinky
- an RGB LED in the center to show the current layer
- more finger stagger, splay angle and contoured keycaps (F2 profile for space key).
You can make your own traveller keyboard by using the openscad tools from the atreus repository, and adding a hole for the LED to shine through.
Quantum MK Firmware
For the full Quantum feature list, see the parent README.md.
Building
Download or clone the whole firmware and navigate to the keyboard/traveler folder. Once your dev env is setup, you'll be able to type make
to generate your .hex - you can then use the Teensy Loader to program your .hex file.
Depending on which keymap you would like to use, you will have to compile slightly differently.
Default
To build with the default keymap, simply run make
.
Other Keymaps
Several version of keymap are available in advance but you are recommended to define your favorite layout yourself. To define your own keymap create file named <name>.c
and see keymap document (you can find in top README.md) and existent keymap files.
To build the firmware binary hex file with a keymap just do make
with KEYMAP
option like:
$ make KEYMAP=[default|jack|<name>]
Keymaps follow the format <name>.c and are stored in the keymaps
folder.