Re: [Pharo-dev] Best practice for overwriting methods in other classes

I have now twice in two different situations felt a need to "steal" a method in Nautilus and make that method an extension method in my own package. In situation A, I wanted to steal the #buildCommentPane to use a different Morph for class comments, In situation B, Sergio and I needed to redefi

Re: [Pharo-dev] Best practice for overwriting methods in other classes

On Fri, May 22, 2015 at 1:08 PM, Kasper Osterbye wrote: > I have now twice in two different situations felt a need to "steal" a > method > in Nautilus and make that method an extension method in my own package. > > In situation A, I wanted to steal the #buildCommentPane to use a different > Morph

Re: [Pharo-dev] Best practice for overwriting methods in other classes

> On 22 May 2015, at 07:08, Kasper Osterbye wrote: > > I have now twice in two different situations felt a need to "steal" a method > in Nautilus and make that method an extension method in my own package. > > In situation A, I wanted to steal the #buildCommentPane to use a different > Morph f

[Pharo-dev] Best practice for overwriting methods in other classes

I have now twice in two different situations felt a need to "steal" a method in Nautilus and make that method an extension method in my own package. In situation A, I wanted to steal the #buildCommentPane to use a different Morph for class comments, In situation B, Sergio and I needed to redefine