Making a change, compiling and updating the keyboard is a process of seconds, which makes trial and error highly enjoyable. Perhaps most important of all: once you have the initial setup done, the iteration cycle is really quick. Programming your own firmware - in C, no less - sounds like a daunting and dangerous undertaking, but thanks to good guides and tools it is actually pretty easy. QMK is the open source firmware supported by this and many other keyboards. ![]() I did not, however, expect to make progress this fast, or to have anywhere near this much fun figuring out and programming my layout. I was expecting all this to be a challenge, especially since I never managed to get comfortable enough with my Pok3r to use it regularly. And it has the keys in straight lines - ortholinearity, as the hipsters call it - just to make getting used to it a little bit more challenging. Oh yeah, it is also pretty small compared to most other keyboards. That means figuring out where you want each function of a keyboard to be, deciding how exactly to invoke it, then editing a C file, compiling a new firmware, uploading it to the keyboard itself, and trying it out. To get the most - or anything, really - out of a keyboard like this, you need to program it yourself. ![]() It is a 40% keyboard, meaning it lacks a lot of keys you expect to find hanging around the outskirts of comfortable hand positioning. This is a KBD4X, made by a company called Kbdfans.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |