Well that's the question.. Can i put a desired image of eToys in the OLPC and load it? I'm wondering this because i want to put an image with some packages loaded (i.e. NetMorph and it's dependences, wich i'm using in Windows) into the Sugar o.s. of an OLPC. I don't know if it is possible but i want to know because if i can't, i'm wasting my time working with images that will be unaccessables! Than you. Mauro
On Wednesday 10 June 2009 10:53:46 pm Mauro Esposito wrote:
Well that's the question.. Can i put a desired image of eToys in the OLPC and load it? I'm wondering this because i want to put an image with some packages loaded (i.e. NetMorph and it's dependences, wich i'm using in Windows) into the Sugar o.s. of an OLPC.
Wouldn't carry your own image(s) on a stick be a better option? etoys-image- and-pr.zip can be put on a memory stick. You will have to make sure to mount the stick with exec option and hack the etoys.sh launcher script.
If you are interested, I can mail the custom launcher and the minor hacks to get the stick going on Linux/Wintel/Mac.
Subbu
On 10.06.2009, at 19:23, Mauro Esposito wrote:
Well that's the question.. Can i put a desired image of eToys in the OLPC and load it? I'm wondering this because i want to put an image with some packages loaded (i.e. NetMorph and it's dependences, wich i'm using in Windows) into the Sugar o.s. of an OLPC. I don't know if it is possible but i want to know because if i can't, i'm wasting my time working with images that will be unaccessables
It is possible, in various ways. Who are your users?
One way is to simply launch the Squeak VM with your image from the Terminal activity's command line:
http://activities.sugarlabs.org/en-US/sugar/addon/4043
A more comfortable way for users is to build an activity bundle. You can take a look at the Scratch bundle, which packs a Squeak image, too. With this, users can simply launch your image like any other Sugar activity by clicking on an icon:
http://wiki.sugarlabs.org/go/Development_Team/Almanac/Activity_Bundles
The most comfortable way for users (and hardest for you as developer) would be to build the XO bundle but add Sugar support code to your image, the way Etoys does. This lets you integrate with all the Sugar services, like the Journal and collaboration support. Also you could add a UI that fits better with the rest of Sugar (like the toolbar in Etoys).
HTH,
- Bert -
etoys-dev@lists.squeakfoundation.org