- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Updated Polymorph

by StÃ©phane Ducasse

Ok I will integrate the changes later this evening On Jan 27, 2009, at 6:26 PM, Gary Chambers wrote: > Got annoyed with the PreferenceBrowser not fully tying in with > themes so > have reworked it a bit. > Interesting to see that less code is needed when utilising the theme > helper > methods. > Done as overrides for Squeak compatability, of course. Really need > to start > thinking of the base being Pharo with patches for Squeak though. ;) > > > Polymorph-Widgets-gvc.33 on SqueakSource. > > Regards, Gary. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 27, 2009

Re: [Pharo-project] Updated Polymorph

by Gary Chambers

Make that Polymorph-Widgets-gvc.34. Fixes a couple of bugs (like the button actions!). Regards, Gary. ----- Original Message ----- From: "Gary Chambers" <gazzaguru2(a)btinternet.com> To: "Pharo Development" <pharo-project(a)lists.gforge.inria.fr> Sent: Tuesday, January 27, 2009 5:26 PM Subject: [Pharo-project] Updated Polymorph > Got annoyed with the PreferenceBrowser not fully tying in with themes so > have reworked it a bit. > Interesting to see that less code is needed when utilising the theme > helper > methods. > Done as overrides for Squeak compatability, of course. Really need to > start > thinking of the base being Pharo with patches for Squeak though. > > Polymorph-Widgets-gvc.33 on SqueakSource. > > Regards, Gary. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 27, 2009

[Pharo-project] Updated Polymorph

by Gary Chambers

Got annoyed with the PreferenceBrowser not fully tying in with themes so have reworked it a bit. Interesting to see that less code is needed when utilising the theme helper methods. Done as overrides for Squeak compatability, of course. Really need to start thinking of the base being Pharo with patches for Squeak though. Polymorph-Widgets-gvc.33 on SqueakSource. Regards, Gary.

Jan. 27, 2009

Re: [Pharo-project] why #ifNotNil: accepts parameter?

by StÃ©phane Ducasse

On Jan 27, 2009, at 5:04 PM, Esteban Lorenzano wrote: > Very interesting stef, thanks a lot... > > but now, I'm not sure of what I did with OB-Tools (I just replace > ifNotNil: [ :blah | ... ] with ifNotNilDo: [ :blah | ... ]... I > understand why the first version of ifNotNil: is done like that in > pharo... but what I do with compatibility? will pharo still support > ifNotNilDo:? > And, I also agree with lukas. blahDo: is ugly, if you have an elegant > solution... but, what I have to do with OB-Tools? I replace methods > (like before) or better I create a package OB-Tools-Squeak with > extensions for Squeak? > > I know... this is hardly a "pharo issue", but maybe can provide pharo > developers of clues of what to do if they are trying to keep > compatibiity (I know, that's not a pharo goal -compatibility-, but > sometimes may be necessary). May be package extensions separately. By accident have you seen the dates of the fixes proposed by vassili 2007 this is not that long compared to the changes of compiled method that we are waiting since at least 2001. So this is why changing is important. But changing for better :) Stef > > > Cheers, > Esteban > > On 2009-01-27 13:09:30 -0200, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> said: > >> I found this blog entry really nice on this specific question. >> >> http://blog.3plus4.org/2007/04/ >> >> >> On Jan 27, 2009, at 1:44 PM, Esteban Lorenzano wrote: >> >>> Hi, >>> I'm trying to understand why pharo modifies squeak behavior of >>> ifNotNil: and introduces the optional parameter... is there a >>> reason? >>> >>> Cheers, >>> Esteban >>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 27, 2009

Re: [Pharo-project] why #ifNotNil: accepts parameter?

by Lukas Renggli

> And, I also agree with lukas. blahDo: is ugly, if you have an elegant > solution... but, what I have to do with OB-Tools? I replace methods > (like before) or better I create a package OB-Tools-Squeak with > extensions for Squeak? I guess the best is to follow the Seaside coding conventions (http://www.seaside.st/community/conventions) for cross platform code like OB-Tools. You might also want to use Slime (http://www.lukas-renggli.ch/blog/slime) because it automatically fixes simple issues like the #ifNotNilDo: thing. Also keep in mind that OB-Tools is supposed to run on GemStone , so better not use #ifNotNilDo:. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 27, 2009

Re: [Pharo-project] why #ifNotNil: accepts parameter?

by Esteban Lorenzano

Very interesting stef, thanks a lot... but now, I'm not sure of what I did with OB-Tools (I just replace ifNotNil: [Â :blah |Â ... ] with ifNotNilDo: [ :blah |Â ... ]... I understand why the first version of ifNotNil: is done like that in pharo... but what I do with compatibility? will pharo still support ifNotNilDo:? And, I also agree with lukas. blahDo: is ugly, if you have an elegant solution... but, what I have to do with OB-Tools? I replace methods (like before) or better I create a package OB-Tools-Squeak with extensions for Squeak? I know... this is hardly a "pharo issue", but maybe can provide pharo developers of clues of what to do if they are trying to keep compatibiity (I know, that's not a pharo goal -compatibility-, but sometimes may be necessary). Cheers, Esteban On 2009-01-27 13:09:30 -0200, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> said: > I found this blog entry really nice on this specific question. > > http://blog.3plus4.org/2007/04/ > > > On Jan 27, 2009, at 1:44 PM, Esteban Lorenzano wrote: > >> Hi, >> I'm trying to understand why pharo modifies squeak behavior of >> ifNotNil: and introduces the optional parameter... is there a reason? >> >> Cheers, >> Esteban >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 27, 2009

Re: [Pharo-project] why #ifNotNil: accepts parameter?

by StÃ©phane Ducasse

I found this blog entry really nice on this specific question. http://blog.3plus4.org/2007/04/ On Jan 27, 2009, at 1:44 PM, Esteban Lorenzano wrote: > Hi, > I'm trying to understand why pharo modifies squeak behavior of > ifNotNil: and introduces the optional parameter... is there a reason? > > Cheers, > Esteban > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 27, 2009

Re: [Pharo-project] why #ifNotNil: accepts parameter?

by Esteban Lorenzano

On 2009-01-27 11:05:49 -0200, Lukas Renggli <renggli(a)gmail.com> said: >> I'm trying to understand why pharo modifies squeak behavior of >> ifNotNil: and introduces the optional parameter... is there a reason? > > Squeak for that matter is incompatible with all other existing > Smalltalk implementations. Luckily that was changed in Pharo. the > compiler can easily figure out if an argument needs to be passed into > the block or not. There is really no need for all these ugly #...Do: > methods. > > Lukas Yes, I understand... but now I have a compatibility issue with OB-Tools (works on pharo, doesn't works on squeak) :( Anyway, I understand :) Cheers, Esteban

Jan. 27, 2009

Re: [Pharo-project] why #ifNotNil: accepts parameter?

by Lukas Renggli

> I'm trying to understand why pharo modifies squeak behavior of > ifNotNil: and introduces the optional parameter... is there a reason? Squeak for that matter is incompatible with all other existing Smalltalk implementations. Luckily that was changed in Pharo. the compiler can easily figure out if an argument needs to be passed into the block or not. There is really no need for all these ugly #...Do: methods. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 27, 2009

[Pharo-project] why #ifNotNil: accepts parameter?

by Esteban Lorenzano

Hi, I'm trying to understand why pharo modifies squeak behavior of ifNotNil: and introduces the optional parameter... is there a reason? Cheers, Esteban

Jan. 27, 2009