[Trac #1108] network view should give topology, freshness, and strength info

Zarro Boogs per Child bugtracker at laptop.org
Tue Mar 20 12:14:48 EDT 2007


#1108: network view should give topology, freshness, and strength info
------------------------------+---------------------------------------------
 Reporter:  AlbertCahalan     |        Owner:  Eben    
     Type:  enhancement       |       Status:  assigned
 Priority:  high              |    Milestone:  BTest-3 
Component:  interface-design  |   Resolution:          
 Keywords:                    |  
------------------------------+---------------------------------------------
Comment (by AlbertCahalan):

 Replying to [comment:3 Eben]:
 > Replying to [ticket:1108 AlbertCahalan]:

 > > As the info about a device or route gets stale, it should fade away.
 >
 > We do have the idea of present vs. absent XOs and devices.  While fading
 the icons isn't really feasible, we might have some more discrete ways of
 indicating this.  Clearly when a signal goes away, the XO should disappear
 from the mesh.  Perhaps we should also pick a threshold below which an XO
 is rendered as absent (white stroke, no fill), so that XOs first
 transition to an outline, but remain present (filling back in with color
 if the signal gets stronger), and only actually disappear once the signal
 is gone.

 You could blur the XO image, pixelate the XO image, punch holes in the XO
 image, etc.

 The XO should NOT disappear immediately when the signal is gone. The
 signal might be temporarily blocked by a vehicle. It's too disorienting to
 have the XOs rapidly appearing and disappearing. Users need to be able to
 interact with an XO that has an unreliable connection, while still being
 notified that the connection is unreliable.

 An XO should begin fading out at the first hint of signal loss, but should
 not disappear until there is little hope for recovery. Maybe give it a
 minute to fully die. Hey, they could morph into skull-and-crossbones
 icons. :-)

-- 
Ticket URL: <http://dev.laptop.org/ticket/1108#comment:4>
One Laptop Per Child <http://laptop.org/>



More information about the Bugs mailing list