#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:                    
-------------------------+--------------------------------------------------

Comment(by Eben):

 Replying to [comment:16 mikus]:
 > I'm posting here to say that "an URL" isn't an universal solution to
 "where did this Activity come from?"  Not everyone will have "downloaded"
 an Activity in order to install it.  Nepal gets some Activities by
 installing a "country custom" build.  I get some Activities by fetching
 tarballs from obscure contributors, then _installing_ them from a working
 directory.  Such cases do NOT provide an URL.

 Certainly true, though I suspect that it will cover a fair number of
 cases.  For starters, none of the "outside ways" of installing activities
 you mention result in Journal entries anyway, so the point is moot.  My
 goal here is, to the extent possible, to provide some shred of evidence
 about how to obtain an activity ''from'' its Journal entry once the actual
 bundle is gone. (My assumption in the case of the country customizations
 is that the local library, or at least the school server, will make the
 activity readily available.  My assumption in the case of installing with
 wget and sugar-install-bundle is that the kid has the capability to track
 down a fresh copy himself.) When a kid does install an activity via
 downloading it, we'll have the download URL; when a kid receives an
 activity from a friend or from an external storage device, the action
 entry in the Journal will specifically say who/what it came from; and in
 all cases, we'll have the URL as specified in the .info file, at the very
 least, assuming it has a Journal entry at all.

 > --------
 >
 > Now that we *have* designed a list of installed Activities in Home view
 -- let's __use__ that list for more than choosing which icons to display.

 That's certainly the course of action we're aiming to take.

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