[Pharo-dev] Morph should not query Color for nil :(

Morph>>colorString: aColor aColor ifNil: [ ^'nil' ]. ^aColor name ifNil: [ aColor storeString ] ifNotNil: [ :colorName | 'Color ', colorName ] such behavior should be moved to Color. The problem is not Morphic per se. This is that OO design was often not considered.

Re: [Pharo-dev] Unused ugly morph methods...

It is forbidden by contract :) 100% On Jan 31, 2016 9:31 PM, "stepharo" wrote: > I really hope that Bloc will forbid such systematic submorphs use because > it leads to code like that. > > Stef > > > submorphNamed: aName > ^ self submorphNamed: aName ifNone: [nil] > >

Re: [Pharo-dev] Thanks nicolai and the sprinter for fixing the selectorTable

On 31/01/2016 15:23, stepharo wrote: > Hi guys > > Thanks for this fix. > I will start recording videos. > > Stef > In the last image I get errors all the time when I use unimplemented methods. I think this might be related if this was done to add syntax highlighting for unimplemented

[Pharo-dev] [50547] recompiling a simple method -> AST cache -> crash

Hi I do not know if this was fixed between 47 and 60 but I simply recompiled BorderedMorph>> initialize to remove a line and I got a do semantic analysis error, leading to a cache error and red square of death in the browser. S.

Re: [Pharo-dev] Warning in Pharo 5

probably this is the default… which it should not! Esteban > On 31 Jan 2016, at 16:51, Mariano Martinez Peck wrote: > > Did you set GTGenericStackDebugger alwaysOpenFullDebugger: true ?? > > On Sun, Jan 31, 2016 at 12:12 PM, Cyril Ferlicot D.

[Pharo-dev] ProcessTest>>testSchedulingIsFirstComeFirstServed

My general understanding of process scheduling is that it is FIFO within same priority. Indeed Pharo has a test for this ProcessTest>>testSchedulingIsFirstComeFirstServed, which however I thought was a bit fragile and I was looking to revise. But now I'm curious whether same-priority-process

Re: [Pharo-dev] GTDebugger missing block parameters?

2016-01-28 1:37 GMT+01:00 Eliot Miranda : > Hi Nicolai > > On Jan 15, 2016, at 4:57 AM, Nicolai Hess wrote: > > > > 2016-01-15 13:26 GMT+01:00 Stephan Eggermont : > >> When debugging a method containing a block with a parameter,

Re: [Pharo-dev] 17502. Morph layoutProperties must not be nil by default

> On 31 Jan 2016, at 13:38, Esteban Lorenzano wrote: > > >> On 31 Jan 2016, at 13:26, Henrik Nergaard > > wrote: >> >> LayoutProperties is an optional part of Morph using some type of defined >> layout (mostly used

Re: [Pharo-dev] 17502. Morph layoutProperties must not be nil by default

no, I don’t :) I commented there. > On 30 Jan 2016, at 21:22, Aliaksei Syrel wrote: > > Hello > > Do you agree? > https://pharo.fogbugz.com/f/cases/17502/Morph-layoutProperties-must-not-be-nil-by-default > >

Re: [Pharo-dev] 17502. Morph layoutProperties must not be nil by default

> On 31 Jan 2016, at 13:16, Aliaksei Syrel wrote: > > layoutProperties := NullLayoutProperties uniqueInstance > to share only one object you would be creating “extension morphs"l anyway > > On Sun, Jan 31, 2016 at 1:06 PM, Esteban Lorenzano

Re: [Pharo-dev] Rubric: spotter with preview leaks some memory

Hi, Hmm. I work with Spotter with preview enabled all the time… but I do not seem to get to the point in which I have to kill the styling process. How do the signs look like (maybe I am not looking at the right thing)? Cheers, Doru > On Jan 31, 2016, at 9:42 AM, Nicolai Hess

Re: [Pharo-dev] Warning in Pharo 5

Le 31/01/2016 16:51, Mariano Martinez Peck a écrit : > Did you set GTGenericStackDebugger alwaysOpenFullDebugger: true ?? > > -- > Mariano > http://marianopeck.wordpress.com I did it in the last Pharo 5 without loading any setting. -- Cyril Ferlicot http://www.synectique.eu 165 Avenue

Re: [Pharo-dev] 17502. Morph layoutProperties must not be nil by default

Closed, thanks for feedback :) Cheers, Alex On Sun, Jan 31, 2016 at 12:43 PM, Denis Kudriashov wrote: > Hi. > > Wait, I do not like this... remember *anything* can be a Morph, not just a >> widget (points, "atoms bouncing", etc.). >> > > Could you explain it? Because you

[Pharo-dev] Thanks nicolai and the sprinter for fixing the selectorTable

Hi guys Thanks for this fix. I will start recording videos. Stef

Re: [Pharo-dev] 17502. Morph layoutProperties must not be nil by default

> On 31 Jan 2016, at 13:26, Henrik Nergaard wrote: > > LayoutProperties is an optional part of Morph using some type of defined > layout (mostly used by the LayoutPolicy subclasses), this is though not the > only way to do layout for a Morph and its submorphs; so not

[Pharo-dev] Warning in Pharo 5

Is it me that did something wrong or in Pharo 5 the warnings open a debugger instead of a Warning window with the explanation? -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France signature.asc Description: OpenPGP digital signature

Re: [Pharo-dev] 17502. Morph layoutProperties must not be nil by default

Hi. Wait, I do not like this... remember *anything* can be a Morph, not just a > widget (points, "atoms bouncing", etc.). > Could you explain it? Because you can't add point to morph for example. 2016-01-31 12:21 GMT+01:00 Esteban Lorenzano : > no, I don’t :) > I commented

Re: [Pharo-dev] Rubric: spotter with preview leaks some memory

2016-01-31 13:46 GMT+01:00 Tudor Girba : > Hi, > > Hmm. I work with Spotter with preview enabled all the time… but I do not > seem to get to the point in which I have to kill the styling process. How > do the signs look like (maybe I am not looking at the right thing)? > >

Re: [Pharo-dev] 17502. Morph layoutProperties must not be nil by default

layoutProperties := NullLayoutProperties uniqueInstance to share only one object On Sun, Jan 31, 2016 at 1:06 PM, Esteban Lorenzano wrote: > > On 31 Jan 2016, at 12:43, Denis Kudriashov wrote: > > Hi. > > Wait, I do not like this... remember