You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 13, 2023. It is now read-only.
How would you go about introducing progress visuals(common to see something like [=====---------]49%) or busy indicators(I've seen a project for this, maybe it was in zsh but should be portable to general CLI output from Rust).
I recall using a CLI app, Hashcat last year that would show several lines of what was going on followed by many lines of status of the computation that was updated and below that were some interactivity options along with shortcut keys that could pause/stop/save/etc the computation.
I guess these would both be a better story as async support develops further in the year, but a neat feature for quicli to be able to offer easily setting up? Item (key, description/label, function to call), view(list of items arranged horizontally I guess?)... or is that going too far into TUI land?
Let me know if you'd like me to split the two features into separate issues.
The text was updated successfully, but these errors were encountered:
How would you go about introducing progress visuals(common to see something like
[=====---------]49%
) or busy indicators(I've seen a project for this, maybe it was in zsh but should be portable to general CLI output from Rust).I recall using a CLI app, Hashcat last year that would show several lines of what was going on followed by many lines of status of the computation that was updated and below that were some interactivity options along with shortcut keys that could pause/stop/save/etc the computation.
I guess these would both be a better story as async support develops further in the year, but a neat feature for quicli to be able to offer easily setting up? Item (key, description/label, function to call), view(list of items arranged horizontally I guess?)... or is that going too far into TUI land?
Let me know if you'd like me to split the two features into separate issues.
The text was updated successfully, but these errors were encountered: