|
From: Mike Y. <you...@us...> - 2001-09-07 20:26:21
|
I've been examining the design and have a couple of issues and maybe some design changes I'd like to bring up to the group. 1. It appears as though we could run into serialization issues with the serializing of a MapSection with regard to grabbing the state of the EventListenerManager. If not done write the EventListenerManager could end up with a bunch of copied listeners rather then pure references like it should have. Perhaps we should change the EventListenerManager to a MapObjectListenerManger so that it could store objectIDs rather then Listener references. So when unserialized it can resolve correct references of the objects....but then that brings up the issue of the ListenerManager being able to obtain a reference to the MapObjectManager during unserialization....so what do you all think should be done? 2.Should the MapObjectManager manage MapTiles as well? Or should they be the property of a MapSection? 3.Should MapTiles be a MapObject at all? Or perhaps we should remove the coords from MapObject so that MapTiles don't get bogged down with shorts as coords so we could replace them with bytes in MapTiles. Or the owning MapSection could easily enough manage the locations of MapTiles through a 2d array. By doing this we would save a large amount of bandwidth when downloading MapSections to clients. What do you all think? Mike |