2.5a4 (was Re: [Seaside] onAnswer: problems)

[Bill Holloway]

With regard to all the "concepts flying around," I like the (now) old
xp/agile addage: "Use the simplest tool that solves the problem."

Bill


Avi Bryant said:
>
> On Jun 3, 2004, at 6:41 PM, C. David Shaffer wrote:
>
>> OK, here's one that works several levels deep.
>
> Thanks.  This doesn't solve Adrian's problem, however, so I'm
> experimenting with an alternate solution.  I've just posted Seaside
> version 2.5a4 to SqueakMap.  This introduces a simple event system; you
> can send #triggerEvent:with: to a component, which will give any
> decoration on that component a chance to handle the event.  You can use
> #onEvent:do: to register a block (or continuation)  that a particular
> event will trigger; this will add a new EventDecoration.  #onAnswer:
> does this for the #answer event, and is used during #call:.  Other
> decorations may also choose to intercept events (such as the
> ValidationDecoration, which won't let an #answer: go through unless
> certain conditions are met).
>
> On the one hand, I'm hoping that this becomes a richer way for
> subcomponents to communicate with their parents, and that would be a
> good thing - the single #onAnswer: callback is a little weak.  And it
> does solve the problems with WAAnswerNotification while still tying in
> nicely to the decoration system.  On the other hand, I'm starting to
> feel like there are maybe too many concepts flying around...
>
> Avi
>
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/listinfo/seaside
>


-- 
"If you don't violate someone's human rights some
of the time, you probably aren't doing your job."

     -- Bush Administration Offical who
        supervised the capture and
        transfer of accused terrorists.
        (Washington Post, Thursday, December 26,
        2002; Page A01)