On 29/01/21 2:54 pm, Marcel Taeumel wrote:
> 
> Morph >> #player in "Morphic-Kernel" / "accessing"
> BookMorph >> #goto: in "MorphicExtras-Books" / "navigation"
> HandMorph >> #pasteMorph in "Morphic-Kernel" / "paste buffer"
> Morph >> #isTileMorph in "Morphic-Kernel" / "classification"
> HaloMorph >> #addTileHandle: in "Morphic-Widgets" / "handles"

IIRC, Etoys was an experiment in visual programming for children too 
young to program via text but made fairly (hindsight!) intrusive changes 
to Morphic. Etoys was organically bound into Squeak; like conjoint twins.

But that was then and this is now. Instead of shooting for a reloadable 
Etoys, what if the next Squeak release makes a clean break from Etoys?

I propose that we slim down Squeak by removing all Etoys-related code by 
without trying to ensure that existing Etoys package successfully loads 
back into the image. This will slim down Squeak significantly and ease 
its maintenance.

The largest user base for Etoys was on XO laptop. Those users are 
unlikely to upgrade to new Squeak. Also, porting Etoys package to load 
into slimmer Squeak may be an easier and better way to continue research 
than striving to maintain both in the released image.

Regards .. Subbu