I'm just a bit embarrassed that in our community - we keep talking about how we have these great refactoring tools (that were invented in smalltalk) - but it looks like in Pharo (and I guess Squeak) - they've fallen a bit behind in terms of usability.
I think people are aware that even in commercial Smalltalks the tools are decades behind the state of the art in Eclipse.
My scenario is a very frequent one - and it should be possible to do effortlessly (and I think that the pieces are in place to do it).
Maybe at ESUG we can rally some energy to help support some of these things (hold an appeal fund... not money - but contributions). I want to help - I just am not sure how to yet - and sometimes this is partly my surprise to discover that some of the things I thought already worked - don't.
Have a look the method #refactoring in ORCmdCreateSubclassRefactoring and ORCmdCreateSuperclassRefactoring. Maybe you can improve something in terms of UI -> Refactoring Engine interaction?
Maybe in the show us your projects demo's it might be worth replaying this scenario and showing how it works in Pharo, and how it works in Eclipse (and maybe another Smalltalk) - and then showing some of the features available in the refactoring engine and trying to get support for improving it.
There are already numerous refactorings that I "ported" from Eclipse: - create multiple accessors at once - generate equal/hash - generate printString - pretty print - make class concrete - swap method As well as some new Smalltalk specific ones: - create cascade - split cascade Lukas -- Lukas Renggli www.lukas-renggli.ch