george973 wrote:All Android Apps are written in Java. Unfortunately it doesn't have the full swing implementation but just a cut down selection of views. Since it tends to run on touch screen devices, the way a user does things is different.
Probably only way to support VASSAL would be to split client into front end GUI/back end modules and use a different GUI implementation of tablets - perhaps with the back end running separately on a server rather than on the device. Although with phones having 16Gb of "Disk" and 750Mb of ram there's probably enough power there to run VASSAL.
Splitting the client would allow implementation on iPads etc since only need port Java VM - no swing required to run back end and the front end could be written in Objective-C and connect via TCP to back end.
Splitting the client in two is a lot of work though. I had a look at doing this with Map and took a month's work to get 50% coding done with all the related stuff in VASSAL.build.module.map. The problem is that all the GUI stuff is intertwined with the back end stuff.
I have a android tablet. It would be great if I could vassel with it. What all would be required to get it working in the android operating