11–20 of 83 posts
git
it was awful, it is getting better and I think it's a good example in several occasions (I mean when it's not an unpredictable sequence of commands that need to be passed to accomplish something outside of a regular workflow)
I like npm-check https://github.com/dylang/npm-check it has a really useful and easy to use UI, on of the nicest terminal UI driven applications I have used. Edited: to use TUI instead of CLI
TUI is not CLI. htop and these curses interfaces was TUI
git
git
it was awful, it is getting better and I think it's a good example in several occasions (I mean when it's not an unpredictable sequence of commands that need to be passed to accomplish something outside of a regular workflow)
There are many different teams within Heroku that need to provide interactions for developers via CLI whether its for dynos or data services. The guide was a way to codify building a consistent interaction that all product managers and engineers could follow. Disclaimer: I work for heroku.
Serverless ( https://serverless.com ) has a nice experience. I believe it is built using inquirer.js ( https://github.com/SBoudrias/Inquirer.js ) I've recently built an internal tool with inquirer and it was a really nice development and user experience. I haven't figured out the best way to test the interactions though. termUI in go is also nice if you need graphing and viz for a dashboard like command line.
I would recommend that you check out the Heroku CLI Style Guide: https://devcenter.heroku.com/articles/cli-style-guide There are many different teams within Heroku that need to provide interactions for developers via CLI whether its for dynos or data services. The guide was a way to codify building a consistent interaction that all product managers and engineers could follow. Disclaimer: I work for heroku.
The only thing I'd personally ask for is if you offer an interactive interface, make sure you can execute the exact same commands on the plain CLI. Also (yeah, two things) support --help and --version (as well as -h and -v) out of the box.
Color, layouts (other than those required for readability), and other things just don't really matter as much, IMO.
https://github.com/nvbn/thefuck
[TL;DR -- typo a command, type 'fuck', will run the command you should have run]
Serverless ( https://serverless.com ) has a nice experience. I believe it is built using inquirer.js ( https://github.com/SBoudrias/Inquirer.js ) I've recently built an internal tool with inquirer and it was a really nice development and user experience. I haven't figured out the best way to test the interactions though. termUI in go is also nice if you need graphing and viz for a dashboard like command line.
I think many/most Node TUI's use Inquirer. I have mixed feelings about it. Python has several library's that provide lower-level constructs for building CLI and TUI's. Then they provide examples for using the library to implement a common pattern or prompt. Inquirer gives you some ready-made prompts but doesn't provide any help/convenience for creating your own prompt. It seems like the wrong level of abstraction.
Inquirer is def the HTML inputs of the terminal but I got pretty far with it. My use case was Fairly Simple™ though. What other UI components do you think it's lacking?