Hi Hilaire,
> On 16 Jun 2017, at 09:46, Hilaire wrote:
>
> Hi Esteban,
>
> Yes, good idea as this protocol is not present in Pharo6, it will ease
> loading Dr. Geo code.
>
> However it looks like there are faulty code in Pharo6 as there are
> exactly *four* senders to this message (see screen
Hi Esteban,
Yes, good idea as this protocol is not present in Pharo6, it will ease
loading Dr. Geo code.
However it looks like there are faulty code in Pharo6 as there are
exactly *four* senders to this message (see screenshot), and exactly
*zero* in DrGeo code, and *one* in the gettext package w
> On 16 Jun 2017, at 09:24, Sven Van Caekenberghe wrote:
>
> Here is how you can maintain compatibility:
>
> self environment
> at: #SessionManager
> ifPresent: [ :manager | manager default registerNetworkClassNamed: self name
> ]
> ifAbsent: [ Smalltalk addToStartUpList: self; addToShutD
Here is how you can maintain compatibility:
self environment
at: #SessionManager
ifPresent: [ :manager | manager default registerNetworkClassNamed: self name ]
ifAbsent: [ Smalltalk addToStartUpList: self; addToShutDownList: self ]
I use it for Zinc.
> On 16 Jun 2017, at 09:21, Esteban L
you can add that protocol by yourself as an extension.
you can create a package DrGeo-Pharo6
and add the method, something like:
addToStartUpList: aClass after: ignoredClass
SessionManager default
registerSystemClassNamed: aClass name
atPriority: 60
then
Hi,
When I install DrGeo from its configuration file in Pharo6, I got the
following VM error.
I guess the addStartUpList protocol is obsolete.
One option is to modify Dr. Geo code in Pharo3 to remove startup
activation, save in the repo, then load newer code in Pharo6, and get it
fixed.
Any sug
