This &quot;tip&quot; is very welcome, didn&#39;t know that you could import changes made from another image. Should definitely be included in the section &quot;recovering lost changes&quot; in the Pharo book (in case it isn&#39;t there already ;-).<div>

<br></div><div>Also very welcome is a new &quot;description of changes&quot;. Without knowing its details, may I make a suggestion?</div><div><br></div><div>When recovering lost changes what we need is to quickly distinguish (i.e. &quot;filter-out&quot;) operations on classes/methods and everything else. Having to look through all the do-its in order to see if they are &quot;Workspace experiments&quot; or important is very time-consuming, and there is always the possibility to miss some important &quot;do it&quot;, and then the whole &quot;import&quot; is stopped.</div>

<div><br></div><div>So it would be great if there were different &quot;filters&quot;, and if the changes were more explicit.</div><div><br></div><div>Other than that, when I needed it, I was grateful that this functionality existed at all :-)</div>

<div><br></div><div>Cheers,</div><div><br></div><div>Sebastian</div><div><br></div><div><br><div class="gmail_quote">2012/11/8 St��phane Ducasse <span dir="ltr">&lt;<a href="mailto:stephane.ducasse@inria.fr" target="_blank">stephane.ducasse@inria.fr</a>&gt;</span><br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><br>
On Nov 8, 2012, at 9:03 PM, Sven Van Caekenberghe wrote:<br>
<br>
&gt; Hi,<br>
&gt;<br>
&gt; One of the cool things of Smalltalk&#39;s images/changes file is that you can do a World Menu &gt; Tools &gt; 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.<br>


&gt;<br>
&gt; 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.<br>
&gt;<br>
&gt; No, it is not !<br>
&gt;<br>
&gt; 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.<br>


&gt;<br>
&gt; 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 &gt; Tools &gt; File Browser and open a Changes browser on it.<br>
<br>
</div>We should add a recover from another image shortcut.<br>
<div class="im">&gt;<br>
&gt; I found this very useful. This is a really important technique to be aware of.<br>
&gt;<br>
&gt; Sven<br>
&gt;<br>
&gt; [1] Sadly, not everything is logged in the changes file: creation of new classes, method deletions are not recorded.<br>
<br>
</div>Yes we should change that.<br>
Ezequiel started to work on a new description of changes.<br>
<div class="HOEnZb"><div class="h5"><br>
&gt;<br>
&gt; --<br>
&gt; Sven Van Caekenberghe<br>
&gt; <a href="http://stfx.eu" target="_blank">http://stfx.eu</a><br>
&gt; Smalltalk is the Red Pill<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
<br>
<br>
</div></div></blockquote></div><br></div>