I've set this to plainbox and set the status to triaged. I have thought of a way to run new-style jobs that have richer capabilities to express their UI. Those would be a new 'plugin' (here probably 'textland') and the way we'd run such jobs would be different. PlainBox would become a textland server hosting a display made by another program in another process. That other process could them be written to a rough set of guidelines and use simple widgets like text gauges.
Alternatively we could offer tests a side channel to pass additional events across but I don't like that (smells like debconf) approach.
Ultimately this bug boils down to having good UI on both graphical tests (using a zoo of toolkits) and on command line tests (using nothing or textland as we go, maybe)
I've set this to plainbox and set the status to triaged. I have thought of a way to run new-style jobs that have richer capabilities to express their UI. Those would be a new 'plugin' (here probably 'textland') and the way we'd run such jobs would be different. PlainBox would become a textland server hosting a display made by another program in another process. That other process could them be written to a rough set of guidelines and use simple widgets like text gauges.
Alternatively we could offer tests a side channel to pass additional events across but I don't like that (smells like debconf) approach.
Ultimately this bug boils down to having good UI on both graphical tests (using a zoo of toolkits) and on command line tests (using nothing or textland as we go, maybe)