DOCSLIB.ORG

Scrollbar Paper

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Scrollbar Paper Brewster, S.A. and Wright, P.C. and Edwards, A.D.N. (1994) The design and evaluation of an auditory-enhanced scrollbar. In, Adelson, B. and Dumais, S.T. and Olson, J.D., Eds. Conference on Human Factors in Computing Systems, 24-28 April 1994, pages pp. 173-179, Boston, Massachusetts, USA. http://eprints.gla.ac.uk/3255/ Glasgow ePrints Service http://eprints.gla.ac.uk The Design and Evaluation of an Auditory- Enhanced ScrollBar Stephen A. Brewster, Peter C. Wright and Alistair D. N. Edwards Department of Computer Science, University of York, Heslington, York, Y01 5DD, UK. Tel.: 0904 432765 [email protected] ABSTRACT At the present time almost all information presented goes A structured method is described for the analysis of through the visual channel. This means information can be interactions to identify situations where hidden information missed because of visual overload or because the user was may exist and where non-speech sound might be used to not looking in the right place at the right time. An interface overcome the associated problems. Interactions are that integrates information output to both senses can considered in terms of events, status and modes to find any capitalise on the interdependence between them and present hidden information. This is then categorised in terms of the information in the most efficient way possible. feedback needed to present it. An auditory-enhanced scrollbar, based on the method described, was then The work reported here is part of a research project looking experimentally tested. Timing and error rates were used at the best ways to integrate auditory and graphical along with subjective measures of workload. Results from information at the interface. The sounds used in this paper the experiment show a significant reduction in time to are based around structured audio messages called Earcons complete one task, a decrease in the mental effort required first put forward by Blattner, Sumikawa & Greenberg [3] and an overall preference for the auditory-enhanced and experimentally tested by Brewster, Wright & Edwards scrollbar. [4]. Earcons are abstract, synthetic tones that can be used in structured combinations to create sound messages to KEYWORDS represent parts of an interface. Auditory interfaces, multi-modal interfaces, earcons, sonification, auditory-enhanced widgets One question that might be asked is: Why use sound to present the extra information? A graphical method could be INTRODUCTION used instead. The drawback with this is that it puts an even It has been shown that non-speech sounds can be designed greater load on the visual channel. Furthermore, sound has to communicate complex information at the human- certain advantages. For example, it can be heard from 360° computer interface [3, 4, 8]. Unless these sounds supply all around, it does not disrupt the user’s visual attention and information that users need to know they will serve no real it can alert the user to changes very effectively. It is for purpose; they will become an annoying intrusion that users these reasons that we suggest that sound be used to enhance will want to turn off. Therefore an important question that the user interface. must be answered is: Where should non-speech sound be used to best effect in the graphical human-computer How should the information be apportioned to each of the interface? senses? Sounds can do more than simply indicate errors or supply redundant feedback for what is already available on The combination of graphical and auditory information at the graphical display. They should be used to present the interface is a natural step. In everyday life both senses information that is not currently displayed (give more combine to give complementary information about the information) or present existing information in a more world; they are interdependent. The visual system gives us effective way so that users can deal with it more efficiently. detailed data about a small area of focus whereas the Alty [1] has begun considering this problem in process auditory system provides general data from all around, control systems. Sound is often used in an ad hoc way by alerting us to things we cannot see. The combination of individual designers. In many cases no attempt is made to these two senses gives much of the information we need evaluate the impact of sound. Gaver [8] used a more about our environment. These advantages can be brought to principled approach in the SonicFinder that uses sounds in the human-computer interface. Whilst directing our visual ways suggested by the natural environment. For example, attention to one specific task, such as editing a document, selecting an item gave a tapping sound or dragging gave a we can still monitor the state of other tasks on our machine. scraping sound. However, in an interface there are many situations where there are no natural equivalents in the everyday world. The SonicFinder used sound redundantly with graphics. This proved to be very effective but we suggest that sound can do more. A method is needed to find situations in the interface where sound might be useful but currently there is no such method. It should provide for a clear, consistent and effective use of non-speech audio Modes: A mode is a state within a system in which a certain across the interface. Designers will then have a technique interpretation is placed on information (for example in one for identifying where sound would be useful and for using it mode characters typed into an editor may appear on the in a more structured way rather than it just being an ad hoc screen, in another they may be interpreted as commands). It decision. is often the case that the details of this interpretation are hidden from the user and mode errors result [13]. This paper describes a structured, informal method of analysing the interface to find hidden information that can Dix et al. [5] suggests two principles that, if satisfied, could cause user errors. It then describes an experiment to test an reduce the number of errors due to hidden information: auditory-enhanced scrollbar designed, using the analysis Observability and predictability. The user should be able to technique, to overcome the problems brought to light. The predict what the effects of their commands will be by aim of the experiment was to justify the model and see if observing the current status of the system. If information auditory-enhanced widgets were effective. about the system state is hidden, and not observable, then errors will result. The above points show that hidden Workload Assessment information is a problem and we suggests using sound to Wright & Monk [14] have argued that quantitative measures overcome it. A method is needed to find out where such of usability such as error rates and performance times do not hidden information exists. provide a complete picture of the usability problems of an interface. They argue that users may perform tasks well and Event, Status and Mode Analysis quickly and yet find the system frustrating to use and that it Analysing interactions with event and status information requires more effort to complete a task than they would was first put forward by Dix [6]. This has been extended to expect. This dissociation between behavioural measures and include explicit information about modes, one of the most subjective experience has also been addressed in studies of important areas of hidden information in the interface. A workload. Hart and Wickens [11] for example, define description of each of the types of information follows. workload “...as the effort invested by the human operator Event: A discrete point in time. It marks an important into task performance; workload arises from the interaction happening in the system. An event can be initiated by the between a particular and task and the performer”. Their user (mouse click) or system (mail arriving). There can be basic assumption is that cognitive resources are required for input events (mouse clicks) or output events (a beep a task and there is a finite amount of these. As a task indicating an error). becomes more difficult, the same level of performance can Status: This is information about the state of the system that be achieved but only by the investment of more resources. is perceivable by the user. If there is information about the We used a workload test as part of our usability evaluation state that is not in the displayed as status information then it of the auditory-enhanced scrollbar discussed in this paper. It will be hidden from the user. Status refers to something that provides a more rounded and sensitive view of usability always has a value such as an indicator. It is relatively static than just time and error analysis alone. and continues over time. The rendering is how the information about the state of the system is displayed. Thus WHERE TO USE SOUND AT THE INTERFACE status information can be rendered in different ways, for There are potentially many ways that sound could be used example graphically, through sound or a combination of in an interface This paper suggests using it to present both. information that is hidden from the user. This is a similar Mode: This maps the events onto operations on the system approach to that taken by Blattner, Papp & Glinert [2] when state. Different modes can make the same events have adding sound to maps. Here information is hidden because different effects. If the mode is not displayed then the user of visual clutter. Information may be hidden for a number of may not know the mapping. reasons: Information is not available: It may not be available on Problems occur when: the display due to hardware limitations such as lack of CPU • Events are not saliently signalled to the user, for example power or screen size.
Load more

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]
  • PC Literacy II
    Computer classes at The Library East Brunswick Public Library PC Literacy II Common Window Elements Most windows have common features, so once you become familiar with one program, you can use that knowledge in another program. Double-click the Internet Explorer icon on the desktop to start the program. Locate the following items on the computer screen. • Title bar: The top bar of a window displaying the title of the program and the document. • Menu bar: The bar containing names of menus, located below the title bar. You can use the menus on the menu bar to access many of the tools available in a program by clicking on a word in the menu bar. • Minimize button: The left button in the upper-right corner of a window used to minimize a program window. A minimized program remains open, but is visible only as a button on the taskbar. • Resize button: The middle button in the upper-right corner of a window used to resize a program window. If a program window is full-screen size it fills the entire screen and the Restore Down button is displayed. You can use the Restore Down button to reduce the size of a program window. If a program window is less than full-screen size, the Maximize button is displayed. You can use the Maximize button to enlarge a program window to full-screen size. • Close button: The right button in the upper-right corner of a window used to quit a program or close a document window – the X • Scroll bars: A vertical bar on the side of a window and a horizontal bar at the bottom of the window are used to move around in a document.
    [Show full text]
  • Spot-Tracking Lens: a Zoomable User Interface for Animated Bubble Charts
    Spot-Tracking Lens: A Zoomable User Interface for Animated Bubble Charts Yueqi Hu, Tom Polk, Jing Yang ∗ Ye Zhao y Shixia Liu z University of North Carolina at Charlotte Kent State University Tshinghua University Figure 1: A screenshot of the spot-tracking lens. The lens is following Belarus in the year 1995. Egypt, Syria, and Tunisia are automatically labeled since they move faster than Belarus. Ukraine and Russia are tracked. They are visible even when they go out of the spotlight. The color coding of countries is the same as in Gapminder[1], in which countries from the same geographic region share the same color. The world map on the top right corner provides a legend of the colors. ABSTRACT thus see more details. Zooming brings many benefits to visualiza- Zoomable user interfaces are widely used in static visualizations tion: it allows users to examine the context of an interesting object and have many benefits. However, they are not well supported in by zooming in the area where the object resides; labels overcrowded animated visualizations due to problems such as change blindness in the original view can be displayed without overlaps after zoom- and information overload. We propose the spot-tracking lens, a new ing in; it allows users to focus on a local area and thus reduce their zoomable user interface for animated bubble charts, to tackle these cognitive load. problems. It couples zooming with automatic panning and provides In spite of these benefits, zooming is not as well supported in an- a rich set of auxiliary techniques to enhance its effectiveness.
    [Show full text]
  • Organizing Windows Desktop/Workspace
    Organizing Windows Desktop/Workspace Instructions Below are the different places in Windows that you may want to customize. On your lab computer, go ahead and set up the environment in different ways to see how you’d like to customize your work computer. Start Menu and Taskbar ● Size: Click on the Start Icon (bottom left). As you move your mouse to the edges of the Start Menu window, your mouse icon will change to the resize icons . Click and drag the mouse to the desired Start Menu size. ● Open Start Menu, and “Pin” apps to the Start Menu/Taskbar by finding them in the list, right-clicking the app, and select “Pin to Start” or “More-> “Pin to Taskbar” OR click and drag the icon to the Tiles section. ● Drop “Tiles” on top of each other to create folders of apps. ● Right-click on Tiles (for example the Weather Tile), and you can resize the Tile (maybe for apps you use more often), and also Turn On live tiles to get updates automatically in the Tile (not for all Tiles) ● Right-click applications in the Taskbar to view “jump lists” for certain applications, which can show recently used documents, visited websites, or other application options. ● If you prefer using the keyboard for opening apps, you probably won’t need to customize the start menu. Simply hit the Windows Key and start typing the name of the application to open, then hit enter when it is highlighted. As the same searches happen, the most used apps will show up as the first selection.
    [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]
  • Using Microsoft Visual Studio to Create a Graphical User Interface ECE 480: Design Team 11
    Using Microsoft Visual Studio to Create a Graphical User Interface ECE 480: Design Team 11 Application Note Joshua Folks April 3, 2015 Abstract: Software Application programming involves the concept of human-computer interaction and in this area of the program, a graphical user interface is very important. Visual widgets such as checkboxes and buttons are used to manipulate information to simulate interactions with the program. A well-designed GUI gives a flexible structure where the interface is independent from, but directly connected to the application functionality. This quality is directly proportional to the user friendliness of the application. This note will briefly explain how to properly create a Graphical User Interface (GUI) while ensuring that the user friendliness and the functionality of the application are maintained at a high standard. 1 | P a g e Table of Contents Abstract…………..…………………………………………………………………………………………………………………………1 Introduction….……………………………………………………………………………………………………………………………3 Operation….………………………………………………….……………………………………………………………………………3 Operation….………………………………………………….……………………………………………………………………………3 Visual Studio Methods.…..…………………………….……………………………………………………………………………4 Interface Types………….…..…………………………….……………………………………………………………………………6 Understanding Variables..…………………………….……………………………………………………………………………7 Final Forms…………………....…………………………….……………………………………………………………………………7 Conclusion.…………………....…………………………….……………………………………………………………………………8 2 | P a g e Key Words: Interface, GUI, IDE Introduction: Establishing a connection between
    [Show full text]
  • Widget Toolkit – Getting Started
    APPLICATION NOTE Atmel AVR1614: Widget Toolkit – Getting Started Atmel Microcontrollers Prerequisites • Required knowledge • Basic knowledge of microcontrollers and the C programming language • Software prerequisites • Atmel® Studio 6 • Atmel Software Framework 3.3.0 or later • Hardware prerequisites • mXT143E Xplained evaluation board • Xplained series MCU evaluation board • Programmer/debugger: • Atmel AVR® JTAGICE 3 • Atmel AVR Dragon™ • Atmel AVR JTAGICE mkll • Atmel AVR ONE! • Estimated completion time • 2 hours Introduction The aim of this document is to introduce the Window system and Widget toolkit (WTK) which is distributed with the Atmel Software Framework. This application note is organized as a training which will go through: • The basics of setting up graphical widgets on a screen to make a graphical user interface (GUI) • How to get feedback when a user has interacted with a widget • How to draw custom graphical elements on the screen 8300B−AVR−07/2012 Table of Contents 1. Introduction to the Window system and widget toolkit ......................... 3 1.1 Overview ........................................................................................................... 3 1.2 The Window system .......................................................................................... 4 1.3 Event handling .................................................................................................. 5 1.3.2 The draw event ................................................................................... 6 1.4 The Widget
    [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]
  • Beyond the Desktop: a New Look at the Pad Metaphor for Information Organization
    Beyond the Desktop: A new look at the Pad metaphor for Information Organization By Isaac Fehr Abstract Digital User interface design is currently dominated by the windows metaphor. However, alternatives for this metaphor, as the core of large user interfaces have been proposed in the history of Human-computer interaction and thoroughly explored. One of these is the Pad metaphor, which has spawned many examples such as Pad++. While the the Pad metaphor, implemented as zoomable user interfaces, has shown some serious drawbacks as the basis for an operating system, and limited success outside of image-based environments, literature has pointed to an opportunity for innovation in other domains. In this study, we apply the the design and interactions of a ZUI to Wikipedia, a platform consisting mostly of lengthy, linear, hypertext-based documents. We utilize a human centered design approach, and create an alternative, ZUI-based interface for Wikipedia, and observe the use by real users using mixed methods. These methods include qualitative user research, as well as a novel paradigm used to measure a user’s comprehension of the structure of a document. We validate some assumptions about the strengths of ZUIs in a new domain, and look forward to future research questions and methods. Introduction and Background Windows-based user interfaces have dominated the market of multipurpose, screen-based computers since the introduction of the first windowed system in the Stanford oN-Line System (NLS)[3]. From Desktop computers to smartphones, most popular operating systems are based upon at least the window and icon aspects of the WIMP (Window, Icon, Menu, Pointer) paradigm.
    [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]