#5271 NORM Never A: Sugar should track window property changes

[Zarro Boogs per Child]

#5271: Sugar should track window property changes
---------------------+------------------------------------------------------
  Reporter:  bert    |       Owner:  marco         
      Type:  defect  |      Status:  new           
  Priority:  normal  |   Milestone:  Never Assigned
 Component:  sugar   |     Version:                
Resolution:          |    Keywords:  sugarization  
  Verified:  0       |  
---------------------+------------------------------------------------------

Comment(by AlbertCahalan):

 Tracking property changes to implement the GUI simply can't be reliable.
 You have a race condition, and maybe even a (mild?) security problem.

 The UI needs a mild redesign anyway. There are problems (bugs in trac too)
 with killing activities that don't start, timeouts (which will always be
 both too long and too short), and even just chewing up CPU time with the
 throbbing icon.

 Starting the icon throb early is no good; there are alternate animations
 that could work. (example: icon flies up behind the donut, then comes
 through the hole if it shows up on the X server) For local connections on
 DISPLAY=:0.0, X can get lots of info about the client. It should do so, if
 it doesn't already. It should provide this info to sugar, if it doesn't
 already. That's enough for sugar to identify the client without needing
 racy cooperation from the client. For remote connections, things are
 fairly raw... but you can still ask for an icon (scale it as needed) and
 name.

-- 
Ticket URL: <http://dev.laptop.org/ticket/5271#comment:1>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system