It seems that what you want could be done with yet another
react-to-attribute-change trick.
We already have:
- monitors called on a change in an attribute of a given name, globally
- watchers called on a change in a given collection attribute on a given
item (synchronous and asynchronous)
- watchers called when an item of a given kind is created, deleted or
stamped
- watchers called when a given item changes
- onValueChanged() called on an item when any of its chandler attributes
change
How about getting rid of onValueChanged() which is too big of a hammer and
replace it with what I think you're suggesting - maybe I'm oversimplifying
here - namely a new attribute aspect naming a method to invoke on an item
when the attribute changes ?
The same method name could be used for multiple attributes, of course.
From the usage I've seen, onValueChanged() is not really needed anymore if we
replace it with this new attribute aspect.
Andi..
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
