<div> <font face="Arial, Helvetica, sans-serif">Dear Drew,<br>
<br>
You are on the mark! Sugar has rich potential independent of the OLPC. As one of the first 25 people at Xerox PARC in the 1970's I was there when the "desktop" metaphor was developed. Since Xerox is the "document" company, there is little surprise that the desktop metaphor is document centric. Some of us who cared about kids also thought about other interfaces. Alan Kay surely falls into this category and his lengthy devotion to Smalltalkish environments attests to his dedication.<br>
<br>
What I like about Sugar is that it is (like many kids) verb-centric, not noun-centric. I'm currently developing a conference presentation on this topic and want to give (good) live CD's to all attendants so they can experience Sugar themselves on whatever hardware they have. I haven't experimented with the Xubuntu version yet, but will look at it in the next day or so.<br>
<br>
The fact is that, at long last, Sugar provides an opportunity for Seymour Papert's visions to reach critical mass. The hardware used should not be an issue.<br>
<br>
Warm regards,<br>
<br>
David Thornburg, PhD<br>
</font></div>
<div> <br>
</div>
<div> <br>
</div>
-----Original Message-----<br>
From: drew einhorn <drew.einhorn@gmail.com><br>
To: Sugar List <Sugar@laptop.org><br>
Sent: Tue, 1 Jan 2008 12:34 pm<br>
Subject: [sugar] Sugar on conventional laptops and desktops<br>
<br>
<div id="AOLMsgPart_0_9e7c445d-ff36-4c38-be70-27ee13d5b9e1" style="margin: 0px; font-family: Tahoma,Verdana,Arial,Sans-Serif; font-size: 12px; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);">
<pre style="font-size: 9pt;"><tt>XO laptops are a scarce resource. Probably I should have dug<br>
deeper into my pocket for several hundred more dollars and<br>
bought a few more G1G1 laptops when I had the chance. But<br>
it's too late now.<br>
<br>
We have more folks who would like to participate in our learning<br>
community than we have XOs.<br>
<br>
There are several techniques for running sugar on desktops, but<br>
they are based on the needs of developers. They tend to result in<br>
stale bleeding versions of sugar and the activities. My guess is<br>
that there are many other folks in the G1G1 community, like me<br>
who need/want to run stable versions of sugar and the activities.<br>
Ship.2 or soon Update.1.<br>
<br>
This does match one use case for the LiveCD that is currently low<br>
on the official OLPC agenda.<br>
<br>
It is also possible to use this type of LiveCD to create a "virtual<br>
Sugar lab"<br>
for a school, where a traditional computer lab's computers are booted into<br>
a Sugar environment, storing their data on a networked or other storage<br>
device, without changing the lab's installed software.<br>
<br>
What is the best approach for the short term?<br>
<br>
Is there a Ship.2 LiveCD image. So far, all I have found are bleeding<br>
edge unstable images, or worse yet stale, bleeding edge images,<br>
all the instablility, and out of date, too.<br>
<br>
A long time ago, not long after PyCon 2007 I built sugar once on a Fedora<br>
Core N box using jbuild. I don't remember what N was. It was fragile and<br>
the activities were not yet useful. When I tried again, git retrieved newer,<br>
broken, bleeding edge versions of the dependencies from the head of the<br>
development trees, and I never got it working again. I assume this has<br>
gotten better since then, but I expect it will still be problematic getting a<br>
good version (for most G1G1 participants) using jhbuild.<br>
<br>
Stable Ship.2 or Update.1 images would be great. But as<br>
Matt Price points out getting the working VMware/QEMU, etc.<br>
infrastructure is a challenge that may be too much for most G1G1<br>
participants.<br>
<br>
Probably the best solution for G1G1 folks would be stable versions of<br>
packages from jani's personal archive matching Ship.2, Update.1, etc.<br>
It would be even better if there were .rpm versions of these<br>
repositories for folks not on debian based distributions.<br>
<br>
Before I put too much effort in finding my own solution to these problems,<br>
I need to be sure I'm not heading off in the wrong direction.<br>
<br>
-- <br>
Drew Einhorn<br>
_______________________________________________<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>
</tt></pre>
</div>
<!-- end of AOLMsgPart_0_9e7c445d-ff36-4c38-be70-27ee13d5b9e1 -->
<div class="AOLPromoFooter">
<hr style="margin-top:10px;" />
More new features than ever. Check out the new <a href="http://o.aolcdn.com/cdn.webmail.aol.com/mailtour/aol/en-us/text.htm?ncid=aolcmp00050000000003" target="_blank">AOL Mail</a>!<br/>
</div>