Thanks Yoshiki.
I added a page based on your description:
http://confluence.immuexa.com/display/sq/Creating+Etoys+Release+for+Squeakla... to-go
linked from
http://confluence.immuexa.com/display/sq/Development
If you see something that needs to change or be added, go ahead, or let me know and I'd change
Milan
On July 18, 2009, Yoshiki Ohshima wrote:
At Sat, 18 Jul 2009 16:58:38 -0400,
Milan Zimmermann wrote:
My assumption is the steps prepare a Etoys image for Squeakland would be something like:
- download etoys 40 from http://tinlizzie.org/olpc/etoys-dev-4.0.zip
- unzip and open etoys-dev-4.0.image
- click the "load code updates" button
- in workspace, run ReleaseBuilderSqueakland new
prepareReleaseImageForSqueakland 5) save as etoys.image
It would be:
- fetch the SVN repository from svn.squeakland.org/installers.
- download etoys 40 from http://tinlizzie.org/olpc/etoys-dev-4.0.zip
- unzip and open etoys-dev-4.0.image
- set the Display size of the image to 800x600.
- Open a workspace and type:
ReleaseBuilderSqueakland new prepareReleaseImageForSqueakland. ReleaseBuilderSqueakland new buildInitialScreenForSqueakland.
(and accept the workspace)
- save that image to a safe place.
- copy the image and changes from above to Contents/Resources of Etoys.app or Etoys-To-Go.app and open the image.
- load code updates.
- Evaluate the code in the workspace.
- save as etoys.image
Whenever a new update is issued, you only need to repeat the cycle from 7) to 10).
Right now, Etoys.app and Etoys-To-Go.app are not exactly in sync (which it should). And to make a Windows installer, you execute: exportAssetsFromToGo.sh, and then open olpc.nsi with NSIS.
-- Yoshiki _______________________________________________ etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev