Revisiting Read Wear: Analysis, Design, and Evaluation

Total Page:16

File Type:pdf, Size:1020Kb

Revisiting Read Wear: Analysis, Design, and Evaluation Revisiting Read Wear: Analysis, Design, and Evaluation of a Footprints Scrollbar Jason Alexander 1, Andy Cockburn 1, Stephen Fitchett 1, Carl Gutwin 2, Saul Greenberg 3 1 Dept. of Computer Science 2 Dept. of Computer Science 3 Dept. of Computer Science University of Canterbury University of Saskatchewan University of Calgary Christchurch, New Zealand Saskatoon, Canada Alberta, Canada {jason, andy, saf75} [email protected] [email protected] @cosc.canterbury.ac.nz ABSTRACT having attended to the thumb’s location during previous In this paper, we show that people frequently return to visits, remembering it, and reproducing it accurately. One previously-visited regions within their documents, and that or more of these activities can fail. In their comparison of scrollbars can be enhanced to ease this task. We analysed navigation in paper and electronic documents O’Hara and 120 days of activity logs from Microsoft Word and Adobe Sellen [25] observed that people use fingers to mark Reader. Our analysis shows that region revisitation is a document regions in paper documents for easy return, and common activity that can be supported with relatively short that equivalent methods are lacking when scrolling. They recency lists. This establishes an empirical foundation for conclude that scrolling is “irritatingly slow and distracting” the design of an enhanced scrollbar containing scrollbar and that people need “quicker, more effortless navigation” marks that help people return to previously visited [25], p.341. document regions. Two controlled experiments show that scrollbar marks decrease revisitation time, and that a large One way to improve support for revisitation is by number of marks can be used effectively. We then design augmenting the scrollbar region with scrollbar marks. Such an enhanced Footprints scrollbar that supports revisitation marks are not a new idea. Attribute-mapped scrollbars , with several features, including scrollbar marks and mark patented in 1990 [31], used coloured marks in the scrollbar thumbnails. Two further experiments show that the to draw attention to salient properties; scrollbars are well- Footprints scrollbar was frequently used and strongly suited to showing this information, as they provide an preferred over traditional scrollbars. overview of the entire document. Hill et al. [18] used a similar approach to denote the read wear that occurs with Author Keywords. use – the marks portray how often sections of the document Document revisitation, read wear, scrolling. have been read. However, their focus was on showing history of use, not on supporting revisitation. ACM Classification Keywords. Read-wear marks on the scrollbar offer a lightweight H.5. Information interfaces and presentation: User method for improving document revisitation compared to interfaces ( Interaction styles , screen design ). traditional scrolling: a mark shows a person where they have been, and provides a navigation cue to help them INTRODUCTION quickly return to that spot. However, the idea has not Scrollbars are a familiar widget common to graphical user caught on, and we are unaware of any system currently interfaces, and have become a standard idiom for view using it (although scrollbar marks are becoming common in navigation within documents. They are compact and IDEs for marking code errors or comments). conceptually simple, yet powerful, providing useful information about the viewport’s location and extent in a We believe the poor adoption of read-wear scrollbars is due larger information space. In particular, the scroll thumb’s to a lack of knowledge about how revisitation occurs in the spatial cue can help revisitation – returning to previously real world, how best to design a read-wear scrollbar, and visited document regions. For example, a user may know the potential benefits and harms of using it in realistic that “moving the thumb roughly four-fifths of the way systems. Consequently, we conducted several investigations down will bring me to the Results section”. to address these knowledge gaps. However, rapid and effective revisitation depends on people 1. How do people revisit document locations, and are current tools well used? We analysed logs from a 120- Cite as : Alexander, J., Cockburn, A., Fitchett, S., Gutwin, C., and day longitudinal study of document navigation in Greenberg, S. Revisiting Read Wear: Analysis, Design, and Evaluation of Microsoft Word and Adobe Reader, and draw three main a Footprints Scrollbar. Department of Computer Science and Software conclusions: that region revisitation is frequent, that Engineering. Tech Report #02/08. 2008. current revisitation tools other than the normal scrollbar 1 are used very little, and that short recency lists can immediate suboptimal strategies are favoured over more contain most locations that people will revisit. efficient long-term ones) suggests that people will often fail 2. Can scrollbar marks improve revisitation, and how many to place bookmarks, even when they can foresee the long marks should be used? We conducted two experiments to term advantage [1]. This is why our research interest lies test the performance of adding marks into the scrollbar. primarily in automatic revisitation support. One study demonstrates that marks can decrease Automatic revisitation tools have been developed to support revisitation time; the other shows that people can revisitation both between and within documents. Familiar successfully use a large number of marks. interface controls such as history lists, ‘Back/Forward’ 3. How can a realistic interface support revisitation? We buttons, and ‘Recent Document’ menus facilitate navigation designed our Footprints Scrollbar (Figure 5) to maximize between documents. These automatic revisitation tools support for revisitation, based on principles derived from minimally intrude on users’ activities: they silently record the log analysis and the two studies. actions, populate a data structure or visualisation, and 4. Is this support used effectively and is it preferred? We provide support when called on. Their primary evaluated the Footprints Scrollbar in two experiments: a disadvantages are that people may not understand the controlled lab study and a realistic usage study. The algorithm for recording or presenting events, and the event Footprints Scrollbar was frequently and successfully set may overwhelm or fail to match the interests of the user. used, improved users’ revisitation time, and was strongly For example, people often misunderstand the behaviour of preferred to traditional scrollbars. the web ‘Back’ button, causing frustration when items Overall, our investigations show that revisitation is worth cannot be revisited [12], and we have observed similar supporting, and that read wear – long known but little problems with missing items in ‘Recent Documents’ studied – is a valuable and usable technique for improving menus, and with user misunderstanding of the temporal revisitation. To our knowledge these studies are the first to order of Alt-Tab window switching. analyse real world revisitation in documents and to use the There are also several widely-deployed examples of results in the design, implementation, and evaluation of a automatic revisitation tools for navigating within read-wear scrollbar. documents. For example, the web browser’s ‘Back’ button works as normal when navigating through internal page RELATED WORK links, and Adobe Reader’s ‘Previous/Next View’ feature Revisitation and its support steps through a linear history of scroll positions and zoom Zipf’s Law [33], the Pareto Principle [22] and the “80-20 levels. Visual Studio also has a ‘previous/next’ list of lines Rule” all demonstrate that many facets of human behaviour that the I-beam cursor has visited. These history lists leave are highly repetitive: although we have extensive no visible trace in the scrollbar, however, so people cannot vocabularies, wardrobes, or choices at our disposal, most of visually scan potential target regions without displaying the time we reuse a small set of favoured options. additional windows or menus. Researchers have also demonstrated that many aspects of computer use are also highly repetitive, such as command Hill et al ’s [18] original Read Wear system showed a use [15, 16], menu selections [11, 14], and web page visits histogram overview of the reading history of an entire [2, 12, 29]. document within the scrollbar. Each horizontal line of pixels in the scrollbar encoded information such as the These observations have stimulated research into interface number of edits, or length of time reading. Similar scrollbar techniques for supporting reuse and revisitation. Some marks are used by several code editors, but the marks are strategies require manual intervention while others used to highlight semantic information such as compilation automatically observe actions and update the interface. errors rather than to support revisitation. Manual revisitation tools require an explicit user action to The concept of document read wear inspired several mark information as interesting. For example, bookmark researchers to examine a variety of techniques for recording tools in web browsers and Microsoft Word let people and visualizing activity beyond the scrollbar. These include explicitly create iconic labels as shortcuts for returning to Wexelblat and Maes’ [30] ‘Footprints’ system, which particular pages or positions in a document. The Bookmark provided maps, trails, annotations and signposts for Scrollbar [24]
Recommended publications
  • Bforartists UI Redesign Design Document Part 2 - Theming
    Bforartists UI redesign Design document part 2 - Theming Content Preface...........................................................................................................................6 The editor and window types......................................................................................7 Python console.............................................................................................................8 Layout:................................................................................................................................................................8 The Console Window.........................................................................................................................................8 Menu bar with a menu........................................................................................................................................8 Dropdown box with icon....................................................................................................................................9 RMB menu for menu bar....................................................................................................................................9 Toolbar................................................................................................................................................................9 Button Textform..................................................................................................................................................9
    [Show full text]
  • Bluebeam Revu Kansas Department of Transportation 700 SW Harrison Topeka, KS 66612
    Kansas Department of Transportation-Bureau of Local Projects http://www.ksdot.org/burLocalProj/BLPDocuments/KDOTBLPEplans.pdf July 1, 2014 i Bluebeam Revu Kansas Department of Transportation 700 SW Harrison Topeka, KS 66612 For additional KDOT training sources, please visit KDOT’s CADD Support channel located at www.youtube.com/kdotcaddsupport Helpful web links: https://studio.bluebeam.com Credit for a majority of this manual goes to: Mike Dillner, KDOT CADD Support Scott Marquis, KDOT CADD Support Jonathan Mushock, KDOT Traffic Safety and Technology Misty Rodriguez, KDOT KCTC Trainer Megan Murray, KDOT KCTC Trainer Ingrid Vandevort, KDOT KCTC Training Coordinator Chapters 1-4 and Appendix A were written by these people and they deserve the credit for the quality of the document they have produced. Revision date: July 2014 ii Bluebeam Revu Kansas Department of Transportation Introduction to Bluebeam Revu This is a guide for how to use Bluebeam Revu for your PDF markup and collaboration needs. Bluebeam Revu provides powerful and easy to use features for marking up Architecture, Engineering, and Construction (AEC) plan PDF documents. The Studio Session feature allows users from any location to participate in a collaborative review. Bluebeam makes use of Amazon Web Services (AWS), commonly referred to as the Amazon Cloud. This service will host the documents for the Studio Session. There are two roles within a Bluebeam Studio Session. That of an initiator, and that of a participant. If you are going to initiate a Studio Session you need to have any tier of Bluebeam Revu installed on your pc. However, to be a participant all that is required is Bluebeam Vu (a free PDF reader), though Bluebeam Revu can be used as well.
    [Show full text]
  • Feature-Rich Components & Tools That Boost the Productivity for You & Your
    Feature-rich components & tools that boost the productivity for you & your development team! Overview tmssoftware.com products Contents VCL Components for Windows application development ........................................................................................... 5 TMS Component Pack............................................................................................................................................... 6 Grid Components .................................................................................................................................................. 6 HTML ENABLED COMPONENTS .......................................................................................................................... 10 Edit controls ........................................................................................................................................................ 13 Planner components ........................................................................................................................................... 17 Outlook / inspector bar components ................................................................................................................. 19 Web connectivity components ........................................................................................................................... 20 Memo components ............................................................................................................................................ 22 System
    [Show full text]
  • Horizontally Scrollable Listboxes for Windows 3.X, Using C++
    Horizontally Scrollable ListBoxes for Windows 3.x, using C++ Ted Faison Ted is a writer and developer, specializing in Windows and C++. He has authored two books on C++, and has been programming in C++ since 1988. He is president of Faison Computing, a firm which develops C++ class libraries for DOS and Windows. He can be reached at [email protected] List boxes are among the most commonly used child controls in Windows applications. List boxes are typically used to show lists of files, fonts, or other variable-length lists of textual information. To add a list box to a dialog box, you generally edit a resource file, using programs such as Microsoft's Dialog Editor or Borland's Resource Workshop. Windows handles most of the list box details transparently. For example, if you add strings to a list box, Windows will automatically put a scroll bar on the control when the list box contains more strings than can be displayed in the client area of the list box. Windows handles scroll bar events - such as moving the thumb or clicking the up/down arrows - without any need for user code. Displaying a list of files in a list box is a somewhat easy task, because filenames have a predefined maximum number of characters. When you create the list box resource, you will generally make the control wide enough to display the longest filename. But what if you use a list box to display strings of varying and unknown length, such as the names of people or the titles of your CD collection ? You could obviously make the list box wide enough to accommodate the widest string you expect, but that would not only look pretty bad, but also waste a great deal of space on the screen.
    [Show full text]
  • Bluebeam Revu PDF Markup & Collaboration
    Bluebeam Revu PDF Markup & Collaboration Bluebeam Revu Idaho Transportation Department 3311 W. State Street P.O. Box 7129 Boise, ID 83713 If you need assistance with Bluebeam, please contact the OTS Support Team: Bluebeam Contacts D1 Benjamin Daley (208) 772-8033 [email protected] D2 Janet Zarate (208) 799-4243 [email protected] D3 Marc Danley (208) 334-8389 [email protected] D4 James Bennett (208) 886-7818 [email protected] D5 Kelli Baker (208) 239-3363 [email protected] D6 Brad Richards (208) 745-5635 [email protected] Bridge Rick Jensen (208) 334-8589 [email protected] HQ Beau Hansen (208) 334-8494 [email protected] HQ Jeremy Hunting (208) 332-7167 [email protected] For More Information: ITD SharePoint CADD/ProjectWise CADD/ProjectWise/Bluebeam Helpful links: BlueBeam Training Materials BlueBeam Support BlueBeam Revu Basics BlueBeam Revu 2016 Tips and Tricks Collaborative Design Review in Bluebeam Studio Revision date: October 2017 ii Bluebeam Revu Idaho Transportation Department Introduction to Bluebeam Revu This course will teach you how to use Bluebeam Revu for your PDF markup and collaboration needs. Bluebeam Revu provides powerful and easy to use features for marking up Architecture, Engineering, and Construction (AEC) plan PDF documents. The Studio Session feature allows users from any location to participate in a collaborative review. Bluebeam makes use of Amazon Web Services (AWS), commonly referred to as the Amazon Cloud. This service will host the documents for the Studio Session. There are two roles within a Bluebeam Studio Session: initiator and participant.
    [Show full text]
  • Hyperion Interactive Reporting
    HYPERION® INTERACTIVE REPORTING – SYSTEM 9 RELEASE 9.3.1 OBJECT MODEL AND DASHBOARD DEVELOPMENT SERVICES DEVELOPER’S GUIDE VOLUME I: DASHBOARD DESIGN GUIDE Interactive Reporting Object Model and Dashboard Development Services Developer’s Guide, 9.3.1 Copyright © 1996, 2007, Oracle and/or its affiliates. All rights reserved. Authors: Dan Montagne The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to
    [Show full text]
  • UI Manager Properties
    APPENDIX A UI Manager Properties THROUGHOUT THIS BOOK YOU'LL FIND TABLES that list the property names and data types for all the UIResource elements of specific Swing components. Although these tables serve to list all the information about a specific component, I fig­ ured it would be handy to also group all the information about property names in one place. With that in mind, Table A-1 provides a complete list of properties used by the predefined look and feel classes-Motif, Macintosh, Metal, and Windows­ provided with the Swing 1.1.1 release. The table indicates with an "X" which of the four look and feel classes uses a particular property. To change the default setting for any one of these properties, you need to notify the UIManager by storing a new setting in the lookup table of the UIManager. For instance, to change the default text for the "Yes" button on a JOptionPane, 11 you'd replace the 0ptionPane. yesButtonText II property with the new setting 11 11 UIManager. put ( 0ptionPane. yesButtonTextll, Si II);. Then, any component cre­ ated after the setting change will get the new value: 11 5i 11 .1fyou want a displayed component to get the new setting, you must call its updateUI () method. When you change the current look and feel, any custom settings you install may be lost. If the class of the property value setting implements the UIResource interface (an empty marker interface such as Serializable), then the setting will be replaced by the default setting of the look and feel.
    [Show full text]
  • The Design, Use, and Performance of Edge-Scrolling Techniques Jonathan Aceituno, Sylvain Malacria, Philip Quinn, Nicolas Roussel, Andy Cockburn, Géry Casiez
    The design, use, and performance of edge-scrolling techniques Jonathan Aceituno, Sylvain Malacria, Philip Quinn, Nicolas Roussel, Andy Cockburn, Géry Casiez To cite this version: Jonathan Aceituno, Sylvain Malacria, Philip Quinn, Nicolas Roussel, Andy Cockburn, et al.. The design, use, and performance of edge-scrolling techniques. International Journal of Human-Computer Studies, Elsevier, 2017, 97, pp.58 - 76. 10.1016/j.ijhcs.2016.08.001. hal-01624625 HAL Id: hal-01624625 https://hal.archives-ouvertes.fr/hal-01624625 Submitted on 2 Nov 2017 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. The design, use, and performance of edge-scrolling techniques J. Aceitunoa,b,∗, S. Malacriaa,c, P. Quinnc, N. Roussela, A. Cockburnc, G. Casiezb aInria Lille - Nord Europe, 40 avenue Halley, 59650 Villeneuve d'Ascq, France bUniversit´eLille 1, Cit´eScientifique, 59650 Villeneuve d'Ascq, France cDepartment of Computer Science and Software Engineering, University of Canterbury, Private Bag 4800, Christchurch, New Zealand Abstract Edge-scrolling techniques automatically scroll the viewport when the user points near its edge, enabling users to reach out-of-view targets during activities such as selection or drag-and-drop. Despite the prevalence of edge-scrolling techniques in desktop interfaces, there is little public research on their behaviour, use or performance.
    [Show full text]
  • Workspace Desktop Edition
    Workspace Desktop Edition 8.5.124.08 9/27/2021 8.5.124.08 8.5.124.08 Workspace Desktop Edition Release Notes Release Date Release Type Restrictions AIX Linux Solaris Windows 02/28/18 Update X Contents • 1 8.5.124.08 • 1.1 Helpful Links • 1.2 What's New • 1.3 Resolved Issues • 1.4 Upgrade Notes Workspace Desktop Edition 2 8.5.124.08 What's New Helpful Links This release contains the following new features and enhancements: Releases Info • The rich text email editor Font menu now displays the full list of fonts • List of 8.5.x Releases available on the agent workstation. Previously, only one font per font family was displayed. • 8.5.x Known Issues • Screen Reader applications can now read the names of colors inside the email Rich Text Editor color Picker control. • Agents can now press the Enter key to insert a selected standard Product Documentation response into an email, chat, or other text-based interaction. Workspace Desktop Edition • It is now possible to sort the content of an 'auto-update' workbin based on a column containing integer values. For that purpose, the key-value pair 'interaction-workspace/display-type'='int' must be specified in the annex of Genesys Products the Business Attribute Value corresponding to that column in the Business Attribute "Interaction Custom Properties". Previously those columns were List of Release Notes sorted as strings. • On an Alcatel 4400 / OXE switch, a Supervisor can now fully log out of the voice channel when exiting Workspace if the value of the logout.voice.use-login-queue-on-logout option is set to true.
    [Show full text]
  • A Visual Metaphor for Navigation of Annotation in Digital Documents
    Touching Annotations: A Visual Metaphor for Navigation of Annotation in Digital Documents C.P.Bowers∗, C.Creed, B.R.Cowan, R. Beale Human-Computer Interaction Centre, School of Computer Science, University of Birmingham, Birmingham, B15 2TT, UK Abstract Direct touch manipulation interactions with technology are now common- place and significant interest is building around their use in the culture and heritage domain. Such interactions can give people the opportunity to ex- plore materials and artifacts in ways that would otherwise be unavailable. These are often heavily annotated and can be linked to a large array of re- lated digital content, thus enriching the experience for the user. Research has addressed issues of how to present digital documents and their related anno- tations but at present it is unclear what the optimal interaction approach to navigating these annotations in a touch display context might be. In this paper we investigate the role of two alternative approaches to support the navigation of annotations in digitised documents in the context of a touch interface. Through a control study we demonstrate that, whilst the navigation paradigm displays a significant interaction with the type of annotations task performed, there is no discernible advantage of using a natural visual metaphor for annotation in this context. This suggests that design of digital document annotation navigation tools should account for the context and navigation tasks being considered. Keywords: Document navigation, touch interaction, affordance, interaction techniques, user study ∗Corresponding author Email addresses: [email protected] (C.P.Bowers), [email protected] (C.Creed), [email protected] (B.R.Cowan), [email protected] (R.
    [Show full text]
  • Hiring Manager Manual
    VTHR Recruitment Manual for Hiring Managers Created on May 8, 2013 Training Guide Hiring Managers Table of Contents Hiring Manager Manual .................................................................................................. 1 Recruitment_Create Job Opening pt.1 - Hiring Manager ..................................................... 1 Recruitment_Create Job Opening pt.2 - Appointing Authority .......................................... 18 Recruitment_Review Applicant Information ........................................................................ 21 Recruitment_Run Detailed Application Report .................................................................... 32 Recruitment_Schedule An Interview ..................................................................................... 42 Recruitment_Update Interview Status ................................................................................... 50 Recruitment_Forward Applicant ........................................................................................... 55 Recruitment_Applicant Accepts Job Offer ........................................................................... 58 Recruitment_Reject Applicant & Send Correspondence ..................................................... 62 Page ii Training Guide Hiring Managers Hiring Manager Manual Recruitment_Create Job Opening pt.1 - Hiring Manager Procedure Step Action 1. Click the Main Menu button. 2. Click the Recruiting menu. 3. Click the Create New Job Opening menu. Page 1 Training Guide Hiring Managers
    [Show full text]
  • PLUGGABLE FACTORY an Object-Creational Compound Pattern  1999 by John Vlissides
    PLUGGABLE FACTORY An Object-Creational Compound Pattern 1999 by John Vlissides. All rights reserved Intent Specify and change product types dynamically without replacing the factory instance. Motivation Suppose you’re using ABSTRACT FACTORY to provide multiple look-and-feel standards as described in that pattern’s Motivation section. Also suppose that applications in your environment should be able to handle changes in screen resolution on-the-fly, as might be required when the user docks or undocks a notebook computer. Undocked, the notebook’s display resolution is, say, 800 by 600 pixels, while the monitor attached to the docking station is set for 1280 by 1024 pixels (see Figure 1). 800 by 600 display 1280 by 1024 display Figure 1 To remain legible, text must be proportionately larger on the monitor than on the notebook. User interface “widgets” that incorporate text, such as buttons and menus, should adopt a larger font, but their look and feel is otherwise unchanged. Similarly, widgets that incorporate a bitmap should use a larger bitmap at higher resolutions. (Compare the icons in the lower right of each display in Figure 1.) Since widget instances are created using a factory, you could effect these changes in appearance in two steps: Replace the factory instance with one that produces widgets with bigger fonts and bitmaps, and then reconstruct the user interface from scratch. But that’s unsatisfactory for two reasons. First, objects that maintain references to the old factory must be updated to refer to the new one. That may be difficult to do, especially if the system was not designed with dynamic updating in mind.
    [Show full text]