One tiny thing about the Package Loader access point as it it now - 

It currently asks the user two questions (Load SM? open a Loader?).
Assuming our main target is the newbie, I'd suggest to replace it with
one question, with three options - load SM and Loader (and open
one)/Just open a workspace or Scamper window on some SM get-started
documentation/nevermind.

Daniel

goran.hultgren at bluefish.se wrote:
> Doug Way <dway at riskmetrics.com> wrote:
> > 
> > On Sunday, November 24, 2002, at 08:57 AM, goran.hultgren at bluefish.se 
> > wrote:
> > 
> > > Stephane Ducasse <ducasse at iam.unibe.ch> wrote:
> > >> Hi scott
> > >>
> > >> I think that this is a really good initiative, if we could have
> > >> Squeak3.4 for christmax this would be great.
> > >> Then I hope that SqueakMap will be shipped with the **final** image.
> > >
> > > Eh, well, I will gladly make any and all jumps through hoops etc to make
> > > it look like SM is in the image ...
> > 
> > I think this is more or less already taken care of.  The "access point" 
> > to SqueakMap is the "Package Loader" item in the "open..." menu (which 
> > allows SqueakMap to be installed remotely the first time it is 
> > selected).  This is already in 3.4alpha and will be shipped with 
> > 3.4final, thus fulfilling Stephane's hopes.
> 
> Yes, I thought Stephane was aware of that so I read his posting as a
> request in favour of including the SM code in the image. And if he wants
> to include a CD with a book or something then he would need to cater for
> people being offline. But as I said - a bit of refinement of the
> bootstrap code (to look in local directory first for the SM base code)
> and then adding a bit of cache-smartness in SM then this would be simple
> to achieve.
> 
> > > but I still want it to be a package
> > > outside. Ok? This is essential - if I have any saying in this matter
> > > *the SqueakMap package will stay outside of the image!*
> > 
> > But the package itself is not in the image, so Goran stays happy, 
> > too. :-)  But the important point is that the access point is there in 
> > the UI, so it will be easily accessible to all in 3.4.
> 
> Right. Btw - this also means I should add a method for uninstalling SM
> so that it doesn't end up "accidentally" being included in the 3.4
> image! SM is easily uninstallable now - there are NO class extensions at
> all - simply remove the classes.
> 
> > - Doug Way
> 
> regards, Göran