On Jul 16, 2009, at 9:25 PM, jira@immuexa.com wrote:
[ http://tracker.immuexa.com/browse/SQ-154?page=comments#action_35752]
Milan Zimmerman commented on SQ-154:
This makes sense. I am out of time now, but will test tomorrow or early weekend.
Thank you, Milan!
By mutual agreement among Bert, Yoshiki, and me, we decided to push the latest fixes embodied in SQ-88, SQ-154, and SQ-257 to the etoys4.0 update stream today. This will make it easier for more people to test, and we still have time before squeakfest/brasil to fix any issues that may arise.
Cheers,
-- Scott
Thanks Scott.
I tested the latest, looks great, I had one problem but realized it was my misunderstanding, as I did not fully apply the intended release preparation steps.
As a result, I have a question: What is the list of steps I need to run to prepare a Etoys image for Squeakland (and for OLPC) release, starting from image at http://tinlizzie.org/olpc/etoys-dev-4.0.zip. If someone can attach it here or email me I will put it on the squeakland wiki- thanks.
I think to describe this is important for testers who would test things like the navigator bar show/hide, scaling and other global things (I am afraid I tripped over missing a step when testing SQ-154 :( so also asked there).
My assumption is the steps prepare a Etoys image for Squeakland would be something like:
1) download etoys 40 from http://tinlizzie.org/olpc/etoys-dev-4.0.zip 2) unzip and open etoys-dev-4.0.image 3) click the "load code updates" button 4) in workspace, run ReleaseBuilderSqueakland new prepareReleaseImageForSqueakland 5) save as etoys.image
but I am (especially) not sure about step 4 - is that the right utility? Also, before running any of the steps, do I need to set the Etoys window to a specific size or just use the default?
Thanks, Milan
PS also, where does OLPC image preparation differ... thanks
On July 17, 2009, Scott Wallace wrote:
On Jul 16, 2009, at 9:25 PM, jira@immuexa.com wrote:
[ http://tracker.immuexa.com/browse/SQ-154?page=comments#action_35752]
Milan Zimmerman commented on SQ-154:
This makes sense. I am out of time now, but will test tomorrow or early weekend.
Thank you, Milan!
By mutual agreement among Bert, Yoshiki, and me, we decided to push the latest fixes embodied in SQ-88, SQ-154, and SQ-257 to the etoys4.0 update stream today. This will make it easier for more people to test, and we still have time before squeakfest/brasil to fix any issues that may arise.
Cheers,
-- Scott
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:
1) fetch the SVN repository from svn.squeakland.org/installers. 2) download etoys 40 from http://tinlizzie.org/olpc/etoys-dev-4.0.zip 3) unzip and open etoys-dev-4.0.image 4) set the Display size of the image to 800x600. 5) Open a workspace and type:
ReleaseBuilderSqueakland new prepareReleaseImageForSqueakland. ReleaseBuilderSqueakland new buildInitialScreenForSqueakland.
(and accept the workspace)
6) save that image to a safe place. 7) copy the image and changes from above to Contents/Resources of Etoys.app or Etoys-To-Go.app and open the image. 8) load code updates. 9) Evaluate the code in the workspace. 10) 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
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
I tried to follow Yoshiki's description, but failed to build an etoys image. It might be good to fix the description like:
- Use laptop.org repository instead of installer's to test with the latest example projects.
- Make sure to run ReleaseBuilderSqueakland after moving the image next to the example projects.
1) fetch the SVN repository from svn+ssh://dev.laptop.org/var/www/etoys/svn/trunk/etoys or http://etoys.laptop.org/svn/trunk/etoys 2) download etoys 40 from http://tinlizzie.org/olpc/etoys-dev-4.0.zip 3) unzip and open etoys-dev-4.0.image 4) set the Display size of the image to 800x600. 5) save that image to a safe place. 6) copy the image and changes to the directory where Gallery.*.pr is in the svn tree (Content/). 7) load code updates. 8) Open a workspace and type: ReleaseBuilderSqueakland new prepareReleaseImageForSqueakland. ReleaseBuilderSqueakland new buildInitialScreenForSqueakland. highlight the 2 lines above and perform do it (Alt-d) 9) save as etoys.image (open the desktop menu by Shift + Alt + w)
Above all, we wouldn't need 4) 5) 7) 8) if etoys-dev-4.0.image is prepared as 800x600 and it has a workspace with necessary expression to do it. I uploaded my etoys-dev-4.0.zip here. http://tinlizzie.org/~takashi/etoys-dev-4.0.zip
Cheers, - Takashi
On Sat, Jul 18, 2009 at 11:17 PM, Milan Zimmermannmilan.zimmermann@sympatico.ca wrote:
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:
1) fetch the SVN repository from svn.squeakland.org/installers. 2) download etoys 40 from http://tinlizzie.org/olpc/etoys-dev-4.0.zip 3) unzip and open etoys-dev-4.0.image 4) set the Display size of the image to 800x600. 5) Open a workspace and type:
ReleaseBuilderSqueakland new prepareReleaseImageForSqueakland. ReleaseBuilderSqueakland new buildInitialScreenForSqueakland.
(and accept the workspace)
6) save that image to a safe place. 7) copy the image and changes from above to Contents/Resources of Etoys.app or Etoys-To-Go.app and open the image. 8) load code updates. 9) Evaluate the code in the workspace. 10) 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
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
At Tue, 21 Jul 2009 11:23:27 -0700, Takashi Yamamiya wrote:
I tried to follow Yoshiki's description, but failed to build an etoys image. It might be good to fix the description like:
But can you tell me where it failed?
I can't check now but wonder if the one at laptop.org is really up to date. Does it have the auotmatic version displaying in the about flap>
It would be nice if it has got a different name...
-- Yoshiki
Yoshiki Ohshima wrote:
At Tue, 21 Jul 2009 11:23:27 -0700, Takashi Yamamiya wrote:
I tried to follow Yoshiki's description, but failed to build an etoys image. It might be good to fix the description like:
But can you tell me where it failed?
I misunderstood as if ReleaseBuilderSqueakland is run before copying to the project directory. And The DemonCastle project was not the latest because of installer svn.
I must say that this description is too difficult to a beginner like me. That's why I made up my etoys-dev-4.0.image.
I can't check now but wonder if the one at laptop.org is really up to date. Does it have the auotmatic version displaying in the about flap>
The answer is yes. But, I thought laptop.org is the master place for projects. Is there any case where installer repository is newer than laptop.org?
It would be nice if it has got a different name...
I don't mind to change the name. Any suggestions?
Cheers, - Takahsi
At Wed, 22 Jul 2009 11:36:59 -0700, Takashi Yamamiya wrote:
I must say that this description is too difficult to a beginner like me. That's why I made up my etoys-dev-4.0.image.
Heh, as you know, even in Japan, "too humble" can be taken wrongly especially when people know you did more work than I did.
I can't check now but wonder if the one at laptop.org is really up to date. Does it have the auotmatic version displaying in the about flap>
The answer is yes. But, I thought laptop.org is the master place for projects. Is there any case where installer repository is newer than laptop.org?
It is out of sync for now. We need to synchronize and make up a good policy. Many of us happen to be face to face for sometime, hopefully that would give us a time to go through it.
It would be nice if it has got a different name...
I don't mind to change the name. Any suggestions?
We could upload it to the svn repository(ies) at the right directory, I think.
-- Yoshiki
Thanks for testing it Takashi,
If you managed to run the build, please feel free to update the instructions based on your experience. If noone does it, I will get to it :) - but probably next weekend at the earliest...
Milan
On July 21, 2009, Takashi Yamamiya wrote:
I tried to follow Yoshiki's description, but failed to build an etoys image. It might be good to fix the description like:
Use laptop.org repository instead of installer's to test with the latest example projects.
Make sure to run ReleaseBuilderSqueakland after moving the image next to the example projects.
- fetch the SVN repository from svn+ssh://dev.laptop.org/var/www/etoys/svn/trunk/etoys or http://etoys.laptop.org/svn/trunk/etoys
- 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.
- save that image to a safe place.
- copy the image and changes to the directory where Gallery.*.pr is in the svn tree (Content/).
- load code updates.
- Open a workspace and type:
ReleaseBuilderSqueakland new prepareReleaseImageForSqueakland. ReleaseBuilderSqueakland new buildInitialScreenForSqueakland. highlight the 2 lines above and perform do it (Alt-d) 9) save as etoys.image (open the desktop menu by Shift + Alt + w)
Above all, we wouldn't need 4) 5) 7) 8) if etoys-dev-4.0.image is prepared as 800x600 and it has a workspace with necessary expression to do it. I uploaded my etoys-dev-4.0.zip here. http://tinlizzie.org/~takashi/etoys-dev-4.0.zip
Cheers,
- Takashi
On Sat, Jul 18, 2009 at 11:17 PM, Milan
Zimmermannmilan.zimmermann@sympatico.ca wrote:
Thanks Yoshiki.
I added a page based on your description:
http://confluence.immuexa.com/display/sq/Creating+Etoys+Release+for+Squea kland%2C+OLPC%2C+or+Etoys- 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
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
Hi :
I finally got back to this.
I tried to follow instructions below how to make a Squeakland release but failed to understand several points. I modified the original text created by Yoshiki thinking I will add details but probably just added confusion. In any case i was unable to understan what to do start to end.
http://wiki.squeakland.org/display/sq/Creating+Etoys+Release+for+Squeakland%... to-go
Would someone who knows this process have time to clarify this page at some point, and add answers to the TODO's etc?
Thanks!
Milan
On July 28, 2009, Milan Zimmermann wrote:
Thanks for testing it Takashi,
If you managed to run the build, please feel free to update the instructions based on your experience. If noone does it, I will get to it :) - but probably next weekend at the earliest...
Milan
On July 21, 2009, Takashi Yamamiya wrote:
I tried to follow Yoshiki's description, but failed to build an etoys image. It might be good to fix the description like:
Use laptop.org repository instead of installer's to test with the latest example projects.
Make sure to run ReleaseBuilderSqueakland after moving the image next to the example projects.
- fetch the SVN repository from svn+ssh://dev.laptop.org/var/www/etoys/svn/trunk/etoys or http://etoys.laptop.org/svn/trunk/etoys
- 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.
- save that image to a safe place.
- copy the image and changes to the directory where Gallery.*.pr is in the svn tree (Content/).
- load code updates.
- Open a workspace and type:
ReleaseBuilderSqueakland new prepareReleaseImageForSqueakland. ReleaseBuilderSqueakland new buildInitialScreenForSqueakland. highlight the 2 lines above and perform do it (Alt-d) 9) save as etoys.image (open the desktop menu by Shift + Alt + w)
Above all, we wouldn't need 4) 5) 7) 8) if etoys-dev-4.0.image is prepared as 800x600 and it has a workspace with necessary expression to do it. I uploaded my etoys-dev-4.0.zip here. http://tinlizzie.org/~takashi/etoys-dev-4.0.zip
Cheers,
- Takashi
On Sat, Jul 18, 2009 at 11:17 PM, Milan
Zimmermannmilan.zimmermann@sympatico.ca wrote:
Thanks Yoshiki.
I added a page based on your description:
http://confluence.immuexa.com/display/sq/Creating+Etoys+Release+for+Squ ea kland%2C+OLPC%2C+or+Etoys- 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 2) unzip and open etoys-dev-4.0.image 3) click the "load code updates" button 4) 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 3) unzip and open etoys-dev-4.0.image 4) set the Display size of the image to 800x600. 5) 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
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
On 21.12.2009, at 00:04, Milan Zimmermann wrote:
Hi :
I finally got back to this.
I tried to follow instructions below how to make a Squeakland release but failed to understand several points. I modified the original text created by Yoshiki thinking I will add details but probably just added confusion. In any case i was unable to understan what to do start to end.
http://wiki.squeakland.org/display/sq/Creating+Etoys+Release+for+Squeakland%...
Would someone who knows this process have time to clarify this page at some point, and add answers to the TODO's etc?
Thanks!
Milan
Just a few data points:
The 4.0 dev image at etoys.laptop.org is identical to the original tinlizzie one except it has been saved at 800x600 pixels and Pango was disabled. See
svn log http://etoys.laptop.org/svn/trunk/etoys/etoys-dev.image
I made the Sugar release image from that dev image by running these scripts in Linux:
http://etoys.laptop.org/svn/trunk/etoys/mkRelease.sh http://etoys.laptop.org/svn/trunk/etoys/mkRelease.st
(though for the 4.0.2339 release I cheated and re-saved the release image while running in a 1200x900 Sugar emulator [being careful to first enter the empty top project] so that on startup on the XO the menu bar does not have to be rebuild)
The Mac release and To-Go release I built on a Mac using the scripts that formerly resided at
http://svn.squeakland.org/installers/
There was buildImage.sh / buildImage.st that updated the image, and makeEtoysMac / makeEtoysToGo to create the app bundles. I ran the setVersion script between building the image and bundling the app to adjust the version numbers while avoiding manual errors when it was getting late.
- Bert -
On Sunday 19 Jul 2009 7:53:51 am Yoshiki Ohshima wrote:
- save that image to a safe place.
Suggest grabbing buttons for some important or Preferences like etoyFriendly, simpleMenus, debugHaloHandle, biggerCursors etc before saving. It would be nice if new preference buttons are placed in the World in the reference dev image itself.
- 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
Just a note of caution. In step 8/9, if any updates modify the current changeset, exportSegmentFileName:directory:withOutInteraction: will get copy these into every project saved from this image :-(. Of course, there is a prompt but children cannot comprehend this message and may choose the option which saves the changeset.
Suggest a 9.5) Ensure that the current changset is empty. If not, rename it and create a new empty change set named 'unnamed'. We could gather all these into ReleaseBuilder as buildFinalImageNamed:andQuit:
Subbu
Thanks Subbu.
Unless someone beats me to it, I will update the page (but feel free to go ahead) .. but I need to first gather a long afternoon or two where I can try to follow the instructions first to know what is hapenning and how to improve.
Milan
On July 22, 2009, K. K. Subramaniam wrote:
On Sunday 19 Jul 2009 7:53:51 am Yoshiki Ohshima wrote:
- save that image to a safe place.
Suggest grabbing buttons for some important or Preferences like etoyFriendly, simpleMenus, debugHaloHandle, biggerCursors etc before saving. It would be nice if new preference buttons are placed in the World in the reference dev image itself.
- 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
Just a note of caution. In step 8/9, if any updates modify the current changeset, exportSegmentFileName:directory:withOutInteraction: will get copy these into every project saved from this image :-(. Of course, there is a prompt but children cannot comprehend this message and may choose the option which saves the changeset.
Suggest a 9.5) Ensure that the current changset is empty. If not, rename it and create a new empty change set named 'unnamed'. We could gather all these into ReleaseBuilder as buildFinalImageNamed:andQuit:
Subbu
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
On Tuesday 28 Jul 2009 9:37:58 am Milan Zimmermann wrote:
Unless someone beats me to it, I will update the page (but feel free to go ahead)
Done. http://tracker.squeakland.org/browse/SQ-154#action_35982
I thought of adding a few lines about distributing custom galleries but the note is already long.
Should this go into a wiki page after a thorough review?
Subbu
etoys-dev@lists.squeakfoundation.org
-
Bert Freudenberg -
K. K. Subramaniam -
Milan Zimmermann -
Scott Wallace -
Takashi Yamamiya -
Yoshiki Ohshima