does that actually require recompiling? i would have expected that via/vial would be able to do that
1 Like
Yes. Via only change keybind, not Numlock behavior.
You also canât do advanced layering with Via. No tap dance, for instance. No script, no numlock (which is just script), etc.
And Via (web interface) actually straight up dont work with even the main qwerty keyboard, which have 4 layers, and they enter different layer depend on the current layer of the keyboard through a script (for the Fn lock) â one with the F1 through F12 on base layer, one with the Fn key pressed on the base layer, one with the media control (volume, settings, etc), and one for the Fn key pressed on the media control. You can map normal keys all you want, but if you want to change this 4-layer toggle behavior, you need to recompile.
Missed opportunity for the ARGB macropad, you can use backlight on a key for the numlock.
Fortunately, the QMK documentation is decent enough. But the QMK toolbox donât work with frameworks, and the framework keyboard github repo is kind ofa nightmare, with like, 10 forks off of different stages, and 10,000 other boards to get you distracted.
Not saying it isnât a mess, but once you know what you need, it feels no harder than normal. Regarding the 10k other boards, well, thatâs how QMK from source always is. You just make a shortcut to the folder for the keyboard(s) youâre working on & you never see the rest.
The firmware version thatâs shipping still looks to be v0.2.9, so:
clone -b v0.2.9 https://github.com/FrameworkComputer/qmk_firmware.git
Custom QMK firmware? - #14 by MJ1
Clear eeprom step: Custom QMK firmware? - #31 by MJ1
2 Likes
maybe a discussion for general or 16 categories, but more than two years on, this has ended up being a pretty big misstep on the 16. Iâm sure some of the community members are rather annoyed as I am that custom keyboards are still out of reach years into the product cycle, but there are a couple other effects of the lack of input height.
I imagine the hype around the 16 could have remained much, much more powerful had kalih or cherry switches fit. Custom and ergo keyboard spaces arenât actually very big, but only being able to show off swapping a macro pad in or move the keyboard left and right is kind of disappointing on launch, and especially so as the 16 shipped and community got their hands on it. In the current availability, the customization is more of a plaything and language accessibility option than a real feature, considering no one actually has an ortho or split 16 outside of the framework office (nod to the pressure sensitive piano module and keyboards that fit x-y but have to be removed before closing the lid though).
Iâm somewhat worried the one key will be unprofitable for framework (considering the usual size of keyswitch companies, and how different it is from normal framework product distribution) and itâs also a bit of a shame the one-key has to be developed with dollars otherwise useful for more generations of the 16.
I will definitely be making a keyboard when one keys become available, and Iâm sure theyâll see some use outside the framework community as the new crown lowest-pro switch. Itâs just a miss itâll be a feature so divorced from the release of the 16, and one that mightâve taken away dev time, particularly when there are really low-pro consumer available options framework could have designed for.
1 Like
noticing today: the One Key page has been updated. the currently out of stock listing says âpack of 9â now!
4 Likes
âFramework CEO Talks 5 Year Journey & Laptop 16 Updatesâ [18:00-19:55] talks about still working on the keyswitch system to enable custom keyboard layouts, not available yet, but âgetting pretty closeâ. A custom lattice could be âa laser cut plastic pieceâ.
[no clue is given on how keys communicate signals, guess they still need to be wired somehow if that still fits the thickness, or traces printed on grooves in the plastic piece. Or maybe adjacent keys link into a chain and no wires are needed underneath them.]
2 Likes
from the images we had I assumed the lattice would be a pcb with solder pads on the edges of the switch-holes. laser cut plastic raises more questions than it quietsâŚ
maybe the idea is a thin base pcb with solder pads, then the plastic lattice keeps lateral forces from breaking the solder (in presumably unlikely events)?
1 Like
Weâre getting close to developer availability.
6 Likes
if perchance the electrical / physical design is finalized right now (just supply and distribution to work out) could a footprint be released early so developers already have pcb designs by the time one-keys arrive at their doors?
if âdev availabilityâ starts with a github update and shipping of modules is even further away that makes sense too
I agree totally with your sentiments, and have taken some flak for saying so.
Unfortunately, I feel that all the warm words about âengaging the maker communityâ (etc etc) may appear cynical in light of the attitude towards keyboard customisation identified in your post. Of course others will assert that hardware hackers are well catered for by Framework - you can choose a different colour bezel for the screen, or swap out an input module.