No subject

"Nested dispatchers allow you to create event bubbling like it is
implemented in Javascript. After an event has been posted to all
observers of the dispatcher, it will be broadcasted to all nested
dispatchers.

If you have one dispatcher that dispatches events of a component in
your framework and one dispatcher that dispatches global events that
are triggered by the framework itself it could make sense that you
nest these dispatchers, so that events posted by the component
dispatcher will also be broadcasted to the global dispatcher."

I was just trying to keep all the Pear library functionalities in the
port; I don't see how useful nested dispatchers can be and really just
need one event handler/dispatcher right now. So, I agree with you
about building the simplest things. Sometimes I just go to the
opposite way, I just can't avoid it. :-)

rodrigo