An awesome tester of ours just happens to be a VIM user. Apparently, he customized his prototype by putting a VIM key in place of Esc.
He also modified the keymap by binding Esc to the base layer and backtick to the Mod layer.
Thanks and well done, Gyuri!
The keyboard. For professionals.
A fully programmable, impeccably built, open source, split mechanical keyboard designed for extreme productivity and ergonomics.
The keyboard. For professionals.
A fully programmable, impeccably built, open source, split mechanical keyboard designed for extreme productivity and ergonomics.
Comments are closed.
The keyboard looks really great and I would buy it in a heartbeat except for one major problem - the F keys require a meta-character. I've been a developer for 30 years, and currently work in AndroidStudio where I only use my keyboard (currently I use a dasKeyboard with blank keys). Coders like myself, require using the F keys continuously and many crucial commands require Ctrl-Alt-F, Alt-Shift-F, or Ctrl-Shift F, etc. Mapping these 3 meta-pairs is not really an option on your keyboard without loss of other key functions. My point being that most coders I know will not use a keyboard that requires an additional key to active the F keys. I'm sure you have considered this, but it's worth mentioning anyway. If you ever do decide to release a model with an additional F key row, I and many of my peers will be the first in line to buy one. One last thing... please make the split keyboard bases heavy enough so that the remain stationary; sticky feet pads are not enough because they loose adhesion in a short time.
Regards, and good luck with you very good idea.
You've raised some great points Monte, thank you for that.
We plan to release larger sized keyboards in the future. In the meantime, I believe a good solution that you haven't considered is mapping these shortcuts to the keys of various layers. For example, you can map Fn+Q to Ctrl+Alt+F1, Fn+W to Ctrl+Alt+F2 and so on. You could make this an application-specific keymap and so you could reuse Fn+Q and Fn+W in another application. How about that?
Again, thanks a lot! Feedbacks like yours are very valuable to us.
Thanks for your response László.
I had considered the the option you suggest which will be useful for many coders. On the other hand, there are a great many hard core developers that shy away from defining new key mappings in their IDE and much prefer to use the default ones provided (Android Studio, Visual Studio, Eclipse, etc.). The reason they like to use the default key mappings is so that than can easily work in peer installations (as well as at client sites) using the same key combinations that they are accustomed to and are always available in any IDE. Coding speed and efficiency can be markedly reduced when you have to switch between custom key mappings in your home environment and default key mappings in other environments for the same tools. That is why the F keys would be so useful. I will probably buy your smaller model when it is first released, just because it is so cool, and I can use it for non-development tasks. But I will look forward to an F key release so that I can use your produce where it really matters, in my IDE. Best wishes for your success with this great product!