sure, close enough
ok sure.
to me the problem seems a little simpler: you just need
- three encoders and three buttons attached to the rpi on GPIO,
- a screen that’s at least 128x64 pixels (if its bigger you’ll want to rescale to maintain legibility.)
that is the minimum. then push2 just acts as a midi controller and you can jump right into helping us figure out how to make apps more hw-agnostic or whatever. (maybe that means abstracting “gridlike” things between weaver and the matron device management stuff, maybe in lua - the latter seems more sensible to me but that’s just an opinion.)
if you want to use the tiny screens on the push, well, we don’t have any stuff that looks like that so it is divergent on several levels and certainly needs its own “driver” - more problematically, it also suggests particular UI design decisions that are different from the decisions one would make with a single screen instead.
ah, heck, ok just actually looked at the push2 specs. so its a big screen. great, that makes it easier. it’s still sort of a clunky fit - UI for norns hw will not be optimal there - but enough to work with.