Sweet! 'Till All Are One!<div><br></div><div>I'm installing Etoys 4 on my itsy-bitsy laptop. In spite of the fact that I think Etoys is really a great thing, I've not acquainted myself with it, as I was already splitting my time between Squeak and Pharo (I've hardly had a spare moment to look at VW!)</div>
<div><br></div><div>Now that there's an easy way to see the diffs, I'm kind of interested to see what the delta is.<br><br><div class="gmail_quote">On Fri, Apr 30, 2010 at 2:20 AM, Bert Freudenberg <span dir="ltr"><<a href="mailto:bert@freudenbergs.de">bert@freudenbergs.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On 30.04.2010, at 10:42, Hannes Hirzel wrote:<br>
><br>
> I have downloaded the image. I like the many example projects which<br>
> come with it.<br>
<br>
</div>Hehe, and that's not even the *real* interface. To see that, from the world menu, choose "new morph...", "make link to project...", "Home". This creates a button that takes you to the home screen (I forgot to put one into the dev image, sorry).<br>
<br>
Of course, if you download the non-developer version from<br>
<a href="http://squeakland.org/download/" target="_blank">http://squeakland.org/download/</a><br>
it will start with the right screen.<br>
<div class="im"><br>
> To be sure: this now means that Etoys is no longer a "fork" of Squeak<br>
> anymore but an "application" running on top of 4.1?<br>
<br>
</div>Not yet. It's a first step towards that, enabling the same tools to be used.<br>
<br>
This is pretty much equivalent to the 2009 Etoys 4.0 release (the release number similarity to Squeak is coincidental). It is still closer to Squeak 3.8 (when we last cross-merged) than Squeak 4.1. If you compare the packages to e.g. trunk, you will see huge differences.<br>
<br>
"Etoys 4.1" is the tentative label for the Etoys Summer 2010 release, we have not yet decided what to actually call it.<br>
<font color="#888888"><br>
- Bert -<br>
</font><div><div></div><div class="h5"><br>
> --Hannes<br>
><br>
> On 4/30/10, karl ramberg <<a href="mailto:karlramberg@gmail.com">karlramberg@gmail.com</a>> wrote:<br>
>> On Thu, Apr 29, 2010 at 11:05 PM, Bert Freudenberg<br>
>> <<a href="mailto:bert@freudenbergs.de">bert@freudenbergs.de</a>>wrote:<br>
>><br>
>>> On 26.04.2010, at 04:56, Bert Freudenberg wrote:<br>
>>>><br>
>>>> On 19.04.2010, at 13:52, Bert Freudenberg wrote:<br>
>>>>><br>
>>>>> Hi folks,<br>
>>>>><br>
>>>>> as we discussed lately we want to enable easier contributions,<br>
>>>>> following<br>
>>> a model similar to Squeak's "trunk". I spent the weekend making the latest<br>
>>> tools from Squeak work in the Etoys image. I did not push it to the update<br>
>>> stream yet, but it is attached. Let's discuss in the developer meeting on<br>
>>> IRC later today.<br>
>>>>><br>
>>>>> Here is how to test it:<br>
>>>>><br>
>>>>> * Download Etoys-To-Go4-Final.zip from <a href="http://squeakland.org" target="_blank">squeakland.org</a> and unzip and run<br>
>>>>> * get halo for world, choose "preferences..." from halo menu<br>
>>>>> * disable "eToyFriendly" in the "scripting category"<br>
>>>>> * click the gray World background, choose "previous project" from the<br>
>>> World menu<br>
>>>>> * you'll be taken to the hidden top-level project, light-blue<br>
>>>>> background<br>
>>>>> * now is a good time to save the image (not save-as)<br>
>>>>><br>
>>>>> This will result in an image ready for development work. I'm suggesting<br>
>>> to use Etoys-To-Go because it is self-contained and allows to save the<br>
>>> image<br>
>>> easily. The regular install is read-only.<br>
>>>>><br>
>>>>> Now for my stuff ...<br>
>>>><br>
>>>> ... which I just pushed to the new 4.1 update stream at <a href="http://etoys.squeak.org" target="_blank">etoys.squeak.org</a><br>
>>>><br>
>>>> * Evaluate this in a workspace to set the new update server (you need at<br>
>>> least a 4.0.2336 image):<br>
>>>> HTTPSocket httpFileInNewChangeSet: '<br>
>>> <a href="http://etoys.squeak.org/updates/newUpdateStream-bf.cs" target="_blank">etoys.squeak.org/updates/newUpdateStream-bf.cs</a>'<br>
>>>> * Then load updates. This will ask if you want to advance to 4.1, say<br>
>>> yes. Load updates again<br>
>>>> * This will take quite a while ...<br>
>>>> * ... but eventually you should have an image with Monticello loaded :)<br>
>>>><br>
>>>> Heres a log of the changes:<br>
>>>> <a href="http://squeakland.org/updates/" target="_blank">http://squeakland.org/updates/</a><br>
>>>><br>
>>>> This includes the recategorization from trunk (huge 1 MB changeset) and<br>
>>> an edited version of Karl's recategorization, ending up in a quite<br>
>>> reasonable number of packages IMHO. Also, thanks to Eliot for porting the<br>
>>> compiler changes!<br>
>>>><br>
>>>> The next step should be to create proper packages and commit them to the<br>
>>> etoys repo.<br>
>>>> - Bert -<br>
>>><br>
>>> We did it :)<br>
>>><br>
>>> There is an initial version of all Monticello packages that now constitute<br>
>>> the Etoys image in our main repository at<br>
>>><br>
>>> <a href="http://source.squeak.org/etoys.html" target="_blank">http://source.squeak.org/etoys.html</a><br>
>>><br>
>>> If you load updates, it will first fetch changesets from the update<br>
>>> stream,<br>
>>> and then proceed to update packages from the repository. We will mostly<br>
>>> just<br>
>>> post new packages from now on. But if needed, we still have the update<br>
>>> stream.<br>
>>><br>
>>> To get an Etoys image for development, either follow the procedure I<br>
>>> outlined above (takes about 10 minutes here), or download an all-in-one<br>
>>> zip<br>
>>> (based on Etoys-To-Go) from here:<br>
>>><br>
>>> <a href="http://etoys.squeak.org/download/" target="_blank">http://etoys.squeak.org/download/</a><br>
>>><br>
>>> It's easier if you do not use save-as in this setup, only regular image<br>
>>> save. The image name is mentioned explicitly in the VM settings.<br>
>>><br>
>>> New versions can be submitted to the "Etoys Inbox" by *anyone*, no<br>
>>> registration required:<br>
>>><br>
>>> <a href="http://source.squeak.org/etoysinbox.html" target="_blank">http://source.squeak.org/etoysinbox.html</a><br>
>>><br>
>>> Of course, Etoys developers can commit to the main repository directly. If<br>
>>> you want to have access, register on that server, and ping me so I add you<br>
>>> to the right group.<br>
>>><br>
>>> We'll look at all contributions, though we need to be somewhat<br>
>>> conservative. Remember this is used by kids worldwide, it's deployed on<br>
>>> about a million machines, and more are to come [1]. Features are cool, but<br>
>>> don't make the kids cry, mkay? ;)<br>
>>><br>
>>> Btw, if someone feels more comfortable using changesets, don't worry, you<br>
>>> can still attach them to a ticket on our tracker at<br>
>>><br>
>>> <a href="http://tracker.squeakland.org/" target="_blank">http://tracker.squeakland.org/</a><br>
>>><br>
>>> Some other developer will then build Monticello packages and commit them.<br>
>>><br>
>>> So, the gates are open, let the contributions flow :)<br>
>>><br>
>>> - Bert -<br>
>>><br>
>>> [1]<br>
>>> <a href="http://www.earthtimes.org/articles/show/one-laptop-per-child-and,1271519.shtml" target="_blank">http://www.earthtimes.org/articles/show/one-laptop-per-child-and,1271519.shtml</a><br>
>>><br>
>>><br>
>>> Great !<br>
>><br>
>> Karl<br>
>><br>
><br>
<br>
<br>
<br>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Casey Ransberger<br>
</div>