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

Re: [Pharo-project] Issue 3688 in pharo: Network primitives missing in the image

by pharo＠googlecode.com

Comment #2 on issue 3688 by jannik.l...(a)gmail.com: Network primitives missing in the image http://code.google.com/p/pharo/issues/detail?id=3688 This one cannot be included because of call to SocketAddressInformation primGetNameInfo: socketAddress flags: flags <primitive: 'primitiveResolverGetNameInfo' module: 'SocketPlugin'> flags == 0 ifTrue: [^self primGetNameInfo: socketAddress flags: SocketAddressInformation numericFlag]. self primitiveFailed

Feb. 10, 2011

[Pharo-project] Issue 3691 in pharo: Cleaning by comparing SimpleMorphic and Morphic

by pharo＠googlecode.com

Status: Accepted Owner: stephane...(a)gmail.com New issue 3691 by stephane...(a)gmail.com: Cleaning by comparing SimpleMorphic and Morphic http://code.google.com/p/pharo/issues/detail?id=3691 I did several cleans by comparing SimpleMorphic Canavs and FormCanvas Attachments: CanvasCleaning.2.cs 36.9 KB

Feb. 10, 2011

Re: [Pharo-project] Issue 3690 in pharo: Monticello Browser: improve submit slice dialog

by pharo＠googlecode.com

Updates: Labels: Type-RequestForEnhancement Comment #1 on issue 3690 by laurent....(a)gmail.com: Monticello Browser: improve submit slice dialog http://code.google.com/p/pharo/issues/detail?id=3690 (No comment was entered for this change.)

Feb. 10, 2011

Re: [Pharo-project] about fillRectangle: aRectangle fillStyle: aFillStyle

by StÃ©phane Ducasse

http://code.google.com/p/pharo/issues/detail?id=3691 I uploaded my fix. Note that I introduced a log class and should probably remove it but I will do that during the integration. Stef > I volunteer for reviewing th cs also. > > Fernando > > On Thu, Feb 10, 2011 at 6:43 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> Igor I saw that this was a double dispatch but I imagine that this is not needed to duplicate the exact same code within the >> same hierarchy. >> Can you have a look? >> I will prepare a cs or a slice with all my changes and it would be great to have somebody else having a look. >> >> Stef >> >>> it seems duplicated in >>>> pluggableCanvas, canvas and balloonCanvas >>>> >>>> fillRectangle: aRectangle fillStyle: aFillStyle >>>> "Fill the given rectangle. Double-dispatched via the fill style." >>>> >>>> aFillStyle fillRectangle: aRectangle on: self >>>> >>>> >>>> do you confirm that? >>>> >>>> >>> >>> it is a bit tricky. The #fillRectange:fillStyle: is a double-dispatch entry >>> actually one could use: >>> >>> aFillStyle fillRectangle: aRectangle on: self >>> >>> See a CompositeFillStyle how it works. >>> >>> The idea was to replace all uses of #doSomething: x color: y >>> or #doSomething:border:colorA:colorB: >>> >>> with #doSomething: x fillStyle: y... >>> >>> Actually all painting operations could take only two objects: shape >>> and fill style. >>> >>> So, in this respect, a color property of Morph should be a fill style, >>> since color can be described as 'solid fill with single color' fill >>> style, >>> a most simplest possible one. >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> >> >> >> >

Feb. 10, 2011

[Pharo-project] Issue 3690 in pharo: Monticello Browser: improve submit slice dialog

by pharo＠googlecode.com

Status: Accepted Owner: laurent....(a)gmail.com CC: aplan...(a)gmail.com New issue 3690 by laurent....(a)gmail.com: Monticello Browser: improve submit slice dialog http://code.google.com/p/pharo/issues/detail?id=3690 We are currently working on version 1.2, so please verify your issue with the latest 1.2 Unstable version before reporting it - we improved a lot the system. If you fill an issue for the first time, please read "How to report bugs" at http://www.pharo-project.org/community/issue-tracking Pharo image: Pharo-core Pharo core version: Pharo1.2rc2 Latest update: #12332 In Monticello Browser, improve GUI for submitting a fix: - +Slice -> rename to 'Contribute a fix' - in Slice GUI: - put a hint like 'Copy paste issue number and summary from http://code.google.com/p/pharo/issues' - change label 'Included packages' to 'Choose packages to include' - in packages list => checkbox From PharoConf Annecy 2011

Feb. 10, 2011

Re: [Pharo-project] about fillRectangle: aRectangle fillStyle: aFillStyle

by StÃ©phane Ducasse

thanks a lot!!! Stef On Feb 10, 2011, at 11:10 AM, Fernando Olivero wrote: > I volunteer for reviewing th cs also. > > Fernando > > On Thu, Feb 10, 2011 at 6:43 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> Igor I saw that this was a double dispatch but I imagine that this is not needed to duplicate the exact same code within the >> same hierarchy. >> Can you have a look? >> I will prepare a cs or a slice with all my changes and it would be great to have somebody else having a look. >> >> Stef >> >>> it seems duplicated in >>>> pluggableCanvas, canvas and balloonCanvas >>>> >>>> fillRectangle: aRectangle fillStyle: aFillStyle >>>> "Fill the given rectangle. Double-dispatched via the fill style." >>>> >>>> aFillStyle fillRectangle: aRectangle on: self >>>> >>>> >>>> do you confirm that? >>>> >>>> >>> >>> it is a bit tricky. The #fillRectange:fillStyle: is a double-dispatch entry >>> actually one could use: >>> >>> aFillStyle fillRectangle: aRectangle on: self >>> >>> See a CompositeFillStyle how it works. >>> >>> The idea was to replace all uses of #doSomething: x color: y >>> or #doSomething:border:colorA:colorB: >>> >>> with #doSomething: x fillStyle: y... >>> >>> Actually all painting operations could take only two objects: shape >>> and fill style. >>> >>> So, in this respect, a color property of Morph should be a fill style, >>> since color can be described as 'solid fill with single color' fill >>> style, >>> a most simplest possible one. >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> >> >> >> >

Feb. 10, 2011

Re: [Pharo-project] about fillRectangle: aRectangle fillStyle: aFillStyle

by Fernando Olivero

I volunteer for reviewing th cs also. Fernando On Thu, Feb 10, 2011 at 6:43 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Igor I saw that this was a double dispatch but I imagine that this is not needed to duplicate the exact same code within the > same hierarchy. > Can you have a look? > I will prepare a cs or a slice with all my changes and it would be great to have somebody else having a look. > > Stef > >> it seems duplicated in >>> pluggableCanvas, canvas and balloonCanvas >>> >>> fillRectangle: aRectangle fillStyle: aFillStyle >>> Â Â Â Â "Fill the given rectangle. Double-dispatched via the fill style." >>> >>> Â Â Â Â aFillStyle fillRectangle: aRectangle on: self >>> >>> >>> do you confirm that? >>> >>> >> >> it is a bit tricky. The #fillRectange:fillStyle: is a double-dispatch entry >> actually one could use: >> >> aFillStyle fillRectangle: aRectangle on: self >> >> See a CompositeFillStyle how it works. >> >> The idea was to replace all uses of #doSomething: x color: y >> or #doSomething:border:colorA:colorB: >> >> with #doSomething: x fillStyle: y... >> >> Actually all painting operations could take only two objects: shape >> and fill style. >> >> So, in this respect, a color property of Morph should be a fill style, >> since color can be described as 'solid fill with single color' fill >> style, >> a most simplest possible one. >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> > > >

Feb. 10, 2011

Re: [Pharo-project] Issue 3401 in pharo: Comparison of Urls is not possible yet

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #1 on issue 3401 by laurent....(a)gmail.com: Comparison of Urls is not possible yet http://code.google.com/p/pharo/issues/detail?id=3401 In PharoInbox: SLICE-Issue-3401-Comparison-of-Urls-is-not-possible-yet-LaurentLaffont.1 Integration of changeset submitted by Cedrick

Feb. 10, 2011

[Pharo-project] A tinyBenchmark

by Torsten Bergmann

see http://fbanados.wordpress.com/2011/02/10/a-tinybenchmark Maybe Eliot is able to say something here on the main differences between Cog <-> VW VM. Thx T. -- NEU: FreePhone - kostenlos mobil telefonieren und surfen! Jetzt informieren: http://www.gmx.net/de/go/freephone

Feb. 10, 2011

Re: [Pharo-project] what is the goal of warpImage: aForm transform: aTransform

by StÃ©phane Ducasse

strange because I can rotate windows and other and still me method has no sender... so this should be for something else. On Feb 9, 2011, at 7:54 PM, Igor Stasenko wrote: > i guess it is related to warpBlt engine, > which can zoom/rotate forms when blitting and do other distortions.. > > > On 9 February 2011 17:03, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> there are no sender in Pharo 1.3? >> SMx does not have them. >> >> Stef >> >> >> > > > > -- > Best regards, > Igor Stasenko AKA sig. >

Feb. 10, 2011