Le 27/1/15 13:21, Roberto Minelli a écrit :
### NautilusRefactoring
- How does it work? Why there are different methods to remove a class, for example? e.g.,
NautilusRefactoring>>#removeClasses: vs. AbstractTool>>#removeClasses:
I looked at it and clean it a bit.
Now AbstractTool is common to all the tools.
NautilusRefactoring introduces refactoring at the level of nautilus
hence redefines the methods.
- Why #removeClasses: is triggered before the actual removal (i.e.,
confirmation dialogue)?
where?
because this is not what I see.
I renamed private... by classRemoval.....
removeClasses: aCollection
"Execute the refactoring of the receiver."
| refactoring |
refactoring := self classRemovalRefactoringObjectFor: aCollection.
refactoring model environment: self model browsedEnvironment.
self performRefactoring: refactoring.
^ true
