#7071 HIGH 8.2.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:  8.2.0 (was Update.2)           
  Component:  sugar        |     Version:  Update.1                       
 Resolution:               |    Keywords:  sugar-love 8.2.0:? blocks:8.2.0
Next_action:  communicate  |    Verified:  0                              
  Blockedby:               |    Blocking:                                 
---------------------------+------------------------------------------------

Comment(by Eben):

 Replying to [comment:24 gregorio]:
 > Hi Guys,
 >
 > Do we have agreement on this? Someone asked me if we should start the
 feature exception process to get this in. I think we should if we are sure
 it meets Bryan's needs and can be done without risking the date.
 >
 > My only concern is that I don't really understand the proposed design!
 I'm used to seeing a functional specification that explains exactly what
 the feature will do. Maybe I can just have Eben show it to me when I am in
 1 CC on Thursday?

 An attempt:

  1. Add an "Erase" item to the secondary palette of activities in Home; it
 should be the last item in the menu, and have the list-remove icon.
  2. When the "Erase" item is activated, a non-modal alert should appear
 asking for confirmation of the deletion, offering "Cancel " and "Erase"
 buttons with the dialog-cancel and dialog-ok icons, respectively.
  3. Upon confirmation, uninstall the activity and remove it from Home
 (both views).
  4. (a) If the bundle is represented in the Journal, remove the associated
 Journal entry. (b) Remove the associated bundle object from the Journal
 (object view), but leave any related actions - such as the initial
 download, transfer from a friend, or transfer from external storage -
 visible (action view).
  5. If a bundle which no longer lives on the laptop but is referenced
 within an action entry is clicked on, the system should attempt to recover
 the bundle from the metadata associated with the action (such as the
 download/update URL from the .info file of the original bundle, which we'd
 need to be sure to keep).

 Notes on the above specification:

  * (2) covers your concern that removing could be done too easily.  One of
 the reasons its relegated to the secondary palette (instead of being
 directly exposed in the view) is to likewise make it a "harder" action to
 invoke.  It should be noted that adding this alert will also break string
 freeze, in addition to feature/code freeze.
  * (4a) is the approach we are taking now, and is consistent with the
 behavior of the current Journal which is much more like the future objects
 view.  (4b) is what we will aim for once the new Journal arrives, at which
 point we'll need to carefully consider (5).

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