#1739 NORM Trial-3: Allow adding and removing activities to the bottom frame

[Zarro Boogs per Child]

#1739: Allow adding and removing activities to the bottom frame
--------------------------+-------------------------------------------------
  Reporter:  tomeu        |       Owner:  Eben   
      Type:  enhancement  |      Status:  new    
  Priority:  normal       |   Milestone:  Trial-3
 Component:  sugar        |     Version:         
Resolution:               |    Keywords:         
  Verified:  0            |  
--------------------------+-------------------------------------------------
Comment (by tomeu):

 Replying to [comment:3 Eben]:
 > Your comment about Sugar integration is a little bit confusing to me.
 When you say that you "load in" all activities in ~/Activities, do you
 mean that you put every one there into the frame directly?

 Yup, all activities except those that have show_launcher=no in their
 activity.info (Read, right now).

 > If that's the case, we really need to have the "loader" check the state
 to be sure the activity reference should be put there at all.  Also, note
 that the stored state should actually be kept as an array, and not a bunch
 of booleans.  We want to remember relative position, so that they can be
 arranged as the child wishes.

 Ok, we could use a config file similar to the one we use for remembering
 friends or access points.

 > Regarding your questions:
 >
 > We either need all activities to exist as Journal entries, or we need to
 lock those that are shipped so that they can't ever be removed.  I think
 the former solution is the better one, although it does force things into
 the Journal that the child didn't create themselves.  Still, for
 management purposes, I feel it's best to treat them equally.  In order to
 put an activity back into the frame, the child could drag it in from the
 Journal, or check the checkbox/toggle within the Journal entry which
 represents its presence there; it would just be appended to the end of the
 list when checked.

 Yes, but what happens if the children deletes the journal entry for
 Browse? He needs to get a new Browse activity from some other laptop? And
 what about the Journal? It's an even more special activity.

 What if we have a basic set of activities that appear on the frame, cannot
 be removed from there, and don't appear in the Journal? They could be
 Browse, Paint, Write, Record, Chat, ... the ones we consider are part of
 Sugar. Perhaps we could lock them on the left side of the frame and leave
 the right side for adding shortcuts to activities in the Journal. Some of
 the shipped activities won't be so integral to the Sugar experience.

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