On 24/03/2013 17:19, Ben Coman wrote:
Stéphane Ducasse wrote:
On Mar 24, 2013, at 10:43 AM, Marcus Denker <marcus.denker@inria.fr> wrote:
On Mar 24, 2013, at 10:40 AM, "Sean P. DeNigris" <sean@clipperadams.com> wrote:
Mark Bestley wrote
For OSX what should probably happen is that the image is saved to ~/Library/Application Support That doesn't sound right to me. How about the use case where I have a portable image on a USB stick? I don't want to make a local copy of the image, just run it. I get putting the VM in a shared predictable location, but why the image? How does one then keep multiple Pharo 2.0's on the same computer? We will not do it like this.
What is planned is that the "Pharo installation" contains a template (read only). When you open the template, it will ask you to save the image to your home directory.
Images are like documents, it should be very easy to have a lot of them.
why should we decide where people should put them. I put the images where I want them to be.
You have learnt where you want them to be. The defaults are for a user who does not know where to put them. As well as the following ...
Because corporate system administrators expect programs to put things in the "correct" locations as defined by the OS vendor. This helps OS platform certification and even if you don't go that far, it lends an air of professionalism.
It only needs to be a default.
I was only suggesting this as a default. It also helps new users so that when they ask for help with OS related stuff elsewhere Pharo appears to act like a normal OS program, this would help to limit the number of responses like the original article where Pharo did not fit in with what was expected by the user of the Operating system. However the freedom to do what ever is wanted should be kept as well.
I should write down what is the plan⦠sadly I have too much else to do, so this will take a while.
Marcus