We should make sure that this works in the case of the 'xs' machine being a disk attached to a teacher's xo, including the more limited times of availability and bandwidth implied. <br><br><div class="gmail_quote">
On Wed, Oct 22, 2008 at 10:10 PM, Tony Anderson <span dir="ltr"><<a href="mailto:tony_anderson@usa.net">tony_anderson@usa.net</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;">
All of this is already implemented in Moodle which will be installed in XS.<br>
<font color="#888888"><br>
Tony<br>
</font><div><div></div><div class="Wj3C7c"><br>
On Wed, Oct 22, 2008 at 2:07 PM, Eben Eliason <<a href="mailto:eben.eliason@gmail.com">eben.eliason@gmail.com</a>><br>
wrote:<br>
> > I'm not sure that such an idea actually requires a special activity,<br>
> > or a "report card" template with preset fields. It seems to me that<br>
> > the item of importance is the ability for the teacher to give each kid<br>
> > an immutable object which they may then view on their XO, and take<br>
> > home to show their parents. This object might be a .pdf, or it might<br>
> > be an image, or it might be something else, but the teacher could<br>
> > create such an object in Write, or in a spreadsheet activity, or in<br>
> > whatever suits their needs best.<br>
> ><br>
> > It seems to me that the more interesting part of this problem is the<br>
> > distribution method. Unlike a homework assignment where the teacher<br>
> > could share an activity, or (in the future) send an object to everyone<br>
> > in the class group, there is need to distribute files individually to<br>
> > the kids by some unique identifier. Perhaps this is the place where<br>
> > an "Evaluate" activity does have it's place. If done well, a fresh<br>
> > instance of the activity could provide a way for a teacher to fill out<br>
> > evaluations (or import in their desired format!) and identify which<br>
> > kid each belongs to. Then, upon sharing that single evaluation<br>
> > activity with the class, each kid would receive *only* their own<br>
> > evaluation from the shared instance. That instance would then, every<br>
> > time they open it, simply be a viewer for that particular evaluation.<br>
> > This is a good example where the master-slave (usually discouraged in<br>
> > Sugar) would actually work.<br>
> ><br>
> > - Eben<br>
<br>
</div></div><div><div></div><div class="Wj3C7c">_______________________________________________<br>
Sugar mailing list<br>
<a href="mailto:Sugar@lists.laptop.org">Sugar@lists.laptop.org</a><br>
<a href="http://lists.laptop.org/listinfo/sugar" target="_blank">http://lists.laptop.org/listinfo/sugar</a><br>
</div></div></blockquote></div><br>