Yeah, thanks for your effort. I saw what you were mentioning but I needed confirmation that I didn�t miss the most important feature :)

Ok, so it is just not a tool for me. I have a project folders containing not only smalltalk stuff but also documentation and other files. The project folders are grouped by companies I work for. So central storage of images is a no-go. I do it the other way round. I have one directory where I symlink all current projects folders into. And this directory I put in the MacOS bar to have quick access.

Then I open an image once and save a new version regularly using �save as�. This is a must for me because I experience a lot of image instability and the changes is broken so too easy to loose code. And it wouldn�t work the way you told me because I save images often so copying _before_ opening an image is not an option.

My workflow just needs manual setup of the projects folder which I would like to be solved somewhat more clever. But as I can see it now I need to stick to my stuff. Sad. I think PharoLauncher is nice.

Norbert