ui: better progress bars #2148
Labels
p1-important
Important, aka current backlog of things to do
refactoring
Factoring and re-factoring
ui
user interface / interaction
Currently we have progress bars for each individual file, which is not helpful when we have many of them. Furthermore when using several threads - a common case - they just fill up a screen, with no indication of where we are.
So I propose switch to using one progress bar for a single mass operation. There was a question from @efiop: how do we show all the filenames that are being processed? I would say we can only show single file taking longest so far like:
Or we can list them in a second line after the progress bar, but I don't think it matters too much.
Another thing that we should probably approach simultaneously is how we code that. Now we pass flags like
no_progress_bar
, sometimes deep enough to make code ugly. I suggest using global progress bar variable, like logger instances so we won't need pass anything. To guarantee that scope won't leek we can use context managers:Or wrap iterables:
To hide progress bars in all called code, without any flags passing:
The text was updated successfully, but these errors were encountered: