#8765 NORM Opportu: Clock activity hogs CPU.

[Zarro Boogs per Child]

#8765: Clock activity hogs CPU.
------------------------------+---------------------------------------------
   Reporter:  thomaswamm      |       Owner:  pierre       
       Type:  enhancement     |      Status:  new          
   Priority:  normal          |   Milestone:  Opportunity  
  Component:  clock-activity  |     Version:  not specified
 Resolution:                  |    Keywords:  clock        
Next_action:  diagnose        |    Verified:  0            
  Blockedby:                  |    Blocking:               
------------------------------+---------------------------------------------
Changes (by bemasc):

 * cc: cscott (added)


Comment:

 Sorry to be so negative, Pierre.  My real complaint here is about the
 disorganization and confusion that leads to these duplicate activities.

 If you're interested to see how to make an efficient clock activity, the
 source code is now being maintained by Scott at

 http://dev.laptop.org/git?p=users/cscott/clock-activity-
 tmp;a=blob;f=pippy_app.py;hb=HEAD

 You can see that the SVG is only rendered once, on startup, and from then
 on the image is held in a server-side pixmap, with the hands drawn by X
 drawing calls.  Also, the clock only renders when the activity is visible.

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