[etoys-dev] Re: Merging Etoys

Bert Freudenberg bert at freudenbergs.de
Sat Feb 20 06:26:30 EST 2010

On 20.02.2010, at 12:17, Bert Freudenberg wrote:
> On 20.02.2010, at 08:36, K. K. Subramaniam wrote:
>> On Friday 19 February 2010 06:30:07 pm karl ramberg wrote:
>>> On Fri, Feb 19, 2010 at 1:37 PM, K. K. Subramaniam <subbukk at gmail.com> 
>> wrote:
>>>> I get stuck in Step A. Where does one draw the boundary between Morphic
>>>> and Etoys? Does one have to start from scratch or is there a partially
>>>> excised version somewhere?
>> ..
>>> Etoys is a seperate package in trunk image that can be unloaded, btw
>> I can unload Etoys from the trunk image, but is there a reference repository 
>> for Etoys for loading it all back?
> You are confusing two things. One is the Etoys image which is what you download from squeakland. The other is the Etoys package in trunk. Those have almost nothing to do with each other as I tried to explain previously.
>> Will the loadable Etoys be hosted in source.squeak.org or in etoys.laptop.org?
> Not laptop.org for sure. Somewhere on squeak.org would be best IMHO. Previously we wanted to host it on squeakland but I spoke to Tim and he agreed that squeak.org might be a good idea.
> If we go the Monticello route instead of continuing with changesets in an update stream then I think making an Etoys project at source.squeak.org is our best option. Is that what we want?

Sent to soon.

What I meant to add is that this Etoys repo would hold *all* code currently in the Etoys image, just as the trunk repo holds all code in the trunk image. Ideally we'd add a configuration-based update mechanism just as in trunk so that we can easily load updates by pushing a button. Does that make the idea more clear?

- Bert -

More information about the etoys-dev mailing list