I put my images into a ~/Pharo/imageDir/image I agree in the one dir per image approach⦠but we were arguing about the root, not the other part :) Esteban On 27 Jan 2014, at 17:53, Sebastian Sastre <sebastian@flowingconcept.com> wrote:
On Jan 27, 2014, at 2:27 PM, Sean P. DeNigris <sean@clipperadams.com> 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