From: Ian S. <Ian...@ar...> - 2003-04-11 23:34:45
|
Hi, In my work on FeatureCollection, I noticed the CollectionListener interface. I know that its been stated that this package needs work (in general) and I think this is one area where thats true. The CollectionListener interface specifies one method : collectionChanged(CollectionEvent ce) And CollectionEvent is a very simple extension of EventObject which only provides support for the source of the event (in this case the FeatureCollection) although the constructor allows any Object. I propose the addition of some more specific details because of the following: Any code interested in "listening" to a FeatureCollection will want to know what the change was specifically. Either Features were added or Features were removed. This information can be extracted through complex, intensive calculations like getting all the features in the collection, iterating through them and comparing them with what the listener already has. It would be a lot easier to just pass the knowledge of what was added or removed to the listener directly. This would not require changes in the listener interface, only the CollectionEvent. Any thoughts? Ian |