#1346 NORM Trial-2: Too many entries are created in the journal

[Zarro Boogs per Child]

#1346: Too many entries are created in the journal
---------------------+------------------------------------------------------
  Reporter:  tomeu   |       Owner:  Eben         
      Type:  defect  |      Status:  new          
  Priority:  normal  |   Milestone:  Trial-2      
 Component:  sugar   |     Version:               
Resolution:          |    Keywords:  write journal
  Verified:  0       |  
---------------------+------------------------------------------------------
Comment (by Eben):

 Four cases:

  1. Create a new object,  make no changes
  2. Resume an old object, make no changes
  3. Create a new object, make changes
  4. Resume an old object, make changes

 In case 1, it's clear that we ''don't'' want a new Journal entry.  It's
 easy to accidentally launch an activity, or launch it and then forget
 about it while doing something else.  It doesn't make sense to store an
 empty object in the Journal.  The actual order of operations is another
 question.  Do we make an entry immediately when an activity is opened, but
 remove it again silently if no changes are made to the object?  Or, do we
 wait for some mutation to happen in order to trigger the creation?

 In cases 3 and 4, we obviously need to store the updated versions as a new
 entry in the Journal.  The actual triggers for the save can be:  focus-
 out, quit, share (change in scope), activity "keep" hint, user "keep"
 hint.

 The less clear case in my mind is number 2, where one resumes an object
 that already exists, but makes no changes to it.  In the "verbose" Journal
 design, we'd say something like: "Looked at <some object>."  However, in
 the object based view, it doesn't make sense to treat this as a new
 version.  I suggest for simplicity that we simply ignore this for now, and
 only create an entry when an object is modified.

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