-
Notifications
You must be signed in to change notification settings - Fork 192
Create a more interactive and clean CLI #624
Comments
So do you know if we can achieve the "goal" with all the described wishes using the current Aside of the PR #623 for the plugin based approach, is there any work done on this matter? I might try to help here. |
I don't know if The thing that bothers me with
The only related work that has been done is #623 as far as I know. That is on going in the sense that the framework is there and we're now porting old commands over. If you'd like to investigate if |
Rationale:
The current CLI can be described as a vertical scrolling log where the bottom line is interactive and allows for command inputs that get displayed in the log. While it gives a quick historical overview, it is not suited for interactive inspection of data such as Blocks and Transactions.
Event logging is interlaced with command history and can clutter the view. Error messages can even disrupt the proper representation of the statusbar (see below). In short, there is enough room for improvement
Goal:
Create a clean interactive CLI. The mitmproxy CLI is a great example how interactive and clean a console application can be. It uses the urwid library for the heavy lifting (beware it has a steep learning curve).
CLI wishes:
The text was updated successfully, but these errors were encountered: