Ok, thanks Andreas, I'll add the information I got to the Swiki.

On the first question below, I'll assume that's the way it is, if you
have news, I'll update it later.

Andreas Raab <andreas.raab at gmx.de> wrote:
> Daniel,
> 
> > > Like I was saying, see #dispatchEvent:. It delegates the task to
> > > MorphicEventDispatcher.
> > So, IIUC, behavior here is specialized by overriding
> > #processEvent:using:, and by subclassing MorphicEventDispatcher. Did I
> > miss anything?
> Behavior can always be specialized by subclassing and re-implementing
> certain messages. I don't get the question.
When I'm reading about a framework, I like to understand what the
expected entry points for modification are (both for my implementation
of clients, and to understand existing clients). When you say "it uses
various rules", I want to establish the limits of what's supposed to be
involved in determining the precise rules. From my browsing, it's just
those methods, I was asking whether there're other intended entry points
there.

[snip]

Daniel