[Sugar-devel] Journal and Updating Software Process
fgrose at gmail.com
Wed Jul 28 12:14:20 EDT 2010
On Wed, Jul 28, 2010 at 10:02 AM, Daniel Castelo <
dcastelo at plan.ceibal.edu.uy> wrote:
> On Tue, Jul 27, 2010 at 11:51 PM, Frederick Grose <fgrose at gmail.com>wrote:
>> On Tue, Jul 27, 2010 at 9:37 PM, James Cameron <quozl at laptop.org> wrote:
>>> On Tue, Jul 27, 2010 at 06:37:18PM -0300, Daniel Castelo wrote:
>>> > * The activities are updated
>>> With "Software update" or manually using Browse?
>>> > * The user delete the journal entry with the activity bundle
>>> > downloaded for this updating process.
>>> > The result of this is that the activity is deleted from sugar
>>> I've seen this on Sugar 0.84 if the activity was updated using Browse,
>>> but not if the activity was updated using "Software update".
>>> > This behavour is normal? Should I reported this as a bug?
>>> If you think it is a bug, then check for it in bugs.sugarlabs.org
>> See https://bugs.sugarlabs.org/ticket/1512
> Great. Thanks!
> The trac ticket suggest a new behavour:
> "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."
> Which is the next step that I should follow to solve this issue? I suposse
> that is to discuss in this email list which could be the best solution.
As noted, the problem of inadvertent deletion of updated or newly added
Activity bundles may occur in the Journal or in the Home list view (through
the erase action in an extended palette). The most comprehensive solution
might involve grouping of Journal items , but that won't be quick.
A quicker solution may be to recognize the Journal entry type or kind in the
Journal (if that is sufficient) and hide or remove the 'erase' entry action
from the palette in the Journal. This would force intentional erasure to
occur in the Home list view, where the intent may be clearer.
Alternatively, erasure from the Journal could be disabled for these entries
unless they were in a filtered, Journal view (by their kind, a kind which
currently is not available in the filter list).
 This discussion thread,
this wiki page, http://wiki.sugarlabs.org/go/Talk:Features/Content_support,
describes a Journal group design for supporting Activity and content
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Sugar-devel