#7071 HIGH 9.1.0: Activities cannot be deleted via GUI

[Zarro Boogs per Child]

#7071: Activities cannot be deleted via GUI
-------------------------+--------------------------------------------------
   Reporter:  ffm        |       Owner:  tomeu             
       Type:  defect     |      Status:  new               
   Priority:  high       |   Milestone:  9.1.0             
  Component:  sugar      |     Version:  Update.1          
 Resolution:             |    Keywords:  sugar-love 9.1.0:+
Next_action:  never set  |    Verified:  0                 
  Blockedby:             |    Blocking:                    
-------------------------+--------------------------------------------------
Changes (by mikus):

 * cc: mikus at bga.com (added)


Comment:

 Replying to [comment:3 Eben]:
 > What I specified before, but has been questioned, is that the activity
 list in home should provide a one-stop activity management solution, from
 which one can update or delete any activities on the laptop.

 I think this is the way to go.  The 'list' view of activities should be
 more functional than just flagging which activities to show in the 'ring'
 view.

 > This is potentially confusing because there's a question of what happens
 in the Journal when an activity is deleted from the list.

 I myself don't use the Journal to install Activities -- I use sugar-
 install-bundle.  But if there is an entry in the Journal that shows the
 Activity being installed, then that entry should be deleted if the
 activity itself is deleted through home 'list' view.

 I don't myself know WHAT data the Journal keeps regarding *using* an
 Activity.  If only "data" is kept, and not any of the resources (e.g.,
 executables) associated with the Activity, my recommendation would be to
 leave that Journal entry alone (at the least, keeping that entry will show
 a history of "what the user did").

 If the user clicks on the Journal entry, and the Activity itself has been
 deleted, a suitable error message should be returned.

 The Journal needs to be able to handle (without ever crashing) the
 situation where the user formerly ran Activity_version_A, but in the
 meantime Activity_version_A has been deleted, and has now been replaced in
 the system by Activity_version_Z (where possibly the data stored for A are
 incompatible with the data needed by Z - such a conflict should be treated
 as a "Activity_version_A is not installed" situation).

 > Do we decouple the bundle from the installation completely, so that
 deleting a bundle does *not* uninstall the activity?

 Simplest answer - yes.  [Let the Journal show "what is in the "system
 database", whereas the home 'list' view shows (with some additions) "what
 is in /home/olpc/Activities".]

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