Closed JamesMowery closed 8 months ago
nickcoutsos
commented
9 months ago The demo is a fake keyboard, corne doesn't actually have encoders.
Edit: is there a particular keyboard you want to build keymaps for? You can use ZMK's setup script to create a repo for a corne or several other keyboards and for the most part the layout metadata is built into the app already.
JamesMowery
commented
9 months ago Thanks! That fixed it. I feel like this web editor is going to be a big attraction to completely new users (like me). However, this wasn't a good experience or outcome from a user perspective.
Always assume that the user doesn't know what's going on (like this sensor thing you mentioned above, which I still don't understand). I did see a sensor section on the first page and clicked delete just now, and it appears to be working now, though I still don't know what or why this does it. It's not explained.
If I was a developer and wanted to gain adoption from people (if that is a desire of this project), please make the brand new user experience a good one.
This might also be a make or break on determining if someone might get into the split/ergo keyboard world. So this is a lot of responsibility to undertake. I wouldn't have purchased my Corne keyboard kit if this web editor didn't exist. This software could actually hurt this entire community if done wrong. Please make the onboarding experience good, or at least ensure it can't be broken out of the box.
JamesMowery
commented
9 months ago Edit: is there a particular keyboard you want to build keymaps for? You can use ZMK's setup script to create a repo for a corne or several other keyboards and for the most part the layout metadata is built into the app already.
Just seen this. I actually don't yet have the Corne here yet, should be arriving in a week. I haven't really gotten deep into that part (I think a lot of people who are just getting into this will probably do that after they build/receive their keyboard). I was just using the web editor to simulate what I think I want a layout to look like. Thus the note about this perhaps being an entryway for people who are completely new to this. Seeing build failures doesn't inspire confidence, as you could imagine.
But good to know that the official ZMK stuff creates a repo for you. I didn't know!
I guess a good follow question is... should I NOT create a repo from the web editor at all and will all my work being done now be worthless (I've setup like 7 layers so far, haha)? Or can I just still use the repo created via the demo project (which is now fixed) for my Corne when it arrives and is built? If true, I think it's simply a documentation issue/fix then. Just put a big red disclaimer on the docs and/or the web editor itself (when on the demo) suggesting you create a repo via the ZMK software, and that should do it!
P.S. I really do appreciate this web editor! Just want it to not dissuade anyone from getting into this! This project is amazing.
nickcoutsos
commented
9 months ago You'll be able to migrate pretty easily without losing any of your work so far. What I'd recommend is following ZMK's steps to create a zmk-config repo set up for corne (or fork from your keyboard's vendor if they provide a more specific setup), and then copy your current corne.keymap into that repo's config/ directory, leaving out the sensor-bindings properties.
Attempted to create my own Github repo for a Corne wireless keyboard with nice!nano v2. Even from the very first build this was failing. Still continues to fail after a few hours of playing around with my own keymap generated from the demo keymap provided.
This is the error I'm seeing:
Here's a more recent attempt with debug mode enabled on the actions/builder if helpful: