#2030 NORM Trial-3: Refresh approximate memory footprint representation

[Zarro Boogs per Child]

#2030: Refresh approximate memory footprint representation
---------------------+------------------------------------------------------
  Reporter:  Eben    |       Owner:  marco  
      Type:  defect  |      Status:  closed 
  Priority:  normal  |   Milestone:  Trial-3
 Component:  sugar   |     Version:         
Resolution:  fixed   |    Keywords:  review+
  Verified:  0       |  
---------------------+------------------------------------------------------
Comment (by Eben):

 Well, that does of course depend a lot on the activities themselves, and
 we're not always in control of those.  I just wanted to provide an extreme
 example to prove the point.  Chances are some activities might grow a lot
 while launching.  The web browser might grow a lot if I click on a link to
 a huge page.  We can't really predict the cases. If there isn't a high
 performance hit, you could do it by the minute, or every 10 seconds, or
 more.

 You could also add a threshold constant so that you only actually do a
 redraw of the ring when a wedge has changed sufficiently in size to be
 noticeable.  I'm assuming that the check is relatively low cost compared
 to the constant re-rendering.

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