This should not be necessary with the newly modularized Squeak 3.3. This
filtration will be the natural result of creating the 'base image' in the
'moduled' Squeak. The real question is how do you reasonably go about
describing entire subsystems that are not part of the base image.

Jim

>
> But I was also hinting (per Andreas' comment) that a simple
> filtration of the existing classes down to some 100 or so probably
> won't quite do it -- and will thus require a few new classes that
> provide more consolidated and powerful abstractions. Also, the Etoys
> part of the system has some good hints about simpler and more
> powerful object models for early users.
>
> Cheers,
>
> Alan
>