[Sugar-devel] Have a discard option in the "name a fresh instance" dialog

Gary C Martin gary at garycmartin.com
Wed Feb 18 18:49:54 EST 2009


On 18 Feb 2009, at 23:42, Eben Eliason wrote:

> This was part of the intended design.  I also still think that the
> "keep" or "don't keep" distinction should remain.  The fact that
> entries appear in the Journal before the activity has stopped or the
> keep button is pressed is a "bug", as I see it.  The Journal/DS should
> be silently keeping track /in the background/ of a temporary save
> file, which can be promoted to a real entry in the case of activity or
> Sugar crash, but I think that an explicit action (stop, keep) should
> result in a new Journal entry.

Oooh, that would also reduce the number of times I switch to Journal  
to resume a previous entry only to discover that  after I've clicked,  
2 or 3 seconds later, Journal finally re-redraws and switches me or  
resumes the wrong entry because the entry display order changes.

--Gary

> I'm certainly open to opinions on this.
>
> - Eben
>
>
> On Wed, Feb 18, 2009 at 4:53 PM, Eduardo H. Silva <hoboprimate at gmail.com 
> > wrote:
>> 2009/2/18 Gary C Martin <gary at garycmartin.com>:
>>> On 18 Feb 2009, at 20:31, Wade Brainerd wrote:
>> [snip]
>>> I'd like to see a 'don't keep' as well, but I think it's a bunch  
>>> more
>>> complicated in the current data-store implementation. Activities  
>>> get Journal
>>> entries created as you switch away from them, and perhaps some  
>>> other cases
>>> (sleep?), so a 'don't keep' button would need to actively DELETE  
>>> journal
>>> entries that may have been created before the activity was first  
>>> stopped.
>> This is the reason I think the terminology should be erase, or
>> discard, because it has already been "kept" automatically. But I'm
>> talking about the frontend of course, I don't know much about the
>> backend of things.
>>
>> Eduardo
>>
>>>
>>> Just wanted to raise the implementation issues, but I would like a  
>>> 'don't
>>> keep' if it didn't burn too much core dev time, though I accept  
>>> this may be
>>> due to my particular current Sugar usage pattern.
>>>
>>> --Gary
>>>
>>>> Best,
>>>> Wade
>>>>
>>>> On Wed, Feb 18, 2009 at 3:27 PM, Eduardo H. Silva <hoboprimate at gmail.com 
>>>> >
>>>> wrote:
>>>> Hi, I managed to run the latest development release of Sucrose.
>>>> When you close a fresh new activitiy instance, it shows a dialog to
>>>> name and keep the instance. I think it should also have the  
>>>> option to
>>>> discard it, which would unclutter the journal with so many  
>>>> unusefull
>>>> entries. It would use the Erase icon (a white minus inside a black
>>>> circle), so as not to confuse other ocasions where the cross in  
>>>> black
>>>> circle is used to escape or cancel an option. The accept icon could
>>>> perhaps be the Keep icon instead. This way, we are asking the  
>>>> user if
>>>> he wants to keep or not the instance, and if so, give him the  
>>>> option
>>>> to name it. What do you think?
>>>>
>>>> Eduardo
>>>> _______________________________________________
>>>> Sugar-devel mailing list
>>>> Sugar-devel at lists.sugarlabs.org
>>>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>>>
>>>> _______________________________________________
>>>> Sugar-devel mailing list
>>>> Sugar-devel at lists.sugarlabs.org
>>>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>>
>>>
>>



More information about the Sugar-devel mailing list