I’ve been really enjoying customizing my Atreus with Chrysalis. However, I’d like to explore some of the more advanced features that, at least for now, require using Kaleidoscope. I have a few basic questions about how to make that transition, though. (Some of these are so basic that I worry I’ve missed something obvious in the docs. If so, I’d appreciate pointers to the right docs, since I must have been looking in the wrong place!.)
- Do I need to start my configuration from scratch, or can I import my existing keymaps? I know I can export configuration from Chrysalis to JSON, but it’s my understanding that there’s currently no way to go from that to the C code Kaleidoscope needs. Is that correct?
- If I do need to start from scratch, how do I do so? I understand that Chrysalis uses EEPROM for its configuration. Does that mean that I should disable the EEPROM plugins when I start using Kaleidoscope? With them enabled, the Kateidoscope keymaps show up in Chrysalis as layers -1, -2, and -3 but I don’t see a way to switch to those layers. Does EEPROM provide functionality (other than supporting Chrysalis) that I’d be missing out on by disabling it?
- (very basic question) Where are the files that I’m importing when flashing my firmware? Following the docs, I started from the Keybordio Atreus example firmware. I expected that this would load an example project, but it seems to only open one file, which is read-only. I can save the file to a new location, but it’s not clear where it gets its imports from. Should I save a copy of all the examples to a new location? If not, what’s the best way to get set up for my own customization? (Maybe this would be more clear to me if I’d written more C code – I was expecting a directory of configuration files governed by something akin to a
Cargo.toml, but maybe that’s the wrong reference point.)
More generally, I’m sure this would all be more clear if I’d programmed an Arduino before but this is my first experience on the platform. Thanks very much for any help you can provide!