on 3/20/01 5:13 AM, "Sam Ruby" <[EMAIL PROTECTED]> wrote:
> I've agonized over this. At the moment, my feeling is that the nag stuff
> is not a property of the workspace definition. The workspace defines what
> the files out on disk ARE, in term of how it takes to produce them. The
> nagging is unrelated to this.
>
> Another way to explain: I can imagine other people wanting to copy my
> workspace definition, but I can't imagine (and don't want for that matter)
> other people copying my nag list.
Let me state another usecase...the current file format of the naglist was a
suggestion that I made to Sam. It is structured in a messaging service type
format [1]. The point being that it would be nice to have a "Nagging
Service" sitting out listening on a Messaging Server somewhere who's job it
is to receive "nag messages" and sent the appropriate emails or other
formats based on them. That way *anything* could create *anything* to nag
about.
Yes, I know that the format of the file could be derived from anywhere, but
the point being that I'm working towards KISS here. :-)
[1] http://elvin.dstc.edu.au/intro/what.html
-jon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
