Updating from earlier (pre 4.0) versions of Ascape

We have tried to preserve as much backward compatibility as possible. Still, this is a the first release in over eight years, and there have been many many changes to Ascape, so it is quite possible that some changes will be needed, especially is you have heavily customized Ascape views and scapes. To convert an existing model, try the follwingattempt to compile it with the new version of Ascape. .

The package hierarchy has changed to org.ascape from one of edu.brook, com.bios, or com.nutech. :) The easiest way to deal with this in a mdoern IDE is probably to delete all of you import statements and then use your IDE's auto-import feature (in Eclipse that is Source:Organize Imports) to attempt to find the re-packaged classes. You may have to do some of this manually.
In 3.0 a new more flexible Scape space mechanism was introduced. You will need to replace all patterns like:
```
new ScapeArray2DMooore()
```
with:
```
new Scape(new Array2DMoore())
```
Simple, eh?

Many methods have been deprecated -- for greater flexibility you should migrate to the replacement methods as soon as is practical. Hopefully these will imprOve the code. For example:

        CellOccupant[] neighbors; 
        neighbors = getHostCell().getNeighboringOccupants(); 
		for (int i = 0; i < neighbors.length; i++) { 
			currScore = ((CoordinationGamePlayer)neighbors[i]).totalSc ore; 
			 if (currScore > bestScore)  { 
				  bestScore = currScore; 
				myColor = ((CoordinationGamePlayer)neighbors[i]).getColor(); 
 		 	} 
		}

        List neighbors = findNeighborsOnHost();
        for (Object neighbor : neighbors) {
            currScore = ((CoordinationGamePlayer) neighbor).totalScore;
            if (currScore > bestScore) {
                bestScore = currScore;
                myColor = ((CoordinationGamePlayer) neighbor).getColor();
            }
        }

And actually there is a much better way to do even that now, but we won't get into that...

The onSetup() and similar methods are no longer used. Use the scapeSetup(ScapeEvent event) pattern instead.
Replace Scape.addAgent() with Scape.add().
All of the Event and Listener classes have been moved to ..ascape.model.event. You may need to update your imports to reflect this if you work with listeners directly. A new class, UserEnvironment, takes over many of the functions of ViewFrameBridge. Typically you will just need to replace getViewFrameBridge() with getScape().getUserEnvironment(), or in some cases, simply UserEnvironment.
If you run into any insurmountable difficulties, post a message to the Ascape forums so that we can sort them out.