vial-qmk VS lagrange-keyboard

i wish to enable several features on my corne thru vial but could not seem to make those from this link to compile - first error was about keycode then something about dynamic keymap when i had the first fixed/simplified. i'd appreciate if anyone could share their tested vial configuration files that i can use as guide.

This applies to OP as well, if you have any Keyboard @ https://github.com/vial-kb/vial-qmk/tree/vial/keyboards/keychron

You'll probably need to download the files from the GitHub repository for Vial or QMK. Depending on what you prefer and what you need. Then you'll have to learn what you need to change to set up the screens and then to edit the files. Your keyboard maker probably can provide you some files you can use. Then you'll have to compile your own HEX file. And only after that you can re-flash your keyboard and use all those amazing things you integrated into the firmware.

It looks like that's a vial keymap specifically for the rev2? I don't know whether it would make a difference, but you could try to compile from this keymap instead and see if it works?

According to this (https://github.com/vial-kb/vial-qmk/blob/vial/keyboards/bastardkb/charybdis/4x6/v2/splinky/config.h) the Vial firmware for Splinky based Charybdis is written natively using RP2040 pin names.

Think you can also port to VIAL? I am currently using the doio firmware without problems, but guessing your updates will be useful: https://github.com/vial-kb/vial-qmk/tree/vial/keyboards/doio/kb16

I've been using VIA to edit my keyboard layout, but unfortunately the software can't find my keyboard anymore (it just gets stuck on 'Searching for devices'). I think I need to reflash my keyboard. I don't have any .hex files for it with QMK toolbox, and the libra mini doesn't show up in the list of keyboards on the online QMK configurator. I do, however, have access to the files found in vial-qmk/keyboards/libra_mini/keymaps/vial (found here https://github.com/vial-kb/vial-qmk/tree/vial/keyboards/libra_mini). I've been using the vial.json file from there to change the layout up until now. How would I go about getting a .hex file, or better yet, a keymap.JSON file compatible with the online QMK configurator?

You can see an example in the photos of my Lagrange keyboard.

I was looking for a suitable example for a tutorial for my programmatic solid modeling CAD Gamma and a clamp seemed suitable. Well, I haven't started work on the tutorial yet, but here's a clamp-mount assembly for my Lagrange keyboard.

I had both my Expert Mouse and the Orb I'm now using, between the two halves of my Ergodox and now my Lagrange. Ergonomically, it is, I think, the natural choice, but perhaps the separation between the halves is larger than average in my setup.

As for Gamma: I wasn't really aware of CadQuery, but I did use OpenSCAD extensively, when designing my Lagrange keyboard. Gamma started as a way to address some aspects I didn't find quite satisfactory (as, to be fair, I can't say I had any real problems). Also to be fair, I used OpenSCAD through a frontend(scad-clj) translating Clojure code to its native language and some of the problems may have been due to that, but that is also one of the issues I had with OpenSCAD: why have to learn a new language when there are existing embedabble scripting languages, you might now already, of if not, which you might use elsewhere and which, having years of development, will likely be better?

This is not about the Dactyl per se, but my Lagrange keyboard supports this (or at least attempts to; it's hard to guarantee that the resulting geometry will be problem-free for a given set of parameters). The build guide goes into some detail on what you're trying to do.

I've tried it. In fact, I've designed it, I designed it as a key meant to be operated with the edge of the palm with my Lagrange keyboard. This doesn't mean it couldn't be used as a thumb key of course, but note that you could also create your own custom version of this (or other keys).

I started with an ErgoDash [1], purchased because my Microsoft/Logitech split keyboards had worn out, and at the time I couldn't find a replacement with normal (not low profile) keys. It has a few additional keys compared to the Iris. I have one at work and another at home, and to make them more similar to the broken keyboards I 3D printed angled bases. I use it for 99% of my typing.

I should probably have tried a Kinesis Advantage 2 first.

I'm partway through printing/assembling a Lagrange keyboard [2] (I'm currently stuck working out how to order the circuit boards), which is similar to the Dactyl. I will add the F1-F12 keys to my print, as they're the only thing I miss -- if a shortcut in my IDE is Ctrl+Shift+F10, it's nice for it to be that, not Ctrl+Shift+Fn+0.

I made [3] to help others see what's available.

[1] https://github.com/omkbd/ErgoDash/

[2] https://github.com/dpapavas/lagrange-keyboard

[3] https://aposymbiont.github.io/split-keyboards/

I don't use a DM, but if the question is whether something like the DM could be used as a daily driver, or whether something "less radical" would be preferable, I can say that I've been using my Lagrange as a daily driver for more than a year now. Its geometry is comparable to that of the DM and, from what I can tell, it's more aggressively curved.

I was warned by a colleague that this was a rabbit hole, then warned by people online, and I'll pass on that warning now.

I tried to help by updating and better-presenting an existing list of ergonomic mechanical keyboards: https://aposymbiont.github.io/split-keyboards/

I'm using an ErgoDash¹ with a 3D-printed tilted stand, but I intend to assemble a Lagrange² "soon".

¹ https://github.com/omkbd/ErgoDash

² https://github.com/dpapavas/lagrange-keyboard

Having spent quite a bit of time over the past couple of years designing a concave keyboard (the Lagrange) and therefore having a sort of vested interest, psychologically speaking, to say "yes, definitely!", I would say: depends what you mean by "worth it".