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

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

by StÃ©phane Ducasse

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 3689 in pharo: Transcript preference for #characterLimit

by pharo＠googlecode.com

Status: New Owner: ---- New issue 3689 by bstj...(a)yahoo.com: Transcript preference for #characterLimit http://code.google.com/p/pharo/issues/detail?id=3689 It would be useful for some of us to be able to specify a different #characterLimit for the Transcript display in a Preferences setting. 20000 characters is sometimes not enough for some tasks/logging.

Feb. 10, 2011

Re: [Pharo-project] Clipping

by Igor Stasenko

On 9 February 2011 14:57, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > In SMxCanvas>>copyClipRect: aRectangle > Â Â Â Â ^ self copyOrigin: origin clipRect: (aRectangle translateBy: origin) > > SMxFormCanvas>>copyOrigin: aPoint clipRect: aRectangle > Â Â Â Â "Return a copy of this canvas with the given origin. The clipping rectangle of this canvas is the intersection of the given rectangle and the receiver's current clipping rectangle. This allows the clipping rectangles of nested clipping morphs to be composed." > Â Â Â Â ^ self copy > Â Â Â Â Â Â Â Â setOrigin: aPoint > Â Â Â Â Â Â Â Â clipRect: (clipRect intersect: aRectangle) > > Canvas>>copyClipRect: newClipRect > > Â Â Â Â ^ ClippingCanvas canvas: self clipRect: newClipRect > > FormCanvas>>copyOrigin: aPoint clipRect: aRectangle > Â Â Â Â "Return a copy of this canvas with the given origin. The clipping rectangle of this canvas is the intersection of the given rectangle and the receiver's current clipping rectangle. This allows the clipping rectangles of nested clipping morphs to be composed." > Â Â Â Â ^ self copy > Â Â Â Â Â Â Â Â setOrigin: aPoint > Â Â Â Â Â Â Â Â clipRect: (clipRect intersect: aRectangle) > > > Do you think that we can remove ClippingCanvas. There are too many canvases in Pharo. > More than that. I'd prefer not seeing such invocations (copyClipRect:) a more correct form for usage is: canvas clipBy:rect during: [ .... ] so it will clip using given rect, and then restore clipping back to previous one. And of course there is no need to copy canvas (except from some corner cases).. it's only adds a complexity on top of already complex drawing operations. -- Best regards, Igor Stasenko AKA sig.

Feb. 10, 2011

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

by Igor Stasenko

On 9 February 2011 14:38, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > 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] drawString: aString from: firstIndex to: lastIndex at: aPoint font: fontOrNil color: c

by Igor Stasenko

On 9 February 2011 14:44, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > PharoCanvas>>drawString: aString from: firstIndex to: lastIndex at: aPoint font: fontOrNil color: c > Â Â Â Â | font | > Â Â Â Â port colorMap: nil. > Â Â Â Â font := fontOrNil ifNil: [TextStyle defaultFont]. > Â Â Â Â port combinationRule: Form paint. > Â Â Â Â font installOn: port > Â Â Â Â Â Â Â Â foregroundColor: (self shadowColor ifNil:[c]) > Â Â Â Â Â Â Â Â backgroundColor: Color transparent. > Â Â Â Â font displayString: aString on: port > Â Â Â Â Â Â Â Â from: firstIndex to: lastIndex at: (origin + aPoint) kern: 0. > > > > SMxCanvas>>drawString: aString from: firstIndex to: lastIndex at: aPoint font: fontOrNil color: c > Â Â Â Â | font | > Â Â Â Â port colorMap: nil. > Â Â Â Â font := fontOrNil ifNil: [StrikeFont default]. > Â Â Â Â font installOn: port foregroundColor: (self shadowColor ifNil:[c]) backgroundColor: nil. > Â Â Â Â font displayString: aString on: port > Â Â Â Â Â Â Â Â from: firstIndex to: lastIndex at: (origin + aPoint) kern: font baseKern negated. > > > I was wondering why the combinationRule is not needed. > probably because font (in #displayString:..) can choose one, which suits for it best. Not canvas. > Stef > -- Best regards, Igor Stasenko AKA sig.

Feb. 9, 2011

Re: [Pharo-project] about FS: a roadmap

by StÃ©phane Ducasse

I will now I decided to do it for real. Stef

Feb. 9, 2011

Re: [Pharo-project] about FS: a roadmap

by Max Leske

cool! Keep it up. On 09.02.2011, at 19:07, StÃ©phane Ducasse wrote: > I was bored in the train so ... > > I did that and now I will do it regularly. > > > - I added trace to gather the exact type of arguments.... and > - moved FSLocator out of core and in resolver. > - added comments to FSFileSystem>>fileExist: and friends. > - changed category name error handling -> error raising > - better argument name for createDirectory > - added comment to createDirectory > - added comment to copy and friends > - added comment to ensureDirectory: > - added comment to isDirectory: > - added comment to isFile: > - added comment to open: aStringOrPath writable: aBoolean > - added comment to readStreamOn: aStringOrPath > > Next step > - should probably rename FileExists as FileAlreadyExistsError > > Stef >

Feb. 9, 2011

Re: [Pharo-project] [COTDC] 6 - StandardFonts

by Laurent Laffont

Le 9 fÃ©vr. 2011 Ã 19:49, Sven Van Caekenberghe a Ã©crit : > > On 09 Feb 2011, at 17:55, Laurent Laffont wrote: > >> Today: StandardFonts >> >> (really at random this time :) >> >> Comment Of The Day Contest - One Day One Comment >> Rules: >> #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). >> #2: If you cannot comment it, deprecate it. >> Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest >> >> Laurent > > I am a facade and a global reference to actual fonts to be used system wide in a number of predefined categories. > > I also provide methods to interactively choose these fonts, to reset all fonts to some default value, to set larger demo fonts, to construct a font menu and to manipulate the current settings as an external specification. > > The font categories that I know of are: ButtonFont, CodeFont, HaloFont, ListFont, MenuFont and WindowTitleFont I would add: Examples: - I open a dialog to choose the font for buttons with: StandardFonts chooseButtonFont. - To change base size for all fonts (when you want big fonts for a screencast or a presentation): StandardFonts setDemoFonts. - Then restore default fonts with: StandardFonts restoreDefaultFonts. -- Laurent Laffont - @lolgzs Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/

Feb. 9, 2011

Re: [Pharo-project] [SPAM] Re: INRIA-CEA-EDF Deep into Smalltalk School registration open

by Diogenes Moreira

+1 On Wed, Feb 9, 2011 at 3:57 PM, Sven Van Caekenberghe <sven(a)beta9.be> wrote: > > On 09 Feb 2011, at 19:02, StÃ©phane Ducasse wrote: > > > Yes! > > I do not know when but a guy will come and record everything :) > > +1 > > >

Feb. 9, 2011

Re: [Pharo-project] INRIA-CEA-EDF Deep into Smalltalk School registration open

by Sean P. DeNigris

Thank you! Thank you! Thank you! Sean -- View this message in context: http://forum.world.st/INRIA-CEA-EDF-Deep-into-Smalltalk-School-registration… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Feb. 9, 2011