January 2016 - Pharo-dev - lists.pharo.org

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

by Cyril Ferlicot Delbecque

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 methods. RubShoutStylerDecorator(Object)>>doesNotUnderstand: #recomposeFrom:to:delta: [ super doesNotUnderstand: aMessage ] in RubShoutStylerDecorator(RubParagraphDecorator)>>doesNotUnderstand: #recomposeFrom:to:delta: in Block: [ super doesNotUnderstand: aMessage ] BlockClosure>>cull: Context>>evaluateSignal: Context>>handleSignal: MessageNotUnderstood(Exception)>>signal RubCurrentLineBarDecorator(Object)>>doesNotUnderstand: #recomposeFrom:to:delta: [ super doesNotUnderstand: aMessage ] in RubCurrentLineBarDecorator(RubParagraphDecorator)>>doesNotUnderstand: #recomposeFrom:to:delta: in Block: [ super doesNotUnderstand: aMessage ] BlockClosure>>cull: Context>>evaluateSignal: Context>>handleSignal: MessageNotUnderstood(Exception)>>signal RubExtraSelectionDecorator(Object)>>doesNotUnderstand: #recomposeFrom:to:delta: [ super doesNotUnderstand: aMessage ] in RubExtraSelectionDecorator(RubParagraphDecorator)>>doesNotUnderstand: #recomposeFrom:to:delta: in Block: [ super doesNotUnderstand: aMessage ] BlockClosure>>cull: Context>>evaluateSignal: Context>>handleSignal: MessageNotUnderstood(Exception)>>signal RubOpeningClosingDelimiterDecorator(Object)>>doesNotUnderstand: #recomposeFrom:to:delta: [ super doesNotUnderstand: aMessage ] in RubOpeningClosingDelimiterDecorator(RubParagraphDecorator)>>doesNotUnderstand: #recomposeFrom:to:delta: in Block: [ super doesNotUnderstand: aMessage ] BlockClosure>>cull: Context>>evaluateSignal: Context>>handleSignal: MessageNotUnderstood(Exception)>>signal RubTextMethodLink(Object)>>doesNotUnderstand: #tes RubTextMethodLink(TextLink)>>= Array(SequenceableCollection)>>hasEqualElements: Array(SequenceableCollection)>>= Array(SequenceableCollection)>>hasEqualElements: RunArray>>= -- Cyril

Jan. 31, 2016

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

by Aliaksei Syrel

It is forbidden by contract :) 100% On Jan 31, 2016 9:31 PM, "stepharo" <stepharo(a)free.fr> 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] > > submorphNamed: aName ifNone: aBlock > "Find the first submorph with this name, or a button with an action > selector of that name" > > > self submorphs do: > [:button | | sub args | > (button respondsTo: #actionSelector) > ifTrue: [button actionSelector == aName ifTrue: [^button]]. > ((button respondsTo: #arguments) and: [(args := button > arguments) notNil]) > ifTrue: [(args at: 2 ifAbsent: [nil]) == aName ifTrue: > [^button]]. > (button isAlignmentMorph) > ifTrue: [(sub := button submorphNamed: aName ifNone: > [nil]) ifNotNil: [^sub]]]. > ^aBlock value > >

Jan. 31, 2016

Morph should not query Color for nil :(

by stepharo

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. Stef

Jan. 31, 2016

Unused ugly morph methods...

by stepharo

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] submorphNamed: aName ifNone: aBlock "Find the first submorph with this name, or a button with an action selector of that name" self submorphs do: [:button | | sub args | (button respondsTo: #actionSelector) ifTrue: [button actionSelector == aName ifTrue: [^button]]. ((button respondsTo: #arguments) and: [(args := button arguments) notNil]) ifTrue: [(args at: 2 ifAbsent: [nil]) == aName ifTrue: [^button]]. (button isAlignmentMorph) ifTrue: [(sub := button submorphNamed: aName ifNone: [nil]) ifNotNil: [^sub]]]. ^aBlock value

Jan. 31, 2016

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

by stepharo

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.

Jan. 31, 2016

Re: [Pharo-dev] Warning in Pharo 5

by Cyril Ferlicot Delbecque

On 31/01/2016 18:33, Esteban Lorenzano wrote: > probably this is the defaultâ¦ which it should not! > > Esteban > GTGenericStackDebugger alwaysOpenFullDebugger. -> false I still get the same thing than on the screen. -- Cyril

Jan. 31, 2016

Re: [Pharo-dev] Warning in Pharo 5

by Esteban Lorenzano

probably this is the defaultâ¦ which it should not! Esteban > On 31 Jan 2016, at 16:51, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > Did you set GTGenericStackDebugger alwaysOpenFullDebugger: true ?? > > On Sun, Jan 31, 2016 at 12:12 PM, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com <mailto:cyril.ferlicot@gmail.com>> wrote: > 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 <http://www.synectique.eu/> > > 165 Avenue Bretagne > Lille 59000 France > > > > -- > Mariano > http://marianopeck.wordpress.com <http://marianopeck.wordpress.com/>

Jan. 31, 2016

Re: [Pharo-dev] Warning in Pharo 5

by Cyril Ferlicot D.

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 Bretagne Lille 59000 France

Jan. 31, 2016

Re: [Pharo-dev] Warning in Pharo 5

by Mariano Martinez Peck

Did you set GTGenericStackDebugger alwaysOpenFullDebugger: true ?? On Sun, Jan 31, 2016 at 12:12 PM, Cyril Ferlicot D. < cyril.ferlicot(a)gmail.com> wrote: > 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 > -- Mariano http://marianopeck.wordpress.com

Jan. 31, 2016

Warning in Pharo 5

by Cyril Ferlicot D.

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

Jan. 31, 2016