On Jan 27, 2014, at 2:27 PM, Sean P. DeNigris <[email protected]> wrote:
>> I think this is conceptually wrong. Images has to go (by default) into >> "~/Documents/Pharo Images". (Same as VMWare virtual machines go into >> "~/Documents/Virtual Machines" and parallels into “~/Documents/Parallels" This sounds right but I’d not take it lightly. I don’t know what would be best. For what is worth, here are some thoughts: 1. I won’t put imageS in a folder. More than one image per folder smells 2. that structure doesn’t look very much git friendly. I’d rather use a Documents/git folder under which I’d clone any project including the many Pharo based projects. As usual, when you clone a git repo, it has its own folder with its own stuff 3. I might want to version the image itself in the git repo. Maybe I want keep a track of the VM too 4. subfolders of the image dir are often used by applications, again, looks like it will easily misfit Idea: maybe the launcher can be location agnostic and remember somewhere the locations of the lasts images that where opened with it and simply offer links to open the ones at the lasts, say 7 images, paths. You will even evade coupling that to the OS
