[Sugar-devel] [FEATURE] Activity as a regular Journal Object request for inclusion to 0.88

Simon Schampijer simon at schampijer.de
Sat Dec 5 03:52:57 EST 2009

On 12/03/2009 06:23 AM, Eben Eliason wrote:
> On Tue, Dec 1, 2009 at 5:54 AM, Martin Langhoff
> <martin.langhoff at gmail.com>  wrote:
>> On Mon, Nov 30, 2009 at 9:40 PM, Wade Brainerd<wadetb at gmail.com>  wrote:
>>> When deleting an object from the Journal that is an activity bundle,
>>> we ought to display an alert with a scary icon.  The alert should
>>> clearly state that Journal entries will no longer be able to be opened
>>> until the activity is reinstalled.
>> Majority of 6 year old will not understand that.
> The best way to handle this, I think, is to let kids delete activities
> but also keep a reference to the source in the form of an update URL
> or similar, so that fetching the activity automatically when an
> instance of it is resumed can be done. There's additional UI work
> there, and we can't guarantee connectivity, etc., but it would help
> reduce the overhead involved. (I'm not suggesting we shouldn't find
> ways to make it clearer when a deletion is happening, either, but as
> noted, the dialog may not work in practice with the target audience.)

Actually, one HI guideline was, that you can undo things. This currently 
applies to simple actions in activities (paste, copy etc). There are no 
ways to undo deleting a Journal entry (or object). For activity 
instances your proposed idea to provide a download link could be one 
option. This does not work for other entries though.

Maybe a bin that caches the objects would work? You can empty it on 
demand and it is emptied automatically when shutting down Sugar.


More information about the Sugar-devel mailing list