Hi, I uploaded the following package to pharo-inbox: --------------------- Name: SLICE-ChangesFile-Fixes-Hernan_Wilkinson.2 Author: Hernan Wilkinson Time: 26 June 2009, 7:31:40 pm UUID: 54cc49c6-ee34-4d99-b8fe-6b8b3446ea6c Ancestors: SLICE-ChangesFile-Fixes-Hernan Wilkinson.1 Dependencies: Kernel-Hernan Wilkinson.350, KernelTests-Hernan Wilkinson .119, Traits-Hernan Wilkinson.281, Files-Hernan_Wilkinson.ducasse.57 2009-06-26: Fixes to save class changes in the changes file --------------------- With this fix, all changes made to classes like adding instance variables, class variables, changing method categories, changing class package, etc. are saved to the changes file. I spend some time trying to find the best way to do it, like Stef said some time ago, the code is not easy to understand, so I decided to do it the simplest way. So each method that changes something in the class, it also logs the change. The good thing is that no matter where the change is made, it is saved. The drawback is that when changing a class from the browser's code panel, it saves the definition twice. All the changes are saved as "doit", so no change to the file in was necessary. Ironically, I had a power down issue when testing it, so I did not loose anything! (and help me to find a bug). All the changes are tested. See ClassOrganizerTest, ClassTest and StandardSourceFileArrayTest Bye, Hernan. * *