[Bugs] #472 NORM: Remove unexpected 'save/load' tab from toolbar

[SugarLabs Bugs]

#472: Remove unexpected 'save/load' tab from toolbar
----------------------------+-----------------------------------------------
    Reporter:  garycmartin  |          Owner:  walter           
        Type:  enhancement  |         Status:  assigned         
    Priority:  Normal       |      Milestone:  0.86             
   Component:  Turtleart    |        Version:  Git as of bugdate
    Severity:  Major        |     Resolution:                   
    Keywords:               |   Distribution:  Unspecified      
Status_field:  Assigned     |  
----------------------------+-----------------------------------------------

Comment(by eben):

 I recall having discussions around the problem of demos/examples in the
 past, and there are two fair ways to handle it, I think.

  1. The "purest" method (in the activity instance model) is to reveal an
 example chooser of some kind when creating a new instance. This emphasizes
 the idea that part of instantiating a new activity from the template of
 its bundle includes a customization step which results in a pre-configured
 state for the new instance. Of course, the downside here is that you have
 to create a new instance to try a new example, which is often undesirable.
 (I think it depends on the learning context: this might be fine for a
 class setting where each example serves as the starting point for a given
 lesson, but breaks down for simple exploratory play.)

  2. Another option, I think, is to treat examples kind of like a "clear
 the canvass" button in a paint activity. In this method, it's just a
 feature of the activity that it supports "real-time" refreshing of its
 state. I think the best way to expose this, personally, is as a button in
 the primary toolbar of the activity which reveals a palette containing a
 set of available templates/demos/examples. The palette could contain a
 simple text list (like a menu), or a matrix of thumbnails illustrating
 projects, or a treeview with projects arranged into categories, etc. This
 method provides a nice consistent interface into the examples (the
 button), but allows the activity developer the freedom to expose them in
 the way appropriate to their content.

 If it would be beneficial to make an "examples" icon that would be
 consistent across all activities desiring such a button, I could try to
 work up some ideas. As a side note, I think it will be important to make
 the undo button work across the loading of an example, so that the act of
 loading an example doesn't destroy previous work without a way back. (The
 addition of version support in the Journal will also partially solve this.
 This is a perfect example of a moment when the activity itself should take
 the initiative to create a "tagged version"—one that will become an
 immediate Journal entry.)

-- 
Ticket URL: <http://dev.sugarlabs.org/ticket/472#comment:10>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system