> This "tip" is very welcome, didn't know that you could import changes made > from another image. Should definitely be included in the section "recovering > lost changes" in the Pharo book (in case it isn't there already ;-). > > Also very welcome is a new "description of changes". Without knowing its > details, may I make a suggestion? > > When recovering lost changes what we need is to quickly distinguish (i.e. > "filter-out") operations on classes/methods and everything else. Having to > look through all the do-its in order to see if they are "Workspace > experiments" or important is very time-consuming, and there is always the > possibility to miss some important "do it", and then the whole "import" is > stopped. > > So it would be great if there were different "filters", and if the changes > were more explicit. > > Other than that, when I needed it, I was grateful that this functionality > existed at all :-)
this is planned but no time. Ezequiel was working on that and soon it will get back to argentina and we need somebody else to help. > > Cheers, > > Sebastian > > > 2012/11/8 Stéphane Ducasse <[email protected]> > > On Nov 8, 2012, at 9:03 PM, Sven Van Caekenberghe wrote: > > > Hi, > > > > One of the cool things of Smalltalk's images/changes file is that you can > > do a World Menu > Tools > Recover lost changes… to get back most [1] of > > your code in case your image/OS/machine suddenly crashed or you forgot to > > save your image or commit your Monticello packages. > > > > But we all have encountered the situation where the image is broken, saved > > in such a state that it no longer starts up properly. In that case your > > code might seem lost forever. > > > > No, it is not ! > > > > Two days ago I had this problem myself and I remembered something Marcus > > said some time ago: you can access the changes file of one (in casu your > > broken image) from another (working) image to select/recover the changes > > you want. It worked perfectly. > > > > The easiest procedure it to copy the .changes file from the broken image > > and rename its extension to .cs and then open it from a World Menu > Tools > > > File Browser and open a Changes browser on it. > > We should add a recover from another image shortcut. > > > > I found this very useful. This is a really important technique to be aware > > of. > > > > Sven > > > > [1] Sadly, not everything is logged in the changes file: creation of new > > classes, method deletions are not recorded. > > Yes we should change that. > Ezequiel started to work on a new description of changes. > > > > > -- > > Sven Van Caekenberghe > > http://stfx.eu > > Smalltalk is the Red Pill > > > > > > > > > > >
