Chrysalis is a graphical configurator for
Kaleidoscope-powered keyboards. While still under
development, it is already usable for a number of tasks. To try it,
you don't even need to flash
Kaleidoscope beforehand, Chrysalis
can do that for you, as it ships with reasonable default firmware
for each supported board.
The primary purpose of the application is to allow one to configure their keyboard without having to compile or flash firmware, by storing the configuration on the keyboard itself, in EEPROM. There are no external tools required, just Chrysalis itself.
- Layout editor to edit the keymap on-the-fly, with the ability to copy one layer to another, and to set a default one.
- Colormap editor to edit the per-key LED colormap on boards that support it.
- Firmware upgrade to upload either the default, Chrysalis-enabled firmware that ships with the application, or a custom one.
The ErgoDox EZ (and any other keyboard wired like it), the SOFT/HRUF Splitography, KBDFans KBD4x, and older, Teensy-based OLKB Planck keyboards are also supported, as long as they run suitable firmware.
Supported operating systems
Chrysalis is primarily developed under Linux, but we target all three major operating systems, and test our releases on Windows and macOS too. That said, our testing is done on Ubuntu 18.04 LTS, Windows 10, and macOS Mojave.
The protocol Chrysalis uses to communicate with the keyboard requires USB serial support, which is known to be problematic on Windows prior to Windows 10.
From installer packages
Choose whether to install the production release, or a development snapshot from the links above, and from the release page, select the installer appropriate for your operating system.
brew update && brew upgrade brew install --cask chrysalis
Chrysalis is alpha quality software. There will be bugs, missing features and non-obvious things. Reporting any and all of these help us make the software better, please feel free to open issues liberally!
To launch the development environment, simply type
yarn && yarn start. To do a
production build, use
yarn run build:all, or limit it to a particular OS:
yarn run build:linux,
yarn run build:mac or
yarn run build:win. See the
scripts section of
package.json for more scripts.
There are sample ENV file & debugging configurations provided in the
dev/sample directory. There is also an example launch.json for VSCode under the
.vscode directory under
dev/sample/.vscode/launch.json. To debug the main process, you may wish to launch from an IDE (without using the above in a terminal), configurations for VSCode are provided. If using the launch or compound configurations, the
timeout properties must allow enough time for the app to fully launch before the debugger(s) stop trying. In the case of compound, this applies to the renderer and main process debugger.
Note: The ports defined in your .env.development & your debugging configuration must match.