Since this One Click setup is intended for
first-timers, I'd suggest
activating by default the PRImagePersistency and modifying its method
saveImageAs: by changing (or adding) two messages :
The One-Click Experience does not target to provide an image for
production. It is more like a ready-made image to experiment (I am
using for lectures and tutorials) and to develop. Having the
PRImagePersistency enabled in a development environment can cause
serious troubles, therefor it is off by default.
saveChangesInFileNamed: (image
fullNameForChangesNamed:
'seaside.changes');
saveImageInFileNamed: (image fullNameForImageNamed: 'seaside.image')
...may be even calling those methods only when the running image is
already named 'seaside'?
What does this do different to what we have now?
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch