keyboards
qmk_firmware
keyboards | qmk_firmware | |
---|---|---|
77 | 10 | |
227 | 0 | |
- | - | |
9.6 | 0.0 | |
9 days ago | over 1 year ago | |
C | C | |
MIT License | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
keyboards
-
Split kb symbol layer for dev/vim user
I have custom alpha layers and extremely optimized symbol layers, combos and other features in my keymap. It is not designed for web development, but it is good for VIM and Java.
-
Hands Down variation with only 20 keys
That made me think. If I would adapt Romak for 20 keys, it would be something like this:
-
Suggest a layout for 5 column and 3 row split keyboard
But since you are a programmer, I invite you to check the fancy programmer features that I have implemented in my keymap. I still need to rework on the documentation, but you can take some inspiration from there if you decide to design your own.
-
Well-known optimized layouts
Romak also has some very nice attributes, as do poqtea and uciea. I also find Canary to have a lot of merit.
-
Cheapest way to try Miryoku style layout
There is also the unusual option to handwire a keyboard without soldering, as I did here, but the result might not be so reliable.
-
APT (V1?) vs Engram
You can see my layout here.
-
Beakl-HC - No more pinky and ring finger pain!
I started my own layout, Romak, using BEAKL as inspiration, with similar objectives, mostly making it more suitable for my home language and reducing the load on pinkies and indexes, concentrating in the middle and ring fingers instead. Another thing I did was to remove the top row key from both the central and pinkie columns. Later I also removed the bottom row key from the pinkies.
-
In need for a beginner guide
My first handwired board checks all your requirements, and I have some pictures of the process, but it is not a complete guide. It might help though. And I think the FFKB case can be great for a first handwired project.
-
Custom 60% layout I've been using, designed for Canadian programmers. Critiques please!
Really nice work, congrats. My custom layout is designed for both Portuguese and English, and I have some of the same ideas implemented, with similar reasoning. I also have some programming features that remind yours, but I preferred to remap hjkl instead.
-
Best way to build hot swap into a handwire?
I've used two different options in my builds. You can see them in the build logs: FFKB and Rommana.
qmk_firmware
-
Help me finish my Colemak layout
Here's my keymap, for use with US Qwerty Intl. English virtual layout yet defaulting to a Colemak-DH physical layout. I basically don't use the numrow. I favour layer access via chording a single key, and biased several things to just use the left hand so I can mouse freely with my right (which has programmable buttons duplicating Ctrl & Shift). The left hand alone can chord the nav layer while also comfortably highlight whole words at a time (Ctrl+Shift+left or right arrows). The symbols are mostly paired for inwards rolls, as Colemak emphasises.
-
Looking for a good Keymap for coding
It'll somewhat depend what virtual layout you're used to the behaviour of, such as any deadkey/compose behaviour for diacritics. I use this on mine (defaulting to the Colemak-DH based alphas layer) in combination with Qwerty US International English virtual layout.
-
First Ergo Home Build: lily58
If you want to have the Lily logo orientated the 'right' way as per the original source artwork before anyone monochromed it, I put the bitmap in my repo.
-
How are ergo keyboards like Lily58 for gamers? (WASD hand position seems awful)
Try another one for Colemak-DH while you're at it, or use mine. You can also have the Lily logo orientated the correct way too...
-
is split usable programming?
Sure, just expect you will iterate on your layers as you find what's most useful and comfortable for you. Here's where I'm at for coding on a split kb while also often using a right hand mouse with a few programmable thumb buttons set to be Ctrl and Shift as per the kb half.
-
Are rotary encoders really that useful? Especially for programming?
My Lily fork is here, specifically my fontless branch where I slimmed the firmware by trying out directly encoding bitmap fragments rather than using the font glyph table system. Basically this lets me have doublesized, black on white characters to show Shift Ctrl Alt AltGr, as well as which side, and have custom Num/Caps/Scroll lock icons. For layer labels I have a mix of smaller-than-standard fonts and icons. You can just draw which pixels you want on/off in the code, each row being a vertical 8pixel column.
-
Change layer names and OLED Display on HotDox V2 ?
If it's QMK and you set up a local build environment, there should be a ´bool oled_task_user(void) {}´ in your keymap.c where you can then change the strings used, or replace the font c file to change the logo art, or even slim the firmware by skipping using the standard font system.
-
List of keyboards by controller / not using pro micro
IIRC, LTO_ENABLE saved me like 30% so do ensure that's working, and you can save about 10% if you cut the font support and data portion out of the OLED driver (as the logo art is a large blob, and fonts work by using 1 array to index into another, even when it is sequential such as for the logo). Manually hunting for and removing those last few sprintf also made a difference. ATM I have a branch that is tinkering with direct custom OLED art instead of using fonts, if I also enable font support I get 10.5k free, with just my OLED usage 12k free, with OLED_ENABLE=no 14.7k free. So I halved the usage cost, 5% overall? I'm not optimised or done, but just want to point out there is potential to look at unused pieces of QMK and cut them out via the preprocessor, and I haven't looked at the backlight api/driver.
-
QMK modifier stripes for OLED display.
You can take a different space-saving approach, especially for the 32x128 OLEDs. I've been tinkering with custom Modifiers labels, layer names, as well as Caps/Num/Scroll lock state notifiers, as this allows far more letters per row than the stock font (and doesn't waste a load of firmware memory to have the bitmaps for those as well as another block mapping them to positions). Even if you use 5 rows for all those state displays, you have a large 32x88 area to put whatever animation you want, and with a custom direct 'font' you could do things like Matrix falling characters.
-
after only been using staggered keyboards and having fatigue when typing on non split keyboards, i finally did it. I joined the ortholinear split keyboardworld. will need to learn how to type in a competely new way but it'll be worth it. lily58pro
If you set up a local QMK build, you can tell it to use Right side as master, and reverse the rotation of the OLEDs to face inwards. Or work on you own contents that fits a horizontal orientation. E.g. WIP.
What are some alternatives?
qmk-keymap - My keymap & reusable QMK gems
STeMCell - STM32F4 breakout board in pro micro pinout. Designed mainly for ergo split keyboards.
zmk-config-dactyl-manuform-4x5
cantor - Cantor keyboard, a 42 key diodeless split keyboard.
iris-keyboard-keymap
Lily58-Acrylic-Case - Lily58 case inspired by the Arisu acrylic case created by FateNozomi.
qmk_firmware - keyboard controller firmware for Atmel AVR USB family
qle - QMK Logo Editor
miryoku - Miryoku is an ergonomic, minimal, orthogonal, and universal keyboard layout.
qmk_firmware - Open-source keyboard firmware for Atmel AVR and Arm USB families
keygen - An(other) algorithm for generating optimal keyboard layouts.
qmk_firmware - Open-source keyboard firmware for Atmel AVR and Arm USB families