This uses the same class registration pattern (implements xx.handler) as the bubbling event dispatch. e
It'll be mostly used to transmit information/changes across model transformation boundaries, avoiding tight coupling.
Use case: BeanEditor contains a field bindable which is transformed to FormModel.
We want to be able to disable the BeanEditor (say during rpc dispatch) - and part of the implementation has the FormModel change its rendered DOM attribute 'inert'
* BeanEditor.inert broadcasts an InteractionEnabled (t/f) message
* FormModel picks it up (receives InteractionEnabled) and modifies its inert attr
Implementation
During a given layout algorithm run, descent messages are cached and fired if a child receiver requires one (once all its binding calls are complet)
To avoid scanning a subtree on event emission, event receivers are attached to any ancestors which emit broadcast events of a given type
This is somewhat similar to listening on a store change - but it's more strongly typed and lets the broadcaster determine what it's willing to publish
It's also a little similar to Java ScopedValue - Alcina LooseContext - in that it's goal is to cross layers in a (type)-safe-ish way
This uses the same class registration pattern (implements xx.handler) as the bubbling event dispatch. e
It'll be mostly used to transmit information/changes across model transformation boundaries, avoiding tight coupling.
Use case:
BeanEditorcontains a fieldbindablewhich is transformed toFormModel.We want to be able to disable the BeanEditor (say during rpc dispatch) - and part of the implementation has the FormModel change its rendered DOM attribute 'inert'
Implementation
This is somewhat similar to listening on a store change - but it's more strongly typed and lets the broadcaster determine what it's willing to publish
It's also a little similar to Java ScopedValue - Alcina LooseContext - in that it's goal is to cross layers in a (type)-safe-ish way