See <a href="http://bugs.sugarlabs.org/ticket/535#comment:5">http://bugs.sugarlabs.org/ticket/535#comment:5</a>, Expose Journal, Home, Group, Neighborhood, & Frame Sources, where it's suggested that we extend the 'Show Source' facility to more of Sugar.<div> Learners like to exercise and demonstrate their knowledge by customizing or changing their environments. We can guide them to learn deeper concepts by giving them ways to encode their customizations. (Providing a convenient undo, save, and restore facility for their work would accelerate their learning.) The 'Modifying Sugar' chapter in our manual, <a href="http://en.flossmanuals.net/Sugar/ModifyingSugar">http://en.flossmanuals.net/Sugar/ModifyingSugar</a>, provides a nice entry ramp for this learning activity. We could provide a similar tutorial for other Sugar features and then benefit from the creativity of all our learners.</div> <div> On Sat, Mar 13, 2010 at 8:11 AM, Bernie Innocenti <<a href="mailto:bernie@codewiz.org">bernie@codewiz.org</a>> wrote: > > On Sat, 2010-03-13 at 13:35 +0100, Bert Freudenberg wrote: > > > So +1 to look customization. E.g., why not allow to change the > > gray frame color? In Etoys you can at least change the toolbar > > color (not permanently though, I should fix that). Even if it > > enrages our latte-drinking black-wearing designer friends ;) > > they're kids after all ... > > I feel that Sugar should aim to reach the same level of "hackability" of > eToys: every UI element is an object that you could drag, drop, copy or > modify. > > Of course, this has consequences in terms of stability and clarity. > Before we could unleash this power we need to think of ways to recover > from mistakes. If multiple undo is too hard, a "restore everything to > defaults" might be good enough. > > Perhaps we're worrying too much. Re-installing the system from USB takes > only 3 minutes and is already being done very often. A boy just showed > up on the door of the repair lab, saying: "se borró el Navegador" (the > Browse activity deleted itself :-) > > All we need to do is make the backup-update-restore procedure slightly > more automated so that kids and teachers could do it without bothering > the technicians. > > Actually, we don't even need to worry too much for a solid backup and > restore procedure. I've always suspected that most kids wouldn't care > about preserving their diary. Now it's confirmed: kids are flocking here > to get the new version of Sugar even though their journals are not going > to be preserved across the upgrade. > > On the other hand, teachers and teacher trainers always ask to preserve > the content of their journal. Technicians use a pair of simple shell > scripts to tar up the journal to a USB stick, so they don't depend on > being within the range of the correct school server. > > I'll summarize all these things in a field report asap. > > -- > // Bernie Innocenti - <a href="http://codewiz.org/">http://codewiz.org/</a> > \X/ Sugar Labs - <a href="http://sugarlabs.org/">http://sugarlabs.org/</a> > > _______________________________________________ > Sugar-devel mailing list > <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> > <a href="http://lists.sugarlabs.org/listinfo/sugar-devel">http://lists.sugarlabs.org/listinfo/sugar-devel</a> </div>