I don't think anyone would want to read their *real* email inside a
web-embedded Squeak page, would they?  At least on my computer, email
files are about the most sensitive they are.  I don't care so much if
someone wipes out my copy of the Linux kernel, but I certainly care
about my email.

So I'm guessing there is some application of Celeste that we're wanting
to use here?  For example, the ability to email a Squeak page to
someone?!  For such applications, it seems perfectly appropriate to use
plugin-specific EMAIL.xxx files.

-Lex





Bob Arning <arning at charm.net> wrote:
> Duane,
> 
> Just in case there was any confusion about what I was getting at:
> 
> 1. The current implementation of the squeak VM as a browser plugin limits all file i/o to the directory in which squeak exists (currently 'yourHD:System Folder:Preferences:Squeak:Internet:' on the Mac) as a security measure. You could make your own plugin that did not have that restriction and worry about misbehaving squeaklets or not.
> 
> 2. Celeste had a couple of methods that used a local file name, 'EMAIL.something.log', e.g. in a message that requires a full path name. These broke when run in a browser since assumptions about working directories do not work in this mode.
> 
> 3. Celeste now works in a browser and hopefully I will not have broken any legitimate expectations of Celeste users. HOWEVER, given (1) and the fact that some people apparently keep their Celeste files outside the squeak directory, this _will_ break when run in a browser.
> 
> 4. No other change or impact on file operations is intended.
> 
> Cheers,
> Bob
> 
> On Thu, 14 Sep 2000 12:59:28 -0700 Duane Maxwell <dmaxwell at exobox.com> wrote:
> >We have a situation where we'd generally like to be able to put writable
> >files outside of the Squeak directory.  This would include Celeste files.
> >
> >>Celeste users:
> >>
> >>I have been doing a little tweaking necessary to get Celeste working when
> >>Squeak is running in a browser. The problems I have hit so far are the
> >>uses of
> >>	StandardFileStream>>open:forWrite:
> >>in
> >>	IndexFile>>logStream and MailDBFile>>save
> >>
> >>which were using local file names and should really be full path names. I
> >>got it working and then started to wonder about some lack of clarity here.
> >>The default for Celeste are files like EMAIL.xxx in the squeak directory,
> >>but there appears to be the possibility that some other directory might be
> >>used. So the question is:
> >>
> >>Does anyone use Celeste where the files are
> >>(a) in a directory *below* the squeak directory or
> >>(b) in a directory *outside* the squeak directory?
> >>
> >>Case (a) might continue to work in a browser, but case (b) would not. Are
> >>either of these actually used or planned?
> >>
> >>Cheers,
> >>Bob