> > Note: Most SM functions use #inform: to display warnings to 
> > the user. I used #notify: in here because I am assuming that
> > server instances of SqueakMap may be running headless, and that
> > a headless server could handle Warning exceptions with no UI
> > interaction.
> 
> Ok, we really need to deal with that.

Yes, but not in this way. It is not Object>>confirm: or Object>>inform: that
is screwed up here. If you want to be able to suppress these notifications
then you should do so explicitly. Neither #inform: nor #confirm: are
exceptional in any sense of the word so it seems rather strange to handle
them as exceptions.

> I've just sent an extremely simplistic ENH to the list that introduces
> Notification classes for #inform: etc, and changes Object to use them
> instead of PopUpMenu directly.
> 
> I can't think of any way this would break existing code, and 
> it sure is nicer for headless servers and web apps.

I'm not at all convinced about this. You would have to randomly guess what
the "right" response for a headless up would be under the circumstances and
I would suspect that this breaks lots of code if ever run under headless
conditions. In addition, the use of #inform: typically signifies a bit of
important information to the user so suppressing it seems like a very stupid
thing to do unless you know beforehand that it is of no importance (but how
could you?).

Cheers,
  - Andreas