Title: halo
1halo
- patrick baudisch, microsoft research, LDUX
- ruth rosenholtz, parc, ASD
- april 10th, CHI 2003
while at xerox parc, now parc inc.
2the problem
3halo ltdemogt
4contents
- 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)
5related work
- driving directionsvs. route planning aids
- overview-plus-detail
- focus-plus-context
- pointing into off-screen space
6 7cinematography
- entry and exit points
- point of view?arrow-based techniques
- partially out of the frame? halo
-
- rings are familiar, graceful degradation
8streetlamps
- 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
9reserve space for content
10arc length distance
11handling many objects
- find best (restaurant) relevance cut-off
- see all (dangers) merge arcs
12app designers can use
- color
- texture
- arc thickness
13 14interfaces
- 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
15pre-study to define tasks
- 8 participants (6 GPS users, 2 PDA users)
- informal interviews 10-40 minutes
- ? 4 tasks to be used in study
161. locate task
? had tosimulate on PC
click at expected location of off-screen targets
172. closest task
click arrow/arc or off-screen location closest to
car
183. traverse task
click all five targets so as to form shortest path
194. avoid task
click on hospital farthest away from traffic jams
20procedure
- 12 participants
- within subject design, counterbalanced
- four training maps per interface/task,then eight
timed maps - questionnaire
21task completion time
Task Arrow interface Halo interface
Locate 20.1 (7.3) 16.8 (6.7)
Closest 9.9 (10.1) 6.6 (5.3)
Traverse 20.6 (14.1) 16.8 (8.7)
Avoid 9.2 (4.7) 7.7 (5.8)
22error rate
Task Arrow interface Halo interface
Locate 23.5 pixels (21.6) 28.4 pixels (33.8)
Closest 22 (42) 21 (41)
Traverse 97.4 pixels (94.7) 81.0 pixels (96.7)
Avoid 15 (35) 14 (34)
23subjective preference
24conclusions
- 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
25Thanks!
- 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 27Extra
28(No Transcript)