Skip to content
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

Topic/cli studio commands 49 #50

Merged
merged 18 commits into from
Jul 28, 2020
Merged

Conversation

biohazard999
Copy link
Contributor

@biohazard999 biohazard999 commented Jul 26, 2020

This fixes #49.
Introduce a common architecture between interactive mode and cli-studio namely TastyCommander.
Preps also for #33

@biohazard999
Copy link
Contributor Author

biohazard999 commented Jul 27, 2020

@hazard999 the main problem when thinking about the cli-studio is if we keep using Terminal.Gui we are totally out of control. If we use system-terminal we loose built in controls and mouse support. On the long run I guess going with a own gui would be better cause we have more control.
It also is a little bit more fresh and doesn't use ncurses, so less dependencies to worry about.

#46 and cli studio need the same sort of abstraction

basically we need something like XtermSharp but over the wire

@biohazard999 biohazard999 marked this pull request as ready for review July 28, 2020 10:17
@biohazard999 biohazard999 requested a review from hazard999 July 28, 2020 10:18
@biohazard999 biohazard999 merged commit 4627c9a into master Jul 28, 2020
@biohazard999 biohazard999 deleted the topic/cli-studio-commands-49 branch July 28, 2020 11:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Execute commands in cli-studio
2 participants