On 12 Nov 2007, at 11:14, Lukas Renggli wrote:
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.
Agreed. My proposal was so that newbies don't need to learn the hard
way they have to save their work on Pier... mainly because saving is
important for them but it is not obvious (can be done from http://
localhost:8080/seaside/tools/versionuploader or from the Squeak world
menu... but, in this case, only with 'save', since the image seaside.
1.image produced by 'save as a new version' will be ignored by the
One-Click setup).
It is more like a ready-made image to experiment (I
am
using for lectures and tutorials) and to develop.
It is great. I plan to use to my web designers to experiment and learn.
Having the
PRImagePersistency enabled in a development environment can cause
serious troubles, therefor it is off by default.
I beg to disagree. As PRImagePersistency is currently implemented,
the only risk I can see is that it eventually fill up the disk, which
is actually a very minor trouble.
Moreover, with my my proposed change for newbies, PRPersistency would
would save always with the same filename (seaside.image instead of
2007-11-12 11-05-38.image or whatever), so no fill up of the disk
would happen. If the newbee messes up and needs to start from a blank
slate, he would do fine decompressing the distribution zip again.
Instead, with the current setup, he would be always starting from a
blank slate, want it or not, until he discovers he can save his work.
My fear is that most newbies won't discover
http://localhost:8080/
seaside/tools/versionuploader before they give up.
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?
At start up, One-Click Experience currently ignores any image not
named 'seaside.image' at start-up. If you detect that the image is
named 'seaside.image', you know that you are running under a One-
Click setup, so you can act in a more newbee friendly way as
suggested above.
Cheers
--manuel