The power of the Internet (connecting the planet) combined with the concepts of subcultures (everyone is interested in something) and blogging (your own syndicated column) never cease to amaze. My posting of some Microsoft UI Research around threaded email discussion was Slashdotted last week. Lots of good discussion ensued, but today a very cool thing happened. The actual Microsoft Researcher, Gina Venolia, posted in the comments section. I confirmed that her post is legit. More importantly she brings up some very good points that I’d like to share. I’ve split up her comment into sections for me to comment on, but her full text remains unchanged.
互联网的力量(连接地球)与亚文化概念(每个人都对某事感兴趣)和博客(您自己的联合专栏)相结合，永无止境。 我上周在Slashdotted上发布了一些有关线程电子邮件讨论的Microsoft UI Research 。 随后进行了许多热烈的讨论，但是今天发生了一件很酷的事情。 实际的Microsoft研究人员Gina Venolia张贴在评论部分。 我确认她的职务合法。 更重要的是，她提出了一些我想分享的非常好的观点。 我将她的评论分为几部分供我评论，但她的全文保持不变。
I am the person doing the work being discussed. I think that there are two things of note in the (maybe not too well written) article. The first is that you can get rid of the headers-and-message-viewer arrangement of most (all?) email programs. This is probably a good thing because it can turn a lot of clicking on headers into a continuous view. It's not exactly rocket science or novel - see the thread visualizations in www.dotnet247.com (e.g. http://www.dotnet247.com/247reference/msgs/34/170488.aspx) or www.lugnet.com (e.g. http://news.lugnet.com/cad/dat/parts/?n=4988&t=i&v=a).
我就是正在讨论的工作的人。 我认为(也许写得不太好)文章中有两点值得注意。 首先，您可以摆脱大多数(全部？)电子邮件程序的标题和消息查看器排列。 这可能是一件好事，因为它可以使标题上的大量单击变为连续视图。 这并非完全是火箭科学或小说，请参见www.dotnet247.com(例如http://www.dotnet247.com/247reference/msgs/34/170488.aspx )或www.lugnet.com(例如http： //news.lugnet.com/cad/dat/parts/?n=4988&t=i&v=a )。
True that the article I posted was an internal “puff” piece meant to let people know what’s going on inside Microsoft Research. It’s fair to say that the author of the piece is not a researcher in this field, and one can’t take an article like this written for a broad audience as a valid abstract of some fairly complex research.
的确，我发布的文章是内部的“吹捧”文章，旨在让人们知道Microsoft Research内部的情况。 可以公平地说，该文章的作者不是该领域的研究人员，并且不能将为广大读者撰写的此类文章作为某些相当复杂研究的有效摘要。
Her first point is one I agree with. The whole master-detail/headers-message paradigm goes against productive viewing of threaded discussion. While many sites, like those she mentioned, and many apps (SharpReader being the most notable, IMHO) push the envelope for threading while still maintaining the headers-message multi-paned approach, the concept isn’t exactly splitting-atoms-hard.
她的第一点是我同意的观点。 整个主从/标题-消息范式与对线程化讨论的富有成效的观察背道而驰。 尽管许多站点(如她提到的站点)和许多应用程序(SharpReader最引人注目，恕我直言)都在推动线程的发展，同时仍然保持标头消息的多窗格方法，但这个概念并非完全难以理解。
The second is that the visualization shows both the sequence of messages and the reply tree at the same time. (Emphasis Scott’s) No doubt about it, you've been able switch between both of these views in email clients for years. The sequence is good because you can see what new in a thread that you're coming back to; it's also good because people aren't replying to only the parent messsage, but things that they've read in the other branches. The reply tree is useful for obvious reasons. With this visualization you can do both AT THE SAME TIME, which is a good thing.
第二个是可视化同时显示消息序列和回复树。 (强调Scott的观点)毫无疑问，您已经在电子邮件客户端中的这两种视图之间切换了多年。 顺序很好，因为您可以看到要返回的线程中的新内容； 这也很好，因为人们不仅会回答父母的信息，而且会回答他们在其他分支机构阅读的内容。 出于明显的原因，回复树很有用。 借助这种可视化，您可以在同一时间完成这一切，这是一件好事。
I’ve always preferred applying additional thought around tough UI problems than the cop-out of a “toggle” between views. Rather than developing an opinion around the article, I took her very valid advice and read one of her published papers online. This excerpt from her abstract clearly expresses the intent of this research, which is certainly more than “yet another threaded email client” - again, emphasis mine.“We present a mixed-model visualization that simultaneously presents sequence and reply relationships among the messages of a conversation, making both visible at a glance. We describe the integration of the visualization into a working prototype email client. A usability study indicates that the system meets our usability goals and verifies that the visualization fully conveys both types of relationships within the messages of an email conversation.”
与视图之间“切换”的解决方案相比，我总是更喜欢针对棘手的UI问题应用其他思路。 我没有对文章发表意见，而是接受了她非常有效的建议，并在线阅读了她发表的论文之一。 她摘录中的摘录清楚地表达了这项研究的意图，这肯定比“还有另一个线程化的电子邮件客户端”要多得多，再次强调我的想法。“我们提供了一种混合模型的可视化效果，该可视化效果同时显示了对话消息之间的顺序和答复关系，使两者一目了然。 我们描述了将可视化集成到工作原型电子邮件客户端中的过程。 可用性研究表明该系统满足了我们的可用性目标，并验证了可视化在电子邮件对话消息内完全传达了两种类型的关系。”
She refers to research by Clark [(1996). Using language. Cambridge University Press.] that
defines utterances in face-to-face conversations as projects, subprojects and digressions, leading to five types of transitions (pair-wise relationships) between utterances: next, push, pop, digress and return.” Applying these concepts to the question of “What is a conversation” leads them to develop a visualization that expresses these constructs with as peers with full fidelity.
她指的是克拉克[(1996)。 使用语言。 剑桥大学出版社。]
将面对面对话中的话语定义为项目，子项目和题外话，从而导致话语之间的五种类型的转换(成对关系)：下一步，推送，弹出，题外话和返回。” 将这些概念应用于“什么是对话”问题，可以使他们开发出可视化的图像，以完全忠实的方式表达这些构造。
They acknowledge prior research and plot their accomplishments in a grid to show at a glance support for the Tree Model of a conversation versus the Sequential Model. Refer to the research document for details about each of these different research projects, such as Loom and ConverSpace. Note, however, that typical Usenet discussions offer some support for the Tree Model, but it’s clear that most interfaces break down around the display of sequentially ordered messages. It’s usually an either-or situation (a toggle.)
他们认可先前的研究，并在网格中标出他们的成就，以一目了然地显示出对话树模型和顺序模型的支持。 有关每个不同研究项目(例如Loom和ConverSpace)的详细信息，请参考研究文档。 但是请注意，典型的Usenet讨论为树模型提供了一些支持，但是很显然，大多数接口在按顺序排序的消息的显示方面都存在问题。 通常是“要么”要么“是”情况(切换)。
In the comments section, Gina mentions when many Slashdot users mentioned to me – IBM’s ReMail project. IBM includes improved support for conversation visualization with something called a “ThreadArc.” This is also an attempt a “mixed-mode” visualization to express both Sequence and Reply relationships between messages. ThreadArcs uses arcs to express a reply-to relationship between messages, and dots to represent each message, with those dots sorted left to right (in English) based on a user-defined sort, usually chronological. It is their belief that a ThreadArc presents a more stable visualization which allows the user to better see the evolution of a message thread over time.
在评论部分，吉娜(Gina)提到了许多Slashdot用户向我提及的时候-IBM的ReMail项目。 IBM通过称为“ ThreadArc”的功能改进了对会话可视化的支持。 这也是尝试“混合模式”可视化来表达消息之间的序列和回复关系。 ThreadArcs使用圆弧表示消息之间的回复关系，并使用点表示每个消息，这些点通常根据用户定义的排序从左到右(英语)进行排序。 他们相信ThreadArc可以提供更稳定的可视化效果，使用户可以更好地查看消息线程随时间的变化。
Gina ends her comment with a reminder to read the research and make your opinions, rather than trign to glean details from an article about the research. Point well taken.
吉娜(Gina)在提醒她时要提醒他阅读研究并发表意见，而不是通过Trign搜集有关该研究的文章的详细信息。 点好了。
The combination of these two things is, I believe, what makes this part of Grand Central novel and interesting. In current email clients and IBM's ReMail, you have to assemble an understanding of what's going on in a thread by looking a message at a time, navigating by clicking on headers, scrolling, etc. In this view it's all laid out at once, navigable with a scrollbar, shifting the burden from the cognitive to the visual system. This, I think, is a very good thing.
Instead of basing your opinions on a short article and a screen shot, I suggest reading a little deeper: http://research.microsoft.com/research/pubs/view.aspx?msr_tr_id=MSR-TR-2002-102
我相信，这两件事的结合才是使大中央区这一部分新颖有趣的原因。 在当前的电子邮件客户端和IBM的ReMail中，您必须通过一次查看消息，单击标题，滚动等等来对线程中正在发生的事情进行理解。在此视图中，所有这些元素都是一次布局，可导航的通过滚动条将负担从认知系统转移到视觉系统。 我认为这是一件非常好的事情。 与其将您的观点作为简短的文章和屏幕截图，不建议您更深入地阅读： http : //research.microsoft.com/research/pubs/view.aspx? msr_tr_id= MSR-TR-2002-102
Thanks, Gina, for reading my blog and helping spread the word about your research!
吉娜(Gina)，谢谢您阅读我的博客，并帮助传播了有关您的研究的信息！
翻译自: https://www.hanselman.com/blog/part-2-shadows-of-future-versions-of-outlook-the-researcher-speaks
扫一扫
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
