Ticket #1512 (closed defect: fixed)
Erasure of downloaded Activity entries in Journal permanently removes the code bundle
|Reported by:||FGrose||Owned by:||alsroot|
|Priority:||Unspecified by Maintainer||Milestone:||0.90|
|Severity:||Unspecified||Keywords:||Usability design r+ dextrose|
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 value of the gray/colored Activity icon distinction is made evident in this situation. The colored icons in the GCompris suite should have another dimension or element to distinguish the two object types. Perhaps the gear icon could be used as a small decoration for all code bundles icons in Sugar.