On Sun, Jan 27, 2013 at 06:34:46PM -0500, Jim Rosenberg wrote:
> I have some projects that I'm working on moving from Squeak 3.8 to Squeak 
> 4.3. Squeak 4.3 won't load projects saved under 3.8 without conversion. To 
> bypass having to learn how to do that, I've been "capturing" all the 
> objects for each 3.8 project as submorphs of a single morph, saving that 
> morph to file, and loading it into a new project in 4.3. This seems to work 
> fine. The 3.8 .morph files load into 4.3 with no "adventures", and things 
> work great in 4.3, identical behavior, no problems.
> 
> Except for this: it is ballooning my .image size, and I would like to try 
> to get a handle on this. Just porting a family of 12 projects is giving me 
> an image size of 106M; this is for an artistic work that was originally 
> realized in Hypercard and fit with room to spare on a 1.4M floppy disk! The 
> .image for just this one work is bigger than my development 3.8 .image that 
> has "everything", so something is getting exploded in size by saving a 
> morph under 3.8 and then loading it under 4.3.
> 
> Is there a way to profile an image to find out where all that disk space is 
> going?

Have a look at SpaceTally. The class comment gives some tips on how to use it.
I'm not sure what the problem is, but the SpaceTally took may help you to
find it.

It's nice to know that you are having success in moving your work from 3.8
to 4.3. People sometime question whether it is worthwhile to put effort into
backward compatibility - this is one of the reasons that it is important :-)

Dave