vlandeiro
Joined 6 years ago
Karma
30
Submissions
7
Member since
Sep 26
Recent submissions
Comment · 1 year ago
Yes, Yakari is a great comic (BD really). I thought about the name for a bit, it was between Yakari and Little Thunder (Yakari’s horse)!
Comment · 1 year ago
Yes, in that case TUI stands for “Terminal User Interface” [1].
Examples of TUIs are top, vim, and emacs
[1] https://en.m.wikipedia.org/wiki/Text-based_user_interface
Comment · 1 year ago
Ha! Great minds!
Thanks for sharing, I’ll take a look at your project.
I looked on github for similar repos before I (re)started on this but couldn’t find anything
Comment · 1 year ago
Yes, you got the point!
Re: what the user is typing should be displayed in the bottom left of the window as they are typing. It’s not really fancy autocomplete, rather it’s keyboard shortcuts.
I answered to a different comment [1] that found the video confusing as well. Let me know if that explanation helps or if the UX is still confusing to you. I’ll need to come up with a better video example.
Comment · 1 year ago
Yes this works for all CLIs but there’s a caveat: yakari requires a TOML configuration file that defines the menu for that CLI. For instance, here’s the definition of the git menu [1].
Gooey is much more automated but limited to Python because it requires adding a decorator to the CLI code.
In other words, yakari is just a command runner with a nice — but apparently confusing — UI.
[1] https://github.com/vlandeiro/yakari-menus/blob/main/git.toml
Comment · 1 year ago
Thanks for the feedback! Seems like the video is confusing to several people so I’ll work on improving it.
I can explain the first steps of the video here:
1. ykr git starts the TUI configured for git. This display a menu where each option is accessible via a keyboard shortcut.
2. User inputs “b”, which opens the “branch” menu.
3. User inputs “l” which runs the command to list all the branches and display them to the user. Hitting ctrl+r hides the result window.
4. Still in the branch menu, the user inputs “c” to create and switch to a new branch. This prompts them with a branch name and the user inputs “demo”. Submitting the branch name calls git checkout -b demo and display the results to the user.
The remaining steps show similar interactions to add and commit a file, as well as deleting a branch.
Does that help understanding how the UX works or are there still confusing parts?