December 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] How to handle Squeak / Pharo differences

by Serge Stinckwich

2011/12/26 laurent laffont <laurent.laffont(a)gmail.com>: > Hi, > > I've tried to load Koans > (https://www.hpi.uni-potsdam.de/hirschfeld/trac/SqueakCommunityProjects/wiki…) > on Pharo. This is this the same code than this one: https://github.com/sl4m/gnu_smalltalk_koans ? -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Matsuno Laboratory, Kyoto University, Japan (until 12/2011) http://www.mechatronics.me.kyoto-u.ac.jp/ Every DSL ends up being Smalltalk http://doesnotunderstand.org/

Dec. 26, 2011

Re: [Pharo-project] Destiny of changed:/update:

by Noury Bouraqadi

I suggest to keep it. It's lightweight solution for problems where events/announcement are overkill. Noury -- http://twitter.com/#!/NouryBouraqadi On 26 dÃ©c. 2011, at 14:43, Sean P. DeNigris wrote: > Will changed:/update: disappear and be totally replaced by Announcements? > > I ask because I'm using ListModel and noticed that it sends a generic "self > changed: #selectionIndex". I built a GUI that had two of them, and couldn't > differentiate between the updates, so I was going to enhance it a little. > > -- > View this message in context: http://forum.world.st/Destiny-of-changed-update-tp4234693p4234693.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Dec. 26, 2011

[Pharo-project] Destiny of changed:/update:

by Sean P. DeNigris

Will changed:/update: disappear and be totally replaced by Announcements? I ask because I'm using ListModel and noticed that it sends a generic "self changed: #selectionIndex". I built a GUI that had two of them, and couldn't differentiate between the updates, so I was going to enhance it a little. -- View this message in context: http://forum.world.st/Destiny-of-changed-update-tp4234693p4234693.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 26, 2011

[Pharo-project] [update 1.4] #14274

by stephane ducasse

14274 ----- - Issue 4783: Shadow and Corner related fixes. http://code.google.com/p/pharo/issues/detail?id=4783 - Issue 4875: Polymorph WindowActiveDropShadow for ShadowStyle: #diffuse does not display correctly for left and right bottom corner, when corners are rounded. http://code.google.com/p/pharo/issues/detail?id=4875 I hope that this is ok :) but it looked like. Stef

Dec. 26, 2011

Re: [Pharo-project] Little list of actions looking for progress

by StÃ©phane Ducasse

I was planning to look at the extensions proposed by Issue 4725: extend the string protocol http://code.google.com/p/pharo/issues/detail?id=4725 So may be we should have a look at them too. Stef On Dec 26, 2011, at 11:43 AM, Sven Van Caekenberghe wrote: > > On 26 Dec 2011, at 10:52, StÃ©phane Ducasse wrote: > >> Issue 2560: Convenient methods from Grease for Strings >> -http://code.google.com/p/pharo/issues/detail?id=2560 > > I will do the strings extensions issue. > > Sven

Dec. 26, 2011

Re: [Pharo-project] Little list of actions looking for progress

by StÃ©phane Ducasse

Cool and thanks. For us this is important to get a really nice and powerful default core libraries! Stef On Dec 26, 2011, at 11:43 AM, Sven Van Caekenberghe wrote: > > On 26 Dec 2011, at 10:52, StÃ©phane Ducasse wrote: > >> Issue 2560: Convenient methods from Grease for Strings >> -http://code.google.com/p/pharo/issues/detail?id=2560 > > I will do the strings extensions issue. > > Sven

Dec. 26, 2011

[Pharo-project] [update 1.4] #14272

by StÃ©phane Ducasse

14272 ----- - Issue 5128: HandMorph>>userInitials: aString andPicture: aForm (part one just the drawOn: method). well another one is called during refresh :) http://code.google.com/p/pharo/issues/detail?id=5128

Dec. 26, 2011

Re: [Pharo-project] How to handle Squeak / Pharo differences

by laurent laffont

Thank you Lukas, I will look at this. Laurent On Mon, Dec 26, 2011 at 11:52 AM, Lukas Renggli <renggli(a)gmail.com> wrote: > For Seaside 2.x this is the global variable SeasidePlatformSupport > that has to be bound to some implementation (this was a bit hacky). > > For Seaside 3.x this is the abstract class GRPlatform, and the Pharo > implementation is GRPharoPlatform. There are countless *-Pharo > packages that add Pharo specific code (mostly to GRPharoPlatform). > > For OmniBrowser this is the abstract class OBPlatform, and the Pharo > implementation in OBPharoPlatform. It redirects some of the preference > code. For the UI differences this is the abstract class OBInterface, > and the Pharo implementation OBPolymorphInterface. Again the code is > in platform specific packages, so you typically won't see the code for > other platforms. > > Lukas > > On 26 December 2011 11:38, laurent laffont <laurent.laffont(a)gmail.com> > wrote: > > On Mon, Dec 26, 2011 at 11:31 AM, Lukas Renggli <renggli(a)gmail.com> > wrote: > >> > >> > I do not get why Seaside should provide a package to deal with > >> > Preferences a la squeak? > >> > I imagine that Seaside does not rely on Preferences so. > >> > >> Indeed, Seaside does not deal with Preferences, but the question was > >> about how to deal with differences in general. > > > > > > Yes. > > > > Lukas, do you have some Seaside / OB class names in mind so I can find > > faster ? Thanks > > > > Laurent > > > > > > > >> > >> > >> Lukas > >> > >> -- > >> Lukas Renggli > >> www.lukas-renggli.ch > >> > > > > > > -- > Lukas Renggli > www.lukas-renggli.ch > >

Dec. 26, 2011

Re: [Pharo-project] How to handle Squeak / Pharo differences

by Lukas Renggli

For Seaside 2.x this is the global variable SeasidePlatformSupport that has to be bound to some implementation (this was a bit hacky). For Seaside 3.x this is the abstract class GRPlatform, and the Pharo implementation is GRPharoPlatform. There are countless *-Pharo packages that add Pharo specific code (mostly to GRPharoPlatform). For OmniBrowser this is the abstract class OBPlatform, and the Pharo implementation in OBPharoPlatform. It redirects some of the preference code. For the UI differences this is the abstract class OBInterface, and the Pharo implementation OBPolymorphInterface. Again the code is in platform specific packages, so you typically won't see the code for other platforms. Lukas On 26 December 2011 11:38, laurent laffont <laurent.laffont(a)gmail.com> wrote: > On Mon, Dec 26, 2011 at 11:31 AM, Lukas Renggli <renggli(a)gmail.com> wrote: >> >> > I do not get why Seaside should provide a package to deal with >> > Preferences a la squeak? >> > I imagine that Seaside does not rely on Preferences so. >> >> Indeed, Seaside does not deal with Preferences, but the question was >> about how to deal with differences in general. > > > Yes. > > Lukas, do you have some Seaside / OB class names in mind so I can find > faster ? Thanks > > Laurent > > > >> >> >> Lukas >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> > -- Lukas Renggli www.lukas-renggli.ch

Dec. 26, 2011

[Pharo-project] [update 1.4] #14271

by StÃ©phane Ducasse

14271 ----- - Issue 5128: HandMorph>>userInitials: aString andPicture: aForm (part one just the drawOn: method). http://code.google.com/p/pharo/issues/detail?id=5128 - Issue 5129: adding eventSource instance variable to HandMorph http://code.google.com/p/pharo/issues/detail?id=5129 Stef

Dec. 26, 2011