<br><br><div class="gmail_quote">On Fri, Jul 17, 2009 at 1:39 PM, Daniel Drake <span dir="ltr"><<a href="mailto:dsd@laptop.org">dsd@laptop.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
2009/7/16 David Farning <<a href="mailto:dfarning@sugarlabs.org">dfarning@sugarlabs.org</a>>:<br>
<div class="im">> A possible answer would be to abstract ALSOParse.py and microformat.py<br>
> as back ends for Sugar-Update-Control (SUC).<br>
<br>
</div>It's not so much the issue of losing support for the existing<br>
widely-deployed setup (although that would be unfortunate), it's that<br>
this seems to lack design. The microformat-style update (along with<br>
certain characteristics of the updater and server implementation) is<br>
not perfect, but it is good for field use and "G1G1" style internet<br>
users.<br>
<br>
The motivation for moving to "aslo" seems to be only that of "because<br>
it's running on <a href="http://sugarlabs.org" target="_blank">sugarlabs.org</a>," without consideration for any<br>
technical pros or cons of the different format, how it might be<br>
deployed in the field, etc. I think you should take a more detailed<br>
approach to this, without limiting yourself to the quirks and current<br>
behaviour of the aslo code.</blockquote><div><br>+1<br><br>Do we have use cases for this? It seems like this is sorta like a bunch of other thngs we need to enable.<br><br>Off the top of my head<br><br><ul><li>Teacher shares a file with a class</li>
<li>Teacher shares a file or lesson plan or student work sample with other teachers</li><li>Student shares with classmate for peer review</li><li>Student shares with teacher for assessment (need an easy way for teachers to see all students work)</li>
<li>Student shares with outside world</li><li>Student shares with school community</li><li>Teacher or student gets an activity for Sugar</li><li>Teacher or Student learns what is possible with Sugar from examples</li><li>
Students or classes of students collaobrate to co-create projects</li></ul>All different, but it would be good if the end users felt there was some consistant logic to how they did these tasks which may well be related in their minds.<br>
<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<font color="#888888"><br>
Daniel<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Caroline Meeks<br>Solution Grove<br>Caroline@SolutionGrove.com<br><br>617-500-3488 - Office<br>505-213-3268 - Fax<br>