Can you explain how this worked once the FileSystem-Git package
was loaded into a different environment? If I understand correctly,
you would have the ST-80 class named 'Path' in the default Smalltalk
environment, and you would also have the FileSystem class named
'Path' in a different environment.

To start making use of FileSystem-Git in the different environment,
is it simply a matter of changing the current environment from
Smalltalk to the different environment? And/or is there some mechanism
for explicitly specifying which of the two 'Path' classes is being
referenced?

Sorry if this is a repeat question, I am quite sure that you have
explained this previously but I am (obviously) a bit confused.

Thanks,
Dave


On Fri, Dec 20, 2019 at 04:07:31PM +0100, Jakob Reschke wrote:
> Hi,
> 
> I loaded FileSystem-Git in a different environment where the FileSystem
> classes for Squeak were named like they are in Pharo (without the FS
> prefix, which was especially troublesome for the class "Path").
> 
> Environments don't take away the effort of adapting the interface (messages
> sent and methods) though.
> 
> Kind regards,
> Jakob
> 
> 
> Am Fr., 20. Dez. 2019 um 15:06 Uhr schrieb Marcel Taeumel <
> marcel.taeumel at hpi.de>:
> 
> > If I recall correctly, Jakob (jr) could successfully load a second
> > FileDirectory implementation into Squeak using the environments. Maybe he
> > can help out?
> >
> > Best,
> > Marcel
> >
> > Am 19.12.2019 21:52:37 schrieb tim Rowledge <tim at rowledge.org>:
> >
> >
> > > On 2019-12-19, at 6:50 AM, Marcel Taeumel wrote:
> > >
> > > > ... lots of differently named classes ...
> > >
> > > So, you can try out Squeak's environments for that? :-)
> > If I had ever read anything that appeared to explain them and the tools to
> > use them without going insane, I might try. Personally I think it unlikely
> > to work. Happy to be shown evidence to the contrary.
> >
> >
> > tim