Changes

consolidate Keep and Save as, Keyboard shortcuts link
Line 1: Line 1: −
<noinclude>{{TOCright}}
+
<noinclude>__TOC__
 
[[Category:Help]]
 
[[Category:Help]]
 
</noinclude>
 
</noinclude>
Line 59: Line 59:  
===[[The Undiscoverable/Collaboration|Collaboration]]===
 
===[[The Undiscoverable/Collaboration|Collaboration]]===
   −
===Keep button===
+
===Keep button and Saving work===
    
Keep places a checkpoint of the current state of your application in the Journal, including a screen shot, Activity state, and metadata. The user can rename the session from the name of the Activity to something specific to the session, and add a description and tags. Users do not agree on why and when to use Keep. See [[Human_Interface_Guidelines/The_Laptop_Experience/The_Journal#The_Notion_of_.22Keeping.22| The Notion of "Keeping"]] in the Sugar Human Interface Guidelines.
 
Keep places a checkpoint of the current state of your application in the Journal, including a screen shot, Activity state, and metadata. The user can rename the session from the name of the Activity to something specific to the session, and add a description and tags. Users do not agree on why and when to use Keep. See [[Human_Interface_Guidelines/The_Laptop_Experience/The_Journal#The_Notion_of_.22Keeping.22| The Notion of "Keeping"]] in the Sugar Human Interface Guidelines.
 +
====Saving Work====
 +
 +
Basically, we need a Save as... functionality, not just a Save that overwrites the previous version and a clumsy Save on Exit where you have to go roundabout to start up again. All of this should be bugged as a Feature Request.
 +
 +
<pre>On Thu, Oct 8, 2009 at 6:42 PM, Caroline Meeks <caroline@solutiongrove.com> wrote:
 +
> Today we worked with two groups on multiplication. They made squares with
 +
> each side being a different multiplication problem that had the same answer.
 +
> http://screencast.com/t/sUbiof2H
 +
>
 +
> We also had them reflect in their Journals about what they did.
 +
> All of this went well.
 +
>
 +
> What was horrible was trying to get the right point in the project saved to
 +
> the Journal and then navigating to the correct place to write.
 +
> The solution I suggest is when you click the Keep button (Journal Icon) from
 +
> an activity that the Journal reflection dialog box appears.
 +
> Here are the problems we had.
 +
>
 +
> Hard to get to the Journal, no easy F# short cut.
 +
> Hard to find the little arrow that gets you to where you can write.
 +
> Especially since if the Frame is active, which it has to be to get to the
 +
> Journal, the little bitty arrow you need to click is covered.
 +
> When students did their assigned task they were eager to go back to
 +
> exploring with Sugar and wrote over their work without it being saved, or
 +
> using the same name as the assigned activity.  This was probably the worst
 +
> outcome because then it was like they hadn't done the assignment, they had
 +
> nothing to show for their work and we'll want to use it later for a
 +
> portfolio.
 +
>
 +
> clicking the Activity Tab to write down the name is a PITA (this one is
 +
> fixed in .88 I think).
 +
>
 +
> After they reflected they wanted to immediately go back to exploring in TA
 +
> and we had to stop them, make them change the name again. They were very
 +
> perplexed by this because they didn't know what to name their new file
 +
> because they hadn't done anything yet.
 +
>
 +
> The word "Description" is not very friendly. I like "What did you do?"
 +
> Walter wants to expand it even further, I'm not sure about that, its pretty
 +
> challenging for the students to type so I'm not sure we want more boxes.
 +
> Confusion between the Keep button and the samples and the snapshot icons.
 +
> No feedback when you click Keep so there is a tendency to click it
 +
> repeatedly.
 +
</pre>
    
===Downloading and installing activities===
 
===Downloading and installing activities===
Line 144: Line 188:  
* Now a smaller Xephyr window will launch
 
* Now a smaller Xephyr window will launch
 
** 832x624 matches the XO display proportions (Pages in Browse will mimic the layout of those on an XO.)
 
** 832x624 matches the XO display proportions (Pages in Browse will mimic the layout of those on an XO.)
 +
===Keyboard shortcuts===
 +
* [[olpc:Keyboard shortcuts]]
    
===Localization===
 
===Localization===
Line 192: Line 238:  
* When you download an image, it doesn't have a preview. Open it and close it immediately to generate one. [http://dev.sugarlabs.org/ticket/1106 Ticket #1106]
 
* When you download an image, it doesn't have a preview. Open it and close it immediately to generate one. [http://dev.sugarlabs.org/ticket/1106 Ticket #1106]
   −
===Saving Work===
  −
  −
Basically, we need a Save as... functionality, not just a Save that overwrites the previous version and a clumsy Save on Exit where you have to go roundabout to start up again. All of this should be bugged as a Feature Request.
  −
  −
<pre>On Thu, Oct 8, 2009 at 6:42 PM, Caroline Meeks <caroline@solutiongrove.com> wrote:
  −
> Today we worked with two groups on multiplication. They made squares with
  −
> each side being a different multiplication problem that had the same answer.
  −
> http://screencast.com/t/sUbiof2H
  −
>
  −
> We also had them reflect in their Journals about what they did.
  −
> All of this went well.
  −
>
  −
> What was horrible was trying to get the right point in the project saved to
  −
> the Journal and then navigating to the correct place to write.
  −
> The solution I suggest is when you click the Keep button (Journal Icon) from
  −
> an activity that the Journal reflection dialog box appears.
  −
> Here are the problems we had.
  −
>
  −
> Hard to get to the Journal, no easy F# short cut.
  −
> Hard to find the little arrow that gets you to where you can write.
  −
> Especially since if the Frame is active, which it has to be to get to the
  −
> Journal, the little bitty arrow you need to click is covered.
  −
> When students did their assigned task they were eager to go back to
  −
> exploring with Sugar and wrote over their work without it being saved, or
  −
> using the same name as the assigned activity.  This was probably the worst
  −
> outcome because then it was like they hadn't done the assignment, they had
  −
> nothing to show for their work and we'll want to use it later for a
  −
> portfolio.
  −
>
  −
> clicking the Activity Tab to write down the name is a PITA (this one is
  −
> fixed in .88 I think).
  −
>
  −
> After they reflected they wanted to immediately go back to exploring in TA
  −
> and we had to stop them, make them change the name again. They were very
  −
> perplexed by this because they didn't know what to name their new file
  −
> because they hadn't done anything yet.
  −
>
  −
> The word "Description" is not very friendly. I like "What did you do?"
  −
> Walter wants to expand it even further, I'm not sure about that, its pretty
  −
> challenging for the students to type so I'm not sure we want more boxes.
  −
> Confusion between the Keep button and the samples and the snapshot icons.
  −
> No feedback when you click Keep so there is a tendency to click it
  −
> repeatedly.
  −
</pre>
      
==Activities==
 
==Activities==