this should be easy to do. that is, use only the sclang+scsynth side of norns to act as the SC side of a tidalcycles session, host the haskell side on a laptop. make a norns engine that just starts
that said - i’ll admit that wasn’t immediately successful using the SuperDirt quark on norns. (it installs ok, but class isn’t recognized - weird.) other quarks i’ve tried are fine. so it will take some hopefully-small amount of fiddling.
not sure i can agree! sorry. in a nutshell i’d argue that affordance-based design is a poor fit for a minimal, hackable interface canvas, and your example of a “broken pattern” is really two equally viable patterns. but maybe on another thread.
this would be good to see. “composition” in that sense is technical and touches both on software design and interface design, but is more about the former - sorry about that.
but it would be interesting for me as a developer to see a collection of proposed specs on how to make best use of a minimal interface. of course idea of norns scripting is to also make the implementation itself maximally accessible, even for functionally dense interface specs.