#5760 HIGH Update.: Objects accumulate on the clipboard, impacting system performance.

[Zarro Boogs per Child]

#5760: Objects accumulate on the clipboard, impacting system performance.
------------------------+---------------------------------------------------
  Reporter:  legutierr  |       Owner:  tomeu    
      Type:  defect     |      Status:  new      
  Priority:  high       |   Milestone:  Update.1 
 Component:  sugar      |     Version:  Build 650
Resolution:             |    Keywords:  review-  
  Verified:  0          |    Blocking:           
 Blockedby:             |  
------------------------+---------------------------------------------------

Comment(by tomeu):

 Replying to [comment:7 marco]:
 > Implementation wise, I think the service should have a method to set
 MAX_SIZE (with a reasonable default), which the shell view would call at
 startup to set a limit based on the grid size.

 I don't yet see that this limit should be implemented in the service, as
 the limit we want to implement for update.1 is very tied to the UI.

 One reason is that only the UI can now the number of elements we want to
 show. As you said, the UI can pass that info to the service, but I find
 that as adding complexity where it is not needed.

 One bigger reason (but related) is that, although we currently lack a way
 of reordering items in the clipboard,  it has been specified since the
 beginning (and see #5755), so when we implement it, we should move the
 limit back to the UI or move the ordering of items in the frame to the
 service (bad design, in my opinion).

 In summary, I think we should have a limit based on UI considerations in
 the shell, and another in the service based on the maximum amount of
 memory and temp nand space that we want to dedicate to clippings.

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