|
From: Mike H. <mh...@le...> - 2001-09-27 20:14:15
|
I think the biggest thing that we need to figure out for the ClientAPI is what methods it needs to publish for the client to have access to all the data it needs. I think the ClientAPI should also allow the client to explicity say when to process the next cycle. The methods I can think of right off the top of my head are: public MoveableObject getPlayerObject() - For getting the MapObject that the player controls public void process() - To tell the API to process the next frame. public Collection getMapCluster() - To get the current MapSection and its surrounding MapSection I can't think of anything else right off the bat but I'm sure we'll think of other things. This should be at least enough to get the ball rolling. I've also attached a gif which is the current UML diagram for the ClientAPI. heathm |