Hi,

I had sprinkled menu items around some tools (like the MCSnapshotBrowser)
that were labelled something like "Load into other environment...", which
would prompt you for the environment, then make it the "Environment
current" during the loading. I have lost track though how many of these I
have submitted to the Inbox or how many have been merged in Trunk and which
were not.

One of these menu items is "change environment..." on a package in the
Monticello Browser. It would change the environment of an MCWorkingCopy for
future snapshots and loads.

Also all my modifications kept Environments out of the package definitions.
In terms of Tony's experiment: you would need your special environment with
doesNotUnderstand: already set up, then make it the "Environment current"
while you load the package in order to get it back as Tony had intended it
to be. For example, create the (empty) package in the Monticello browser,
then "change environment" of it to your special environment, then load the
package from a repository. If you would not do this and load as usual
instead, it would load into Smalltalk globals instead, regardless of how
Tony had saved it.

Kind regards,
Jakob

Am Do., 25. März 2021 um 19:10 Uhr schrieb Tobias Pape <Das.Linux at gmx.de>:

> HI
>
>
> > On 25. Mar 2021, at 19:09, Tony Garnock-Jones <tonyg at leastfixedpoint.com>
> wrote:
> >
> > On 3/25/21 6:20 PM, Vanessa Freudenberg wrote:
> >> Your PI subclass just needs to answer what classes and methods are
> considered to be in your package. What else do you need?
> >
> > They need to be attached to the correct Environment on load, too. So the
> package needs to know something about Environments other than Environment
> current.
>
> I think Jakob had a bit more tooling, no?
>
> BEst
>         -Tobias
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20210325/9c7a9408/attachment.html>