Linked by David Adams on Fri 5th Aug 2011 17:42 UTC
Graphics, User Interfaces Since we're on a CLI kick today, here's an "attempt at presenting some of the most important guidelines for CLI design."
Thread beginning with comment 483910
To read all comments associated with this story, please click here.
For starters...
by shotsman on Sat 6th Aug 2011 06:31 UTC
shotsman
Member since:
2005-07-22

The article assumes the command-line utilities are to be used on a *nix system (e.g. GNU/Linux, BSD, Mac OS X, Unix), and it will frequently reference to common tools on such systems.

If you are only going to consider *nix then IMHO, you are a mission that is doomed to failure.

If you are going to provide guidlines on what should go into a decent CLI then you MUST consider other systems. By failing to do that you are setting out on a marathon with one leg in plaster.

For example,
As I stated before the hierarchical help system used in the VMS DCL environment is wonderful. It makes a flat help system redundant. So why can't to divorce the help system from the application?
Supply the binary and the help file that is accessible through the generic shell help widget (or whatever).

Lets get away from the limitations imposed on us by the Original Unix devs who were working on very slooooowwwww devices (eg Teletypes, ASR33, 110Baud). Times have changed.
So should the command line.

Now I'll take cover because I expect to get blown away.

Reply Score: 7

RE: For starters...
by siride on Mon 8th Aug 2011 03:54 in reply to "For starters..."
siride Member since:
2006-01-02

I hate info pages. I find manpages much easier to manage. It's for this reason that when I find documentation or guides or books online, I always go for the "entire manual in a single PDF/HTML page" option instead of the piece-by-piece option. It's much easier to scroll around or use search than navigate a hierarchy that someone else devised and that may not actually organize things in a way that helps *you* find what you need.

Reply Parent Score: 3