About ExternalDropHandler initialize

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

About ExternalDropHandler initialize

stephane ducasse
Hi guys

registerStandardExternalDropHandlers is not invoked from the class initialize and I was wondering if
one of you know why.
Right now we have:

ExternalDropHandler class >> initialize
        "ExternalDropHandler initialize"

        self resetRegisteredHandlers.
        self
                registerHandler: self defaultImageHandler;
                registerHandler: self defaultGZipHandler.
       
This is the same in Squeak
_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: About ExternalDropHandler initialize

Gary Chambers-4
I guess the registerHandler: bits should move to
registerStandardExternalDropHandlers.
Even after cleanUp you'd want them, I think.

Most of the users of ExternalDropHandler actually call the initialize
instead of cleanUp for doing clean up...

Regards, Gary

----- Original Message -----
From: "stephane ducasse" <[hidden email]>
To: "Pharo Development" <[hidden email]>
Sent: Tuesday, March 09, 2010 4:55 PM
Subject: [Pharo-project] About ExternalDropHandler initialize


> Hi guys
>
> registerStandardExternalDropHandlers is not invoked from the class
> initialize and I was wondering if
> one of you know why.
> Right now we have:
>
> ExternalDropHandler class >> initialize
> "ExternalDropHandler initialize"
>
> self resetRegisteredHandlers.
> self
> registerHandler: self defaultImageHandler;
> registerHandler: self defaultGZipHandler.
>
> This is the same in Squeak
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project 


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: About ExternalDropHandler initialize

Stéphane Ducasse
Yes it was my impression too.

Stef

On Mar 9, 2010, at 6:19 PM, Gary Chambers wrote:

> I guess the registerHandler: bits should move to registerStandardExternalDropHandlers.
> Even after cleanUp you'd want them, I think.
>
> Most of the users of ExternalDropHandler actually call the initialize instead of cleanUp for doing clean up...
>
> Regards, Gary
>
> ----- Original Message ----- From: "stephane ducasse" <[hidden email]>
> To: "Pharo Development" <[hidden email]>
> Sent: Tuesday, March 09, 2010 4:55 PM
> Subject: [Pharo-project] About ExternalDropHandler initialize
>
>
>> Hi guys
>>
>> registerStandardExternalDropHandlers is not invoked from the class initialize and I was wondering if
>> one of you know why.
>> Right now we have:
>>
>> ExternalDropHandler class >> initialize
>> "ExternalDropHandler initialize"
>>
>> self resetRegisteredHandlers.
>> self
>> registerHandler: self defaultImageHandler;
>> registerHandler: self defaultGZipHandler.
>>
>> This is the same in Squeak
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project 
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project