Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Support for non-ZMK devices #262

Open
vsisl opened this issue Oct 3, 2024 · 3 comments
Open

Feature request: Support for non-ZMK devices #262

vsisl opened this issue Oct 3, 2024 · 3 comments

Comments

@vsisl
Copy link

vsisl commented Oct 3, 2024

Hi there!

tldr: Would it be possible to add support for any keaboards (not just ZMK) to keymap-editor by taking advantage of kanata (or another similar tool)?

I'm kind of a newbie in the custom keyboard world. For the last few years, I've been using macOS and ukelele to create a custom keyboard layout. My layout is pretty specific and not possible to replicate with e.g. Microsoft Keyboard Layout Creator (MSKLC)

Now I would like to switch back to Windows and I don't want to learn an new keyboard layout just because switching a platform. Also I work exclusively on laptops and I don't want to use an addtional keyboard. I want to use the keyboard of my laptop.

I came across of kanata which can be used to customize any keyboard. The software looks great but after many hours of unsuccessful attempts, I realized the configuration of kanata is too complex for me.

Now I came across of your keymap editor, which looks super awesome and user friendly! I do realize it works only with devices with ZMK firmware though.

My question is: Would it be possible to add support for any keaboards (not just ZMK) to keymap-editor by taking advantage of kanata (or another similar tool)?

@nickcoutsos
Copy link
Owner

It's an interesting thought but unlikely.

Way back when I started developing this as an editor for my QMK-based keyboard and for a while I could use it to edit either QMK or ZMK keymaps but it was really a worst-of-both-worlds situation. Being able to more generically support ZMK features meant focusing on handling the devicetree model of behaviors and bindings and even with QMK there isn't a translation between the two if you want more than just the trivial features.

With kanata... well this is my first time looking at it. It looks interesting but, again, wildly different

@vsisl
Copy link
Author

vsisl commented Oct 4, 2024

Hi @nickcoutsos

Thanks a lot for sharing your thoughts! I completely understand your conclusion.

By chance do you know about any other key-mapping tool similar to kanata, that would also work with all keyboards but would be easier to configure?

@nickcoutsos
Copy link
Owner

I'm not super familiar with this space, but I've used Karabiner Elements on macos and know if AutoHotKey for Windows.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants