-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Campaign to Save the CLI #161
Conversation
e273f6d
to
f762993
Compare
f762993
to
4700f99
Compare
4700f99
to
54096fb
Compare
54096fb
to
d1b8c59
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is fixed in #182
|
Fixes #128. Requires #158.
I should clarify my aim is to get it working and to make it pretty later (cf. #172).
Part of my goal in this PR is to make #147 potentially easier. The CLI is intentionally aiming to be a highly simplified event/queue manager, thus I aim to clear the event's status frequently in order to reuse it later. The TUI is, to my knowledge, never waiting on more than one event at a time. Therefore we have not need to have multiple events. If we do have some place where we are waiting on multiple, then we can have two different ones at that time. This would make the code much simpler, leaner, and easier to reuse.
What I imagine therefore, from this PR, is extracting all the event/queue code from the TUI, the CLI, and the GUI, into its own class module.