Here's a link to the first of what I'd like to call our "development"
series of builds, indicated by SVN version number:
In this build, you'll find implementations of:
* RFE #1637163: make VASSAL faster, more responsive
* RFE #1566177: Implement JAI tiled images to reduce memory usage
* RFE #1565958: Zooming to larger than 100%
Specifically, it should now be possible to load much larger modules
now than before, due to memory-sensitive caching and writing large
images to disk.
Additionally, you'll find the following known issues:
* Requires Java 1.6+ because I haven't added the SwingWorker.jar yet.
* Much diagnostic stuff spewed to the terminal.
* Occasional weird behavior when loading Board images: Whenever the
first Board image gets in the queue ahead of the button images,
repaint performance is bad and I haven't been able to figure out why
* Memory-mapped temp files might not be cleaned up if VASSAL crashes.
* Large modules will require quite a bit of disk space at runtime. If
you needed 1GB of heap to run a module using the 3.0.x series, then
there's a good chance that you'll be able to run the module with only
512MB of heap (or less) now, but with 1GB of disk space used by temp
files while VASSAL is running. I don't work miracles, the storage has
to come from somewhere...
* It's almost certainly the case that you'll be able to find bugs I
haven't spotted yet. Let me know what you find so we can move toward
a "testing" release.