Hi!

Russell Allen <russell.allen at firebirdmedia.com> wrote:
> "Richard A. O'Keefe" <ok at atlas.otago.ac.nz> wrote:
> > The number of files there *are* in an application *once it is installed*
> > and the number of files the user *has to touch* to make installation happen
> > are very different things.  The fact that a Squeak application might want
> > a VM, some sources, an image, lots of pictures, and some squeak-books
> > doesn't mean that the *user* ever has to touch more than one file.
> 
> When I started to use Squeak, it came in four files (VM, image, changes,
> source).  When it ran, it ran within those four files.
> 
> Now my four files have grown.  I have another four files for Email, a
> folder called 'prefs' and another folder called 'audio' that have popped
> up from nowhere.  A 'squeaklets' folder has appeared and started to fill
> itself with stuff.  When I run Squeak, misc files such as
> 'SqueakDebug.log' appear, change and dissapear.  And (worst of all) a
> folder called 'My Squeak' has appeared in a completely different part of
> my hard drive (although, to be fair I think this is from the browser
> plugin :).

Well, I guess one of the reasons is that external files are not as
easily corrupted.
Images do burn sometimes... That would probably account for email and
prefs.

Another reason may be that it is information that should be shared
between images - prefs? Are they shared?

And the debug-log is because of the fact that the image crashed so that
was the only way to report what happened and Squeak can run headless too
needing to report what went wrong.

Can't really say about audio and squeaklets.

regards, Göran