Lic. Edgar J. De Cleene wrote:
> Steven :
> 
> As you said thanks again, thanks again Pavel for leading in the right
> direction.

Indeed.

> What I wish is downsize more to MVC and rip another Mb, yesterday I study
> Pavel's image and try get back mvc related stuff, but as mvc project open I
> was unable to switch.
> 
> Any ideas ?

Interesting question. Short answer is, I will be surprised if you can 
gain a full MB from replacing Morphic w/ MVC in this particular image. 
Not that it's not possible, by all means go for it, but Morphic got a 
serious buzz cut in Pavel's image, and QuiteSmall took that even further.

If your only goal is getting the image as small as possible, you might 
look as some other possibilities (eg. stripping out networking, 
stripping out some unused kernel classes, removing the dependency 
between ChangeSets and ObjectWithDocumentation, etc).

If you do go for it, I hope you try to do it as a Monticello project. 
Say, a bunch of MVC-* system cats, and, when you 
override/rewrite/file-back-in methods in the Model hierarchy, put them 
in '*mvc-' method protocols. Then, go ahead and strip out Morphic brute 
force. Once you've got a clean MVC image that passes all the 
(appropriate) SUnit tests, we could compare the two images to see what 
the two images share, what they shouldn't, and what the *should* share 
and what they should not.

Even though nobody would confuse QuiteSmall with a kernel/core, if 
people create more items in the addon folder that can be loaded and 
unloaded from the QuiteSmall image, it might be helpful as a reference 
down the line for those more advanced/formal projects that will be 
"packagizing" Squeak. Put another way, even if MVC (or Etoys) were to be 
put back into QuiteSmall in a somewhat brute force fashion, it still 
might illuminate with a hazy light the relationship between MVC (or 
Etoys) and the rest of the image.