> As you've discovered, we've got a few conventions. :-) Some things > extend ArgoEventListener in an event-specific manner and others > implement PropertyChangeListener directly. Generally I prefer the > former style, but I'm not really thrilled with the central event types > registry in ArgoEventTypes since this seems to introduce more coupling > than is desirable. Having said that, I think extending > ArgoEventListener is the right way to go for this since it will keep > things consistent. What do others think?
I really don't like the way we've used PropertyChangedEvent, I think that was not the best decision for listening to changes from the model subsystem. It makes a class that's listening poorly self-documenting as it's not actually clear what it is interested in listening to. It can also result in bloated methods dealing with too events from different subsystems. I'm don't know what advantage there is of having our own base events and listeners or a central registry. Just extending EventListener and EventObject I would have thought would be fine. But then we have a third way. Bob. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
