Re: [Sugar-devel] Keep confusion, yet again
Hi Daniel,
In attach I'm sending a patch which change the Keep string to Keep a
copy.
Hope it will help.
Daniel Drake wrote:
Argh!
Another country, another core team confused by the Keep button.
The Argentinian in-house generated teaching materials say: (translated
from Spanish)
To save the work that you did in the activity, go to the toolbar at
the top of the screen and click the Keep button.
Same story every single time.
Pretty please can someone please pick up the project of improving this
situation? Even if it's just killing this button for the time being.
I've seen this confusion in all 6 of the countries that I've visited.
And in most of those cases, it's written in the teacher training
materials, so the trainers pass this misinformation onto the teachers
who pass it onto the children.
For now I am going to update the Spanish translation to say Guardia
copia (Keep a copy) but this is not the solution...
Daniel
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
--
Jorge A. Saldivar G.-
From 8a2da36117aa8b5e38fb0ead9664024d47ab4e96 Mon Sep 17 00:00:00 2001
From: Jorge Saldivar jsaldi...@paraguayeduca.org
Date: Wed, 21 Apr 2010 17:26:50 -0400
Subject: [PATCH] Change keep string to keep a copy
---
src/sugar/activity/widgets.py |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/src/sugar/activity/widgets.py b/src/sugar/activity/widgets.py
index 2867666..5ce82bd 100644
--- a/src/sugar/activity/widgets.py
+++ b/src/sugar/activity/widgets.py
@@ -163,7 +163,7 @@ class KeepButton(ToolButton):
def __init__(self, activity, **kwargs):
ToolButton.__init__(self, **kwargs)
-self.props.tooltip = _('Keep')
+self.props.tooltip = _('Keep a copy')
self.props.accelerator = 'CtrlS'
client = gconf.client_get_default()
--
1.6.3.3
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Keep confusion, yet again
Reviewed-by: James Cameron qu...@laptop.org -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Keep confusion, yet again
Hi Jorge,
- self.props.tooltip = _('Keep')
+ self.props.tooltip = _('Keep a copy')
I think this will break translations. Not sure what our procedure for
renaming a string is; you might want to make your patch also change
all instances of 'msgid Keep' in po/* to be 'msgid Keep a copy',
which would keep the translations working.
Thanks,
- Chris.
--
Chris Ball c...@laptop.org
One Laptop Per Child
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Keep confusion, yet again
On 21 April 2010 18:48, Chris Ball c...@laptop.org wrote:
Hi Jorge,
- self.props.tooltip = _('Keep')
+ self.props.tooltip = _('Keep a copy')
I think this will break translations.
I think that's what we want; this new string will come up as
untranslated in pootle, alerting translators to submit translations
for the clearer string.
Daniel
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Keep confusion, yet again
Hi, I think that's what we want; this new string will come up as untranslated in pootle, alerting translators to submit translations for the clearer string. Ah, that's fine. (I assumed we'd want to use the old translations in the meantime.) - Chris. -- Chris Ball c...@laptop.org One Laptop Per Child ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Keep confusion, yet again
On 21.04.2010, at 23:57, Chris Ball wrote: Hi, I think that's what we want; this new string will come up as untranslated in pootle, alerting translators to submit translations for the clearer string. Ah, that's fine. (I assumed we'd want to use the old translations in the meantime.) - Chris. The actual problem is that renaming the button does not help. The mouse-over balloon in Etoys says: Keep a copy of the current project in the Journal It's no use. There are only two options IMHO: 1) Remove the button. If you want to copy an entry, use the Journal. 2) Make the button actually overwrite the entry. No silent auto-save on exit, but ask if save is desired. - Bert - ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Keep confusion, yet again
On Wed, Apr 21, 2010 at 6:22 PM, Bert Freudenberg b...@freudenbergs.de wrote: On 21.04.2010, at 23:57, Chris Ball wrote: Hi, I think that's what we want; this new string will come up as untranslated in pootle, alerting translators to submit translations for the clearer string. Ah, that's fine. (I assumed we'd want to use the old translations in the meantime.) - Chris. The actual problem is that renaming the button does not help. The mouse-over balloon in Etoys says: Keep a copy of the current project in the Journal It's no use. There are only two options IMHO: 1) Remove the button. If you want to copy an entry, use the Journal. 2) Make the button actually overwrite the entry. No silent auto-save on exit, but ask if save is desired. I'd lean toward the first option. It's intended purpose was always to be a convenience on top of auto-save, that simply forced a new version. Once Sugar has full version support, and a Journal updated to take advantage of it, restoring the Keep functionality as it exists probably wouldn't cause problems anymore. Until then, I think the auto-save is much friendlier than the usual prompt-on-quit, with the possibility for lost work. Eben - Bert - ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Keep confusion, yet again
Hi Eben, I'd lean toward the first option. It's intended purpose was always to be a convenience on top of auto-save, that simply forced a new version. Once Sugar has full version support, and a Journal updated to take advantage of it, restoring the Keep functionality as it exists probably wouldn't cause problems anymore. Until then, I think the auto-save is much friendlier than the usual prompt-on-quit, with the possibility for lost work. Think I'm having trouble following -- are you proposing that we remove the Keep button now, and also remove the prompt-on-quit dialog now? Thanks, - Chris. -- Chris Ball c...@laptop.org One Laptop Per Child ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Keep confusion, yet again
On Wed, Apr 21, 2010 at 7:18 PM, Chris Ball c...@laptop.org wrote: Hi Eben, I'd lean toward the first option. It's intended purpose was always to be a convenience on top of auto-save, that simply forced a new version. Once Sugar has full version support, and a Journal updated to take advantage of it, restoring the Keep functionality as it exists probably wouldn't cause problems anymore. Until then, I think the auto-save is much friendlier than the usual prompt-on-quit, with the possibility for lost work. Think I'm having trouble following -- are you proposing that we remove the Keep button now, and also remove the prompt-on-quit dialog now? No, sorry. The current prompt-on-quit is fine, as it only occurs when you stop a brand new activity instance. It basically asks do you want me to keep track of this thing in your Journal, and from then on it will auto-save as usual. Since the Keep button is causing so much confusion, I was proposing to remove it for now (until we have more complete version support), but keep the prompt the first time a new instance is stopped. We can still skip the prompt if the instance is manually renamed, under the assumption that naming the item implies a desire to track it in the Journal. Eben Thanks, - Chris. -- Chris Ball c...@laptop.org One Laptop Per Child ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Keep confusion, yet again
On Wed, Apr 21, 2010 at 07:27:44PM -0400, Eben Eliason wrote: No, sorry. The current prompt-on-quit is fine, as it only occurs when you stop a brand new activity instance. It basically asks do you want me to keep track of this thing in your Journal, ... How do I answer no? As far as I can tell, it basically asks you will keep track of this thing in your journal, what name, description and tags do you want? -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Keep confusion, yet again
On 22.04.2010, at 01:39, James Cameron wrote: On Wed, Apr 21, 2010 at 07:27:44PM -0400, Eben Eliason wrote: No, sorry. The current prompt-on-quit is fine, as it only occurs when you stop a brand new activity instance. It basically asks do you want me to keep track of this thing in your Journal, ... How do I answer no? As far as I can tell, it basically asks you will keep track of this thing in your journal, what name, description and tags do you want? You can't. Btw, in the next Etoys version I intend to implement option 2. The auto-save-on-exit just does not work out for Etoys. Playing with an Etoys project modifies it, so when exiting, it's not in the same state as the author wanted. - Bert - ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Keep confusion, yet again
On Thu, Apr 22, 2010 at 01:48:09AM +0200, Bert Freudenberg wrote: On 22.04.2010, at 01:39, James Cameron wrote: On Wed, Apr 21, 2010 at 07:27:44PM -0400, Eben Eliason wrote: No, sorry. The current prompt-on-quit is fine, as it only occurs when you stop a brand new activity instance. It basically asks do you want me to keep track of this thing in your Journal, ... How do I answer no? As far as I can tell, it basically asks you will keep track of this thing in your journal, what name, description and tags do you want? You can't. Ah, okay. For a few minutes I thought I had missed something obvious. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Keep confusion, yet again
Argh! Another country, another core team confused by the Keep button. The Argentinian in-house generated teaching materials say: (translated from Spanish) To save the work that you did in the activity, go to the toolbar at the top of the screen and click the Keep button. Same story every single time. Pretty please can someone please pick up the project of improving this situation? Even if it's just killing this button for the time being. I've seen this confusion in all 6 of the countries that I've visited. And in most of those cases, it's written in the teacher training materials, so the trainers pass this misinformation onto the teachers who pass it onto the children. For now I am going to update the Spanish translation to say Guardia copia (Keep a copy) but this is not the solution... Daniel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Keep confusion, yet again
On 19 April 2010 09:41, Daniel Drake d...@laptop.org wrote: For now I am going to update the Spanish translation to say Guardia copia (Keep a copy) but this is not the solution... Meant to write Guardar copia. Daniel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Keep confusion, yet again
On Mon, 2010-04-19 at 09:41 -0300, Daniel Drake wrote: Argh! Another country, another core team confused by the Keep button. The Argentinian in-house generated teaching materials say: (translated from Spanish) To save the work that you did in the activity, go to the toolbar at the top of the screen and click the Keep button. Same story every single time. Pretty please can someone please pick up the project of improving this situation? Even if it's just killing this button for the time being. I've seen this confusion in all 6 of the countries that I've visited. And in most of those cases, it's written in the teacher training materials, so the trainers pass this misinformation onto the teachers who pass it onto the children. I've seen users and teachers fooled by the Keep key here too. I remember reading in an old book on human interface design called The Psychology of Everyday Object that testers are never going to report usability annoyances of this kind, attributing the mistake to themselves rather than to the UI designer. For now I am going to update the Spanish translation to say Guardia copia (Keep a copy) but this is not the solution... Jorge is going to work on this. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Keep confusion, yet again
Bernie wrote: I remember reading in an old book on human interface design called The Psychology of Everyday Object that testers are never going to report usability annoyances of this kind, attributing the mistake to themselves rather than to the UI designer. Our new testers in Sri Lanka certainly reported this usability annoyance, but they did so on the testing@ mailing list, so I'm not sure if the relevant developers would have received it. ;-) -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
