Hi Avi!

Avi Bryant <avi at beta4.com> wrote:
[SNIP]
> The advantage here is that it's possible to catch any individual one of
> these without affecting the rest of the UI.  For example, in an install
> script you might want to ignore any simple messages, but still have
> progress bars show up - so you could do something like
> 
> [...] on: InformUserNotification do: [:n | n resume].

Ahh, sorry - I responded to Andreas post before reading this thoroughly.
The above I assume explains the somewhat "non obvious" solution.

> What I've actually done so far is a hybrid of this approach - I define an
> exception for each interaction, all of which are subclasses of
> UserNotification.  I've then defined UserNotificationHandler classes that
> catch any UserNotifications, and then call a particular handler method
> using double dispatch through the notification.  This way, generally what
> you have to do for a new UI is define a new Handler subclass and implement
> the #handleFooNotification:, #handleBarNotification: methods - but it
> would still be possible to catch individual exceptions in special cases.
> However, this all feels a bit heavyweight and overdesigned.
> 
> Any comments?

I like the goals you set up, though I would agree it fells
"overdesigned". On the other hand I can't counter with anything simpler.

> Avi

regards, Göran