Login to OSNews
Username or Email
Designing Command-Line Interfaces
on Fri 5th Aug 2011 17:42 UTC
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 484143
To view parent comment,
To read all comments associated with this story, please
RE: CLI != text only
on Tue 9th Aug 2011 00:33 UTC in reply to "
RE: CLI != text only
"I admit, it's fun to think about playing video on character-cell displays. Yet I also think that many people confuse CLI's as something that lives within a text only terminal.
A less limiting version of CLI's would allow for graphical displays."
Yes, this is actually what I meant by my maps query interface example under the CLI Article. The GUI part should remain, but a CLI query engine could be added. Something like Autocad or SQL software uses.
The CLI should function with or without the GUI portion to give the user maximum flexibility.
I agree 100%. It seems my understanding from other comments here is that a CLI = less GUI. It shouldn't be. You can have CLI's in the form of terminals flying around all over your favorite desktop environment, express yourself with the power of CLI commands on any of that window terminals, while watching high definition videos or (3d videos) at the same time. This is the future.
We can't just revert to the old dumb terminal of the ancient Unix days.
Sign Up For The OSNews Newsletter!
Friends & Fans
OSNews Privacy Statement
Notice to Bulk Emailers
© 1997-2017 OSNews Inc. All Rights Reserved. OSNews and the OSNews logo are trademarks of OSNews.
Source Code © 2007-2017,
, except where noted
Reader comments are owned by the poster. We are not responsible for them in any way.
All trademarks, icons, and logos shown or mentioned in this web site are the property of their respective owners.
OSNews.com uses icons from the
© 2008 John Resig
Reproduction of OSNews stories is permitted only with explicit authorization from OSNews. Reproductions must be properly credited.