1 / 28

halo

halo. patrick baudisch , microsoft research , LDUX * & ruth rosenholtz, parc, ASD april 10 th , CHI 2003. *while at xerox parc, now parc inc. +. the problem. halo <demo>. contents. halo is not a focus plus context technique (related work)

louise
Download Presentation

halo

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. halo patrick baudisch, microsoft research, LDUX* & ruth rosenholtz, parc, ASD april 10th, CHI 2003 *while at xerox parc, now parc inc.

  2. + the problem

  3. halo <demo>

  4. contents • halo is not a focus plus context technique(related work) • halo is a lamp shining onto the street(designing halo) • halo is 16-33% faster than arrow-based visualization techniques (user study) • build interactive halo applications! (conclusions, lessons learned)

  5. related work • driving directionsvs. route planning aids • overview-plus-detail • focus-plus-context • pointing into off-screen space

  6. halo design

  7. cinematography • entry and exit points • point of viewarrow-based techniques • partially out of the frame halo rings are familiar, graceful degradation

  8. streetlamps • aura visible from distance • aura is round • overlapping auras aggregate • fading of aura indicates distance what we changed • smooth transition  sharp edge • disks  rings • dark background  light background

  9. intrusion border handle space for arcs… and for corner arcs reserve space for content

  10. arc length = distance

  11. handling many objects • find best (restaurant): relevance cut-off • see all (dangers): merge arcs

  12. app designers can use • color • texture • arc thickness

  13. user study

  14. interfaces • arc/arrow fading off • scale 110-300m/cm • map as backdrop • readability ok • same selectable size • hypothesis: halo faster legend halo ring distance from display border

  15. pre-study to define tasks • 8 participants (6 GPS users, 2 PDA users) • informal interviews 10-40 minutes •  4 tasks to be used in study

  16. 1. locate task  had tosimulate on PC click at expected location of off-screen targets

  17. 2. closest task click arrow/arc or off-screen location closest to car

  18. 3. traverse task click all five targets so as to form shortest path

  19. 4. avoid task click on hospital farthest away from traffic jams

  20. procedure • 12 participants • within subject design, counterbalanced • four training maps per interface/task,then eight timed maps • questionnaire

  21. 16% 33% task completion time

  22. participants underestimated distances by 26% • participants saw ovals (gestalt laws?) • we can compensate for that: width += 35% error rate

  23. subjective preference

  24. conclusions • halo 16%-33% faster than arrows • no split attention • distortion-free space • scale independent • no need to annotate distance • perceive all rings at once [treisman & gormican] • limitation: max number or rings • future work: applications where peripheral objects move and change

  25. Thanks! • try halo: http://www.patrickbaudisch.com/projects/halo • polle zellweger, jock mackinlay,lance good, and mark stefik( “citylights” short paper talk) • scott minneman and allison woodruff

  26. end

  27. Extra

  28. (a) locate (b) closest (c) traverse (d) avoid

More Related