blob: b5fde3d4e97046e9ffdf5cf935a2db34a54acf78 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
|
# Keymap Editor
A browser app (plus NodeJS server) to edit QMK and ZMK keymaps. This was hastily
thrown together and then even more hastily converted to a Vue app with support
for ZMK tossed in.
## Setup
You've got a couple of options:
### Local
You can clone this repo and your zmk-config and run the editor locally. Changes
are saved to the keymap files in your local repository and you can commit and
push them to as desired to trigger the GitHub Actions build.
Read more about [local setup](running-locally.md)
### Web
This editor has a (very) rudimentary GitHub integration. You can load the web
app and grant it access to your zmk-config repo. Changes to your keymap are
committed right back to the repository so you only ever need to leave the app to
download your firmware.
Try it now:
1. Fork [zmk-config-corne-demo] on GitHub
2. Go to [keymap-editor] and authorize it to access your forked repo.
Read more about the [GitHub integration](api/services/github/README.md)
## Features
* WYSIWYG keycode and layer editing.
* Keymap (JSON and `.keymap`) generation
* If the (non-standard) `row` and `col` attributes are specified in
`info.json` they will be used to render the generated files in a more human-
readable format that matches the physical layout of the keyboard. Note that
these values are now the rol and column of the wiring matrix which may be
different to use GPIO pins more efficiently.
#### ZMK Behaviours
The app tries to treat both firmware libraries the same way, parsing a key
binding into a `behaviour` and a list of `parameters` -- QMK doesn't share this
concept so a placeholder behaviour of `&kp` is used, and later ignored.
I haven't studied all of ZMK's behaviours closely but this tool supports the
unusual `&bt BT_SEL` behaviour/command which requires one additional parameter
which needs to be added/parsed dynamically.
Side note: I'm Canadian and default to writing behavio*ur*. To match ZMK I will
try to standardize on its spelling but mistakes are likely.
## What's broken/missing
Probably a lot. Like I said, I've mostly built this for myself. I wanted a
graphical way to edit my keymap and I didn't want to have to get yet another
handwired keyboard merged into the QMK repo to rely on their configurator.
I know that QMK moves quickly and now supports a lot of configuration in
`info.json` that I don't provide a way to edit. ZMK has a lot of behaviours that
I haven't defined, and would benefit from a schema definition agreed on by the
dev team.
In a previous version I had started working on supporting combos but gave up
because I couldn't be bothered to experiment with `TAPPING_TERM` settings that
felt comfortable.
More recently I've ripped out QMK-related code. Some interfaces haven't been
updated, so there's still some vestigial support for both. It's less important
to make this a 100% fit for the ZMK codebase and more important to provide a
proof of concept for how apps can be built to support users of the firmware.
### What else?
If you have thoughts on what needs to be fixed to support _your_ keyboard or to
make this a useful tool for users of either firmware, let me know.
I'm not committing to taking this on myself, and I'll probably never do much
testing on any other keyboards, but I'm happy to have discussions on where this
(or another tool) can go.
## License
The code in this repo is available under the MIT license.
The collection of ZMK keycodes is taken from the ZMK documentation under the MIT
license as well.
[keymap-editor]: https://nickcoutsos.github.io/keymap-editor/
[zmk-config-corne-demo]: https://github.com/nickcoutsos/zmk-config-corne-demo
|
