[Sugar-devel] Nobody understands "Keep"

[Eben Eliason]

On Thu, Jul 9, 2009 at 7:55 PM, Eduardo H. Silva<hoboprimate at gmail.com> wrote:
> 2009/7/9 Tomeu Vizoso <tomeu at sugarlabs.org>:
>> On Thu, Jul 9, 2009 at 12:29, Martin Dengler<martin at martindengler.com> wrote:
>>> On Thu, Jul 09, 2009 at 11:22:16AM +0100, Daniel Drake wrote:
>>>> On Thu, 2009-07-09 at 10:45 +0100, Martin Dengler wrote:
>>>> > On Thu, Jul 09, 2009 at 09:52:23AM +0100, Daniel Drake wrote:
>>>> > > Nobody in the world seems to understand the Keep button. People think
>>>> > > it's for regular saving and you should do it before you close or switch
>>>> > > away from your activity.
>>>> >
>>>> > That's not far from the truth, right?  At least in any work-losing or
>>>> > surprising way...
>>>>
>>>> It's far from the truth in that it's not normally what you want to
>>>> do.
>>>
>>> My quoting-foo is bad, so I've caused confusion (in myself, too :)).
>>>
>>>> To save your work, simply click the Stop button or change so that
>>>> another activity has focus. If you click Keep, you'll end up with 2
>>>> copies - one from when you clicked Keep, and one from when you clicked
>>>> Stop (or focused on another activity).
>>>>
>>>> As far as I understand it, Keep is useful for these types of scenarios:
>>>> - you've done a lot of work but now it's time to refactor/reorganize the
>>>> whole thing. However you want to keep a copy of the rough version you
>>>> have now, as "insurance" or perhaps for reference while you re-mangle
>>>> the work.
>>>> - you've made a template for something, now you want to save that
>>>> template (as a blank template) before starting on a version where you
>>>> fill in the content.
>>>
>>> This is a great explanation -- it should be in the HIG or something.
>>
>> But the biggest problem is how do we explain this to users without
>> them having to read the HIG (or manual)?
>>
>> Should be called "Keep a copy"?
>
> +1
> For a while, in the pt_PT translation of Sugar I did, I named the Keep
> button as Keep a copy.

I urge again that "keep a copy" is not what is intended, in the long
run. Without proper versions, of course, this is effectively how it
behaves. Therefore, it's no surprise many saw it this way. But with
versions, the "keep" button is actually a "keep new version" button.
As mentioned before, a "new version" retains the tree_id, whereas a
true "copy" does not.

Since versions are on the way, we should make sure to clarify the distinction!

Eben


>>
>> Regards,
>>
>> Tomeu
>>
>>>> Daniel
>>>
>>> Martin
>>>
>>> _______________________________________________
>>> 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
>>
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>