[Bugs] #1512 UNSP: Erasure of downloaded Activity entries in Journal permanently removes the code bundle

[Sugar Labs Bugs]

#1512: Erasure of downloaded Activity entries in Journal permanently removes the
code bundle
------------------------------------------+---------------------------------
    Reporter:  FGrose                     |          Owner:  tomeu                      
        Type:  defect                     |         Status:  new                        
    Priority:  Unspecified by Maintainer  |      Milestone:  Unspecified by Release Team
   Component:  sugar                      |        Version:                             
    Severity:  Unspecified                |       Keywords:  Usability design           
Distribution:                             |   Status_field:  New                        
------------------------------------------+---------------------------------

Comment(by alsroot):

 Replying to [comment:5 alsroot]:
 > Replying to [ticket:1512 FGrose]:
 > > This behavior in the Journal is inconsistent with other 'installed'
 Activities, which are erased (un-installed) with a warning dialog from the
 Home list view.
 > >
 > > Additionally, when one erases an updated Activity from the Home list
 view, it is not permanently erased as the code bundle referenced in the
 Journal download entry is still available.
 > >
 > > These peculiarities in this design lead to confusion and might better
 be hidden or reconciled.
 > >
 > > The download event record, as a system event, might have a 'hide
 event' option or not be erasable.  The code bundle behind the event
 should, perhaps, only be erased from the Home list view (installed-
 Activity-code-bundle management), while system or Activity events and
 their associated object instances are managed from the Journal of Activity
 event instances.
 >
 > The Zero Sugar tries to reconcile this from scratch, i.e., every
 activity will be identified by http url, there will be no need to download
 .xo if user wants to have activity launcher in F3 list (activity code will
 be downloaded on the first launch). Activity implementations will not be
 stored in journal. imo, trying to reuse journal for not trivial cases like
 packaging is overkill.

 I.e. there will be only one place where activities live, in F3 view (or in
 its analog). For now, we have natively installed activities (represented
 in F3 but w/o chances to remove), installed from .xo (also represented in
 F3 view), .xo in journal.

-- 
Ticket URL: <http://bugs.sugarlabs.org/ticket/1512#comment:6>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system