The command-line tag has no wiki summary.
12
votes
3answers
243 views
Can I optimize this command-line interface?
I am designing a command-line interface for users and administrators to interact with an online radio system. One of the administrator tasks is assigning songs and albums to various genres. This is ...
5
votes
2answers
61 views
Masked password characters in a GUI vs terminal
In a GUI form, or for example a login box on a website, it's usual for masked characters to appear like ********* as you type out your password.
But in terminal applications, for example ssh, this ...
3
votes
4answers
171 views
How to improve this retro CLI web app ux?
I want to improve the retro-ness and the coolness of this CLI (command-line interface) for a web app. I just want it to give the user the experience of typing into a 1980s library terminal, at, say, ...
2
votes
1answer
127 views
CLI and Recall Memory [closed]
Is there any evidence that using a command line interface will improve a user's recall memory?
or...
Do users with better predispositions to recall abilities do better with command line interfaces?
...
1
vote
2answers
87 views
How to design user friendly aliases for command line interface element identifiers?
I've run into this problem, i'm making a CLI that enables the user to make bookmarks, notes or comments on elements. Each element has it's internal unique identifiers and usual entity stuff. The ...
1
vote
2answers
150 views
What are the minimal guidelines for a dual command-line / gui interface?
I'm designing a website that has a constant CLI and optional GUI's for every functionality. What i'm basically doing is an automated form generated for each parameter and a description.
I'm also ...
0
votes
2answers
152 views
Drawing a chessboard with unicode characters [closed]
Wondering the best unicode characters to draw a chessboard... particularly the right combination of square and row/col delimiters (if any) to give a readable layout in a terminal window. Here's what ...
-1
votes
1answer
83 views
explaining/documenting an intricate mechanism
I'm torn between two worlds, I have this very intuitive (but intricate) mechanism in a command line tool, and I'm wondering as to what extent I should explain this.
I can go the simple way, not ...
