[Arp] view events

[fluxs]

>
>
>Would the actual call to a system event be better handled in the
>controller than the view?  This lets the controller know about
>relationships between views without the views themselves needing to
>know about one another.
>

I'm not sure this is what you mean, but if you say that the controller 
shouldn't know about the views relationships, I agree with you. If the 
controller decide that the refering view has to update, it can ask this 
view to do so. But if the case require several views to update, then I'd 
have the controller to update some model state so an event is 
broadcasted to the views and each view knows what it has to do without 
bothering about the others. No relationship between the views or between 
several views and one command has therefore to be implemented.

fluxs