上下文相关对话框的视图
我最近与同事讨论了在应用程序中使用上下文帮助,争论的焦点是现在是否需要它,或者是否许多公司都在这样做,但实际上并没有给最终用户带来任何显着的好处。如果我们的应用程序中只有 pdf 文件或 chm 文件而没有任何上下文相关帮助,我们会更好吗?我只是很好奇其他开发人员对此有何看法,主要是因为上下文相关的帮助设置起来有点痛苦,特别是如果您依赖少数开发人员。
I recently had a discussion about the use of contextual help in applications with my colleagues and the argument was if there is a need for it these days or if it's something that many companies do but does not actually have any significant benefit to the end user. Would we be better off having just pdf files or chm files without any context sensitive help in our applications? I was just curious as to what other developers think about it, primarily because context sensitive help is a bit of pain to set up and especially if you depend on a small number of developers.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
![扫码二维码加入Web技术交流群](/public/img/jiaqun_03.jpg)
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
据我所知,大多数应用程序似乎每个屏幕都提供一个主题。
如果您在对话框中看到不清楚的短语,您希望只需按 F1 即可进入主题。
但当然,评论者也是对的。如果它被认为是一件苦差事,并且该主题由表单的屏幕截图和机械重复的完全相同的文本组成,那么它不会有任何帮助。
当然,以这种态度创建的手册也不会再有任何帮助。
As I see it, most applications seem to provide one topic per screen.
If you see a phrase that is not clear in a dialog, you want to be simply able to press F1, and be in the topic.
But of course, the commenters are also right. If it considered a chore, and that topic consists out of a screenshot of the form and the exact same texts mechanically repeated, it won't be any help.
But then of course, the manual won't be any more help when created with such attitude either.