#4365 NORM Never A: Write activity leaves crud in journal

[Zarro Boogs per Child]

#4365: Write activity leaves crud in journal
-------------------------------+--------------------------------------------
  Reporter:  AlbertCahalan     |       Owner:  tomeu         
      Type:  defect            |      Status:  new           
  Priority:  normal            |   Milestone:  Never Assigned
 Component:  journal-activity  |     Version:                
Resolution:                    |    Keywords:                
  Verified:  0                 |  
-------------------------------+--------------------------------------------
Changes (by tomeu):

  * component:  interface-design => journal-activity


Comment:

 Activities that doesn't use the activity API in the sugar lib are already
 managing their own entries and can delete their own entries whenever they
 want (and also create them when they want).

 Other (most) activities are not directly managing their journal entries,
 so it would be dangerous if somehow they deleted their entries.

 In this case I think we could add a is_dirty() method to the Activity API
 that would return True by default and that activities would override in
 order to give inside to Sugar about the state of it's state. is_dirty
 would return True if since the last save, there have been changes worth
 saving to the journal.

 We also have the possibility of making the default implementation of
 is_dirty smarter and storing after every save a md5 checksum of the
 contents so we can check the next time if the actual data has been
 changed.

 For avoiding the creation of empty entries, is_dirty should return False
 when the activity has just been opened.

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