I don't post my private projects because after work and kids I have barely any time for them.
The keyboard is going to be mechanical with Bluetooth, trackpoint and maybe tiny OLED display. The whole point of this is that it runs my software and so I can put on it whatever layout, logic and other shenanigans I want.
I already have it working as both mouse and keyboard and got two sets of Cherry MX silent red switches.
While the trackpoint is working great, I don't yet know how I am exactly going to fit it between keys. An idea I have is to sacrifice one key completely and make it a trackpoint with a custom keycap (rubber red?)
The way this works is that controller detects that trackpoint is in use and maps some other keys on home row of left hand side to function as mouse buttons.
There is going to be microsd for software and configuration updates.
I have not yet started with plover. I just looked at the code and I know this is probably going to cost major effort to get it to run on STM32.
Sounds neat! Thanks for sharing. My only comment from research (no practical experience) is that I'd worry about the spring force of the MX making chording tiresome. I know the Georgi goes to some lengths to get switches with a lower force.
> I don't post my private projects because after work and kids I have barely any time for them.
I hear ya. I was excited because I've been mentally toying with the same project. But you know, first I need to finish my remodel, fix the truck, build a deck....
The keyboard is going to be mechanical with Bluetooth, trackpoint and maybe tiny OLED display. The whole point of this is that it runs my software and so I can put on it whatever layout, logic and other shenanigans I want.
I already have it working as both mouse and keyboard and got two sets of Cherry MX silent red switches.
While the trackpoint is working great, I don't yet know how I am exactly going to fit it between keys. An idea I have is to sacrifice one key completely and make it a trackpoint with a custom keycap (rubber red?)
The way this works is that controller detects that trackpoint is in use and maps some other keys on home row of left hand side to function as mouse buttons.
There is going to be microsd for software and configuration updates.
I have not yet started with plover. I just looked at the code and I know this is probably going to cost major effort to get it to run on STM32.
There is also this post from Plover developer on additional challenges to get it done: https://www.reddit.com/r/Plover/comments/6ucy15/stenography_...
I don't agree that this is necessarily a huge problem that can't be resolved.