About three years ago I was working on a TUI input deck using a Raspberry Pi 2 and the NoIR camera module and AR orientation markers on the surface for drawing the UI in my cybre helmet.
I should revisit that project this winter.
@er1n figure I can probably get much more reasonable input processing speed out of the Pi 3 (or a Rock64 if I have to) - the pi 2 just wasn't up to it at the time
@djsundog dj cybredog
Nice thing about separating input and output in a mixed TUI/AR environment is that you can move read-only bits of UI data off of the touch surface - touch an area at an edge, scroll a menu off the side of that edge, no finger obscuring your view of the selector (for instance - you can, of course, build in 3d off the surface (and can calculate the three-axis orientation of a QR code for some cool effects))
@djsundog one thing i've always wanted to do, that a TUI+AR setup sounds great at, is:
run command A, use its stdout as the stdin of BOTH command B and C
how the fuck do you represent that as a 1 dimensional command? i haven't figured out how to do it in bash
tee >(process1) >(process2) >(process3) | process4
@riking (but yeah, TUI is great for multiplexing inputs and outputs because it's easy to represent graphically - pure data does great at this as well due to its graphical nature)
This is a private instance that @firstname.lastname@example.org is using for development and testing.