https://youtu.be/oFRx_QxzET8 by @lone maple
In this demo, Alex shares the latest updates to the Terminal UI feature.
1 messages · Page 1 of 1 (latest)
https://youtu.be/oFRx_QxzET8 by @lone maple
In this demo, Alex shares the latest updates to the Terminal UI feature.
We need help deciding which TUI to make the default… 🙏
(both are hidden behind an experimental flag at the moment)
I think my vote goes to the inline one. It's closer to how "normal" CLI tools work in terms of outputting logs compared to being a fully featured TUI.
I would probably use the other one when I need to debug something or go back to understand how/why something broke. But most of the time (hopefully) I don't need to debug, I just need to see my pipeline pass.
I would vote for inline as well. Like @raw plaza said, most of the time I would not interact with the pipeline, I would need interactive one when I need to debug. Also, I found visualization of inline really amazing, and easier to understand when I see together with pipeline logs
Something closer to inline makes sense as the default to me as well. I definitely want interactive for debugging, but inline is clearer for the iterative loop you mentioned. My only concern is for projects with more than say 32 concurrent tasks, this could become unreadable. If that sounds unreasonable I know of linear algebra libraries that frequently setup big build matrices to catch numeric instabilities introduced between any 2 versions and across 4 compilers and 3 precisions, If any of of those 24 entries creates multiple vertices that could quickly become unreadable.
I agree that inline is better for quick glance but I wish there was a way to have a compact and verbose version. A compact version would only output the stderr/stdout from the commands (segmented by Pipeline) within the pipeline and the verbose one would show all the details (eg: cache layers, folder/file transfers etc.)
I agree that inline is ideal as long as it stays readable. Maybe in the future it could default to showing user-defined pipeline names, and collapse individual operations, to keep the visual complexity lower?
That would be great!
+1 - varying degrees of verbosity makes a ton of sense; there are already a few flags like that in the progress UI library, lots of room for further exploration