[vassalengine-devel] Import module

[Michael K. <mk...@da...>]

I have an almost complete module that imports an ADC2 module into
VASSAL.  So far, it is capable of rendering maps made up of discrete
elements (hexes, hexsides, hexlines, etc.) as well as maps that are
made up of sheets.  It does hex numbering correctly and renders
counters correctly as well.  It also does a separate counter tray that
better mimics the behaviour of the ADC force pools. There are a number
of things it does not do yet and there are a few quirks still. It
actually renders maps made of discrete elements substantially better
than the original program (except for scanned maps, which look exactly
the same).

You can compare these two screenshots:
http://myweb.dal.ca/mkiefte/adc2.png
http://myweb.dal.ca/mkiefte/vassal.png

The reason I did this is because it is excruciatingly difficult to get
my 64-bit Linux machine to run ADC2 (I did get it to work
eventually--but not before I wrote the module).  It will run all of
the ADC2 modules that I have, so it makes me happy at least.

With respect to copyright, my intention was not to write a converter,
but rather something that just read in an ADC2 file such that it would
operate correctly.  It does that.

The problem is that the improvements to this module are coming more
and more slowly.  I've got the bulk of the information in ADC2 files
into VASSAL, but it's the little stupid bits that are starting to take
a lot of time to translate into VASSAL functionality.  If I try to
complete this module, it will bog me down for a significant amount of
time.

What do you guys think?  Should I try to tidy this up for public consumption?

- Michael.