Going modular #73
urob
announced in
Announcements
Replies: 3 comments 3 replies
-
Glad to see that Awesome work. 👍🏼 |
Beta Was this translation helpful? Give feedback.
3 replies
-
Amazing work. Thank you for sharing it all! |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thanks @urob! Updated my config, no issues, working flawlessly. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Currently, this config relies on a custom ZMK fork for the building. Historically, that fork included many experimental features, many of which are now part of upstream ZMK or are available as ZMK modules.
My hope is that with the module ecosystem growing, I'll be eventually able to build against upstream ZMK and a few modules. In c8b4369, I started making this transition. Instead of using my
main
ZMK branch to build my firmware, I'm now usinggoing-modular
.Switching to the
going-modular
branch, the reliance on experimental features is now down to two features:require-prior-idle
(merged upstream)masked-mods
fix (merged upstream)hold-on-release
forbalanced
(merged upstream)repeat
fix (merged upstream)tri-state
behavior PR (replaced bytri-state
module)smart-word
behavior PR (replaced byauto-layer
module)hold-on-release
fortap-preferred
(no replacement needed 1)There are two new patches added to make testing with
west test
work when ZMK is loaded as a module:test.py
west
issue (#725)One of the remaining features (mouse movements) is huge and it finally being merged upstream is widely anticipated.
Once it is, the only reason for me to keep using a custom ZMK fork for non-testing purposes will be @caksoylar's tweaks for my Corneish Zen.2 Any other board will be able to build against upstream ZMK and a few models. Not sure why, but I find that really exciting! 🎉🎉
I'll be using this issue to track the progress to going fully modular. For now, I'm still maintaining both of my ZMK "production" branches (
main
andgoing-modular
). But I'll be lowering the upgrade frequency ofmain
and may at some point makegoing-modular
the newmain
. I recommend anyone using my branches in their build routine to consider making a similar switch to a modular ZMK system.Footnotes
I kept this commit around as a courtesy for people who wanted to play around with hold-tap flavors and still use positional hold-taps. But since I am only using the balanced flavor myself, there's no need to keep it in my ZMK branch. ↩
Those tweaks rely on some core changes that can't be easily moved to a module. ↩
Beta Was this translation helpful? Give feedback.
All reactions