> >We can have Behaviors to modify only the Click method, only MouseMove > method, etc. Or Behaviors to modify security rights/levels. Or anything > else we can imagine. And we can play with them as we want at RUNTIME. > > I fail to see at this stage why I would want to 'modify' these > methods, and at runtime, meaning that the response to an event > would be different depending on a particular state of the program. > Interesting, but not high on my list of priorities (the dyno in me > probably! :)). Well, the security reasons might urge you to have different behaviors for the same class of objects, depending on user level. Sounds like a pretty neat idea to me; having observed some discipline while using it we might obtain nice things on existing apps by just adding some behavior properties to existing forms. The side effect is that we've made the full circle: after thirty years, we get back to the program capable of modifying itself on the run :>