[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 #getComments and #addComments:notifying: to fill out behaviour for package comments. What is the kosher way to work and contribute in such situations? I guess it will also pop up in situations outside of Nautilus. -- View this message in context: http://forum.world.st/Best-practice-for-overwriting-methods-in-other-classes... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.