[Sugar-devel] [IAEP] [DESIGN] 'Resume' vs 'Start a new' Activity
Simon Schampijer
simon at schampijer.de
Sun Jan 10 15:12:02 EST 2010
On 01/08/2010 04:02 PM, Bert Freudenberg wrote:
> On 08.01.2010, at 15:41, Edward Cherlin wrote:
>>
>> On Fri, Jan 8, 2010 at 05:39, Gerald Ardito<gmanb5 at gmail.com> wrote:
>>> I am interested in this discussion.
>>> I am managing a deployment of 140 XOs/SOAS (mostly XOs) and this issue comes
>>> up a lot with the students. A couple of classrooms are just finishing a
>>> project with EToys and Resume was a big problem for us.
>>> In EToys, you seem to have to rename the project in the Journal. So, every
>>> Journal entry says, by default, "EToys Project." So, time is lost trying to
>>> find the right one (until the students get the naming thing).
>>
>> In my draft guide to Discovery, I am suggesting that teachers
>> explicitly tell students how to name sessions for the first few days,
>> with decreasing guidance as students get the idea.
>>
>> "We are going to save our work now. Click the stop sign, everybody. Do
>> you see that the name "Etoys Project" is highlighted? That means you
>> can just start typing your own name for your session. Type the name
>> [name] in place of "EToys Project". Now click OK.
>>
>> "Save your work, everyone. Does anybody remember how?" "Click the Stop
>> icon and give the session a name?", some student asks. "Right."
>>
>> "Now save your session. What should we call it?" Accept a suggestion
>> and write it on the board.
>>
>> "Now save your session, and remember--" "To name it!!" they all shout.
>
> This works fine for other activities. For Etoys, we never got around to implement the prompt-for-title-on-stopping-an-unnamed-instance-dialog. And more recent discussion suggested that dialog is too annoying anyway. It may get removed in a future Sugar version. So currently that ticket has a rather low priority - feel free to comment:
There is a Feature about that topic, too.
http://wiki.sugarlabs.org/go/Features/Write_to_journal_anytime
Regards,
Simon
More information about the Sugar-devel
mailing list