Avi, see Stephen Pair's email on this.

Right now the logic is "is this image VW, VA, or other Smalltalk."

CstMessageHandler class>>selectCorrectBehavior
CstMessageHandler class>>newOwner:
CstMessageDispatcher>>newDefaultHandler
CstMessageDispatcher>>initialize




-----Original Message-----
From: Avi Bryant [mailto:avi at beta4.com]
Sent: Monday, December 09, 2002 3:24 PM
To: squeak-dev at lists.squeakfoundation.org
Subject: Re: Messenger package ( was: RE: Yet another SAR feature
request (YASFR))



Ah, nice.  Having looked at the web page, but not the code - how does it
determine how to do the messaging?  What I'd like is some kind of
dynamic
scoping mechanism (ie, signal a MessengerImplementationNotification or
something) so that when inside a Seaside app, the Messenger used can be
a
web-based one...

 On Mon, 9 Dec 2002, Brent Vukmer wrote:

> I for one think it's pretty cool!
>
> I filed the attached SAR version of the Messenger package into a
3.4beta image and tried Paul's example code in a Workspace.  Seems to
work just fine.
>
> The only edits I made were to re-name the categories for the extension
methods on Object, String and Symbol to be DVS-friendly ).
>
> -----Original Message-----
> From: Les Tyrrell [mailto:tyrrell at canis.uiuc.edu]
> Sent: Monday, December 09, 2002 12:50 PM
> To: squeak-dev at lists.squeakfoundation.org
> Subject: Re: Yet another SAR feature request (YASFR)
>
>
> Sounds like something that Paul Bauman's Messenger would solve rather
nicely.
>
> http://wiki.cs.uiuc.edu/CampSmalltalk/Messenger+project
>
> - les
>
> ----- Original Message -----
> From: "Stephen Pair" <spair at acm.org>
> To: <squeak-dev at lists.squeakfoundation.org>
> Sent: Saturday, December 07, 2002 7:37 AM
> Subject: Yet another SAR feature request (YASFR)
>
>
> > Ned,
> >
> > One of the things I'm seeing from sar installations is interactive
> > behavior (ie. Installing a SAR opens a morphic window).  I think it
> > would be nice to add some capability to SARInstaller that would
support
> > headless (or quiet installations).  Here are a few ideas about how
to do
> > it...
> >
> > - have some concept in the installer regarding "interactive" vs.
> > "silent" installs...in the preamble you could write "self
isInteractive"
> >
> > - allow parameters to be passed into the installation...the caller
could
> > do this with "SARInstaller class>>installSAR:parameters:" or
similar.
> > The parameters could be a dictionary.
> >
> > - improve methods like #error:, #warning:, #inform:, #confirm:, etc
such
> > that they take a symbol *and* a message as arguments.  For example:
> >
> > self
> > confirm: #installDLLs
> > msg: 'Would you like to install the Windows DLLs for
> > this package?'
> >
> > The implementation of #confirm:msg: would look for #installDLLs in
the
> > list of parameters and, if found, will answer that value...if not
found,
> > an exception would be signaled whose defaultAction is to prompt the
> > user.
> >
> > Anyway...it would be nice to support fully automated installations;
> > especially as people want to do automated builds, loading of
> > pre-requisites, etc.
> >
> > - Stephen
> >
> >
>
>
>