[majoredShrinked Image] ProcessBrowser walk-back on open
JArchibald at aol.com
JArchibald at aol.com
Sun Mar 4 11:32:20 UTC 2001
=> Sun, 4 Mar 2001 04:48:50 -0500 "Phiho Hoang" <phiho.hoang at home.com> =>
<< I just filed in 'ProcessBrowser' (filed out from Squeak3.0.image) into my
shrinked image. >>
=> 3/4/01 6:07:34 AM EST, arning at charm.net =>
<< I don't want to discourage you from doing something that you may be
enjoying, but I hope you understand that you are likely to encounter these
sorts of difficulties a lot. When you do a #majorShrink, it really is *major*
>>
PhiHo,
To second what Bob said, Major Shrink is *major*. And to second what I said
earlier, one must have a clear objective of the end result in mind to
usefully create a shrunken image. #majorShrink is principally a delivery
device, intended in its current form to produce compact systems for one
reason or another.
Now I can accept that one reason for a compact system is pedagogical; i.e.,
to produce a very small, tidy system which serves as an examplar for learning
Squeak (or Smalltalk, or whatever). But repeating a bit of my previous
submissions to this Mailing List, I would suggest the right way to do this is
to proceed to develop a clear idea of what one wants to do (what one wants to
have in such a system) using the full Squeak image. After having done that,
then one can produce a shrunken image to fit those characteristics with a
tolerable amount of pain.
Again, as I said previously, I do think of this as a rather brave effort.
Nonetheless, don't hesitate to ask what you need of this group if you decide
to persist. However, on the road you are on, you are going to get a
succession of errors described by walk-backs all of which point back to some
method (or class) that is missing. That is one of the FEATURES of
majorShrink; that's what it's suppose to do.
Good luck,
Jerry.
____________________________
Jerry L. Archibald
systemObjectivesIncorporated
____________________________
More information about the Squeak-dev
mailing list
|