文本用户界面设计参考？
有关于文本用户界面设计的好书或其他参考资料吗？我对图形用户界面不感兴趣。我对良好的命令行和脚本界面的可用性感兴趣。
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
有关于文本用户界面设计的好书或其他参考资料吗？我对图形用户界面不感兴趣。我对良好的命令行和脚本界面的可用性感兴趣。
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
接受 或继续使用网站，即表示您同意使用 Cookies 和您的相关数据。
发布评论
评论（4）
您的界面应遵循 ESR 在艺术中所描述的“最小惊喜规则” Unix 编程。如果您的程序支持命令行选项，请确保它们具有传统含义。请务必阅读有关CLI 和可视化界面之间的权衡的章节。
Your interface should follow the Rule of Least Surprise as described by ESR in The Art of Unix Programming. If your programm supports command line options, make sure they have the traditional meaning. Be sure to read the chapter about Tradeoffs between CLI and Visual Interfaces.
IBM 开发了一个称为“通用用户访问”的标准。通用用户访问基本界面设计指南已以 BookManager 格式和 HTML 此处。
该指南是作为开发 3270 应用程序的标准而编写的。在我看来，最重要的部分是功能键标准和颜色标准。
IBM developed a standard called Common User Access. The Common User Access Basic Interface Design Guide has been published in the BookManager format and in HTML here.
The guide was written as a standard for developing 3270 applications. In my opinion the most important parts are the function keys standard and a color standard.
我会使用一个最喜欢的程序作为此类事情的参考。您认为哪种命令行实用程序具有良好、高效的界面，您可以在其上建模您的程序？用它。
更新：所以我认为我需要对此进行一些修改。它被过于字面地理解了。谷歌和这个网站证明了互联网是非常民主的。流行的东西会以某种方式被复制、链接或复制。
鉴于此，再加上个人使用计算机的经验，我认为基于个人经验和对所提供解决方案的考虑，得出一个比较好的解决方案是可行的。
例如，vim 是一个很棒的程序。很多人都使用它并且喜欢它。但这种类型的接口可能不适用于版本控制系统（至少不能很好地使用）。但这两个界面对于它们所适合的用途来说都非常优雅。另一方面，vim 类型界面可能适用于版本控制系统的一部分——例如提交对话框。
现在，我知道 vim 通常用于 svn（在基于 UNIX 的操作系统上）的“提交对话框”（默认情况下）。这只是混合两种风格的界面以提供一个有凝聚力的解决方案的示例。
I'd use a favorite program as a reference for something like this. What command line utility do you think has a good, efficient interface that you could model your program on? Use it.
Update: So I think I need to revise this a little. It was taken way too literally. Google and this site proved that the internet is very democratic. What is popular is replicated, linked to or reproduced in someway.
Given this, plus one's personal experiences with computers, I think it is feasible to derive a pretty good solution based on personal experience and consideration for the solution to be provided.
For example, vim is a great program. A lot of people use it and love it. But that type of interface is probably not going to work (at least well) for a version control system. But both interfaces are very elegant for the purpose they suite. On the other hand, the vim type interface might work for a section of the version control system -- the commit dialog for example.
Now, I know that vim is normally used for the "commit dialog" (by default) for svn (on unix based OSes). This is just an example of mixing two styles of interfaces to come up with a cohesive solution.
您应该看看 Ubiquity 背后的一些想法以及一些想法 Aza Raskin 谈到的，似乎是同一类事情。
You should have a look at some of the ideas behind Ubiquity as well as some of the ideas Aza Raskin talks about, seems like the same kind of thing.