The user experience I'd go for is something like this:

- user downloads new Squeak release
- runs Squeak
- does something
- saves image
- quits
- runs Squeak again
- by default, sees her/his modifications
- but there should be an option to "start clean" (using the release image)

This would avoid the "please save the image in a different location"
dialog, saving would just default to a location different from the release
image (*)

We had something almost like this for the OLPC Etoys release. The image was
installed in /usr/local/share which is not writable by the user. Saving
defaulted to a user directory. The VM startup script would check if there
was an image in the user directory. If so it would run that, otherwise the
system image.

Something similar could work for Squeak. The main problem would be to have
a VM mechanism for selecting an image you want to run on startup.

- Bert -

(*) That said, forcing the user to choose a location on first time startup
would be okay too, and better than what we have now
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20180517/7635a04b/attachment.html>