smartknob VS i3

...it's a spring and a servo. Or a brushless motor.

https://github.com/scottbez1/smartknob

...or any not-bottom-end-of-market steering wheel for driving video games.

I made a rotary input device that provides software-defined "virtual" detents and end-stops, implemented using a BLDC gimbal motor. It can dynamically switch from completely smooth unbounded rotation, to having detents with configurable spacing and strength and "end-stops" that spring back if you try to rotate past them.

https://www.youtube.com/watch?v=ip641WmY4pA

It's got a round LCD on the front of the knob (wired and supported via the hollow shaft of the motor) and uses the flex of the PCB and strain gauge sensors (in the latest revision, simply SMD resistors whose resistance changes when stretched) to detect when the knob is pressed down.

It's open source hardware and software - https://github.com/scottbez1/smartknob

HN folks might appreciate that it communicates with host software on the computer via protobuf-encoded USB serial messages -- nanopb is awesome for embedded C protobuf support, and having the defined schema, autogenerated serialization code, and compile-time type safety is so much nicer than ArduinoJson or hand-written binary protocols!

I'd love to get it hooked up to some real software eventually (video editors or home-assistant control are my 2 main ideas), but it's really just been a fun project to tinker with and try out some new ideas and parts I've never used before.

GitHub

I'm trying to design a smartknob based off Scottbez1's design (https://github.com/scottbez1/smartknob), but with a stripped down feature set. However I can't seem to get the magnetic sensor to work properly - it's an MT6701 connected to an ESP32 via SSI.

Thank you so, so much for finding it. Unfortunately on eBay its not cheaper and ali doesn't have it cheaper either. It looks like an out of production item, like when I wanted to make this https://github.com/scottbez1/smartknob and it was gone except when sparkfun got a few.

While I believe Memory Saver was a great improvement, it only works if the tab is hidden or the window minimized. I recently learned the required state is not triggered if the tab is open but on another virtual desktop. At least this is the case with many of not all Linux window managers. Some of the many discussion threads on the topic:

https://github.com/i3/i3/issues/4353

> This is very true, and unfortunately there are very few people working on linux accessibility (including not me! I am part of the problem!).

Accessibility work itself ironically suffers from an accessibility problem. I brought up i3wm above, the issue for that is pretty illuminating: https://github.com/i3/i3/issues/3393

It's not that the devs are saying "this doesn't matter", the devs behind one of the most popular tiling window managers in the X11 ecosystem are saying, "this does matter, but we don't know how to fix it. We don't know what changes we'd need to make to get Orca working."

It's a really fundamental breakdown that's kind of a tragedy because I honestly believe that if accessibility communities were more heavily baked into testing and development in Linux and if this wasn't treated like two separate worlds, it would be better for everyone -- fixing accessibility concerns very often improves interfaces across the board and makes them more powerful.

But... how do you bridge that gap? I don't really know, I tried looking into Orca to see what would need to happen here and bounced off of it pretty hard, it's not a very approachable tech stack and there aren't tutorials or getting started guides. And on the other side of the issue I can preach about needing accessibility input during interface design, but I'm not in a position to give specific advice because I don't use screenreaders or alternate control schemes and I don't know what the biggest problems are.

The people who need to be involved in that process can't get involved because there's a tech barrier in place even for technically inclined people, and because the underlying software locks them out from the start. i3wm isn't ever going to get someone who's intimately familiar with Orca to jump into the conversation because the people who need to use Orca can't use i3wm. So that leaves the people who can address that tech barrier, but they don't know what to do or how to approach the problem because of the lack of involvement and because the communities are isolated from each other. So it's a chicken-and-egg problem and I don't know how to solve it.

This is partially why i use tools like i3 (/ sway). i like the tool; it works extremely well for me; the design has stayed the same for 20 years; there's no profit motive to come along and fuck everything up. it just works. it is boring in the best way possible.

I use MacBook Pro (Retina, 15-inch, Mid-2014) with Manjaro as OS using i3 as a window manager. It isn't perfect, but I'm thrilled with it. I have been a Mac OS user for the last 15 years and wouldn't change what I have now for a Mac OS because I don't need more than what I'm using for development.

Even though, we have moved the official i3 support channel to GitHub discussions, i3's biggest community is still on reddit and if things continue like that there is going to be a lot of helpful content on an increasingly closed platform.

for example, take i3. https://github.com/i3/i3/issues/4478

For daily usage I really like kubuntu with i3wm, but it takes some configuration and getting used to the shortcuts, but it's well worth it