[Bugs] #2388 UNSP: Deleting bundle from journal does not uninstall library bundle

Sugar Labs Bugs bugtracker-noreply at sugarlabs.org
Thu Sep 30 08:24:44 EDT 2010


#2388: Deleting bundle from journal does not uninstall library bundle
------------------------------------------+---------------------------------
    Reporter:  tonyforster                |          Owner:  tomeu                      
        Type:  defect                     |         Status:  new                        
    Priority:  Unspecified by Maintainer  |      Milestone:  Unspecified by Release Team
   Component:  sugar                      |        Version:  Git as of bugdate          
    Severity:  Major                      |       Keywords:  dextrose                   
Status_field:  New                        |   Distribution:                             
   Seeta_dev:  unassigned                 |  
------------------------------------------+---------------------------------
Changes (by garycmartin):

  * seeta_dev:  => unassigned


Comment:

 Replying to [comment:1 sascha_silbe]:
 > We recently changed activities to behave exactly this way (see #1512),
 so we probably shouldn't make content bundles behave otherwise.
 > This needs input from the Design Team. One option might be to include
 installed content bundles in the list view of the home screen (activities
 list).

 FWIW: There is some agreement in trying to remove the home list view
 (users get lost there and/or think they are in the Journal). The Journal
 fav stars could then be used select what is shown in the home fav view
 (thus allowing any Journal entry to be shown on the home fav view, another
 request we've seen). This implies that the Journal will need to display
 all _installed_ activity bundles, and possibly library content could be
 shown as well, however the direction has been away from supporting
 'content bundles'. Ideally Browse should support opening zipped up web
 directories, and then we don't need the extra magic ways for the custom
 library UI/support/maintenance issues, as they could be
 used/manipulated/shared just like any other Journal entry. I'm planning on
 putting up a feature pages (Christian is interested in helping out on this
 as well).

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


More information about the Bugs mailing list