Hi, I don't think my experience is really usable for general image shrinking. What I was doing is preparing images to run on the iPhone, and then I was cutting a lot of things needed in any other scenarios. In fact, I named my "technic" as "brute shrinking" :P and what I was using was an adaptation of Pavel's experiments:
1) I run all the cleans provided on Pharo. 2) I change the morphic UI with a dummy one. 3) I remove lots of packages using package unloader (and I said: lots... any package I'm not using). 4) I remove lots of classes (again, any clearly not-used class remaining in not unloaded packages) 5) I remove lots of methods (using Pavel's listing, here) 6) finally I was removing even InputEventFetcher, etc. (no need for a iOS user interface, I'm processing the events in "other way") with all this, my smallest image were about 4.1M... and it was working properly inside an iPhone :) as you can see... it doesn't look like it is useful for real non-mars scenarios... I can provide the scripts, of course, if you still think it is useful. and I thought on reorganize, taking into account all this drops, yes... but the experiments were aborted by the apple clause change... now solved, but no time to continue the work on it yet :) Cheers, Esteban El 05/01/2011, a las 4:58a.m., Adrian Lienhard escribió: > > On Jan 4, 2011, at 22:42 , Mariano Martinez Peck wrote: > >> ps: I wonder if any of those scripts should be added to ScriptLoader > > Yes, that would be good! Like this we can improve them and other people can > contribute. > > Esteban, could you share your experience with unloading packages? I assume > you had to also reorganize packages to make them cleanly unloadable? If yes > these changes should be integrated to improve the modularization. > > Cheers, > Adrian
