open unzipped module

Is it possible somehow to open a module that is not zipped?

I keep my modules unzipped when editing them, to make version management useful and make it easier to edit the image files, but the only way I found to make this practical was to write a pair of scripts to zip-edit-unzip every time.



Messages mailing list …

Post generated using Mail2Forum (

That was unfortunately the conclusion I reached from skimming the 3.0 source code some months ago.

Is it on the roadmap? How do other module makers manage all their data? Keeping everything in a zip is fine for distribution and play of course, but it’s not very practical when developing the module.

I don’t know how it works on your computer, but on mine, when I click on an archive, like a VASSAL module, the OS doesn’t really care whether it’s a folder or an archive. I can edit images within the archive no problem. Gnome on Linux just treats it like a folder that happens to be compressed.

How does it work on Windows?

  • M.

P.S.: How do you activate the middle and right mouse button on a Mac that only has one button?

2009/1/10 pelle < (>

Post generated using Mail2Forum (

I’m on Linux. Didn’t think of that possibility, since I only use the command-line, but that would solve the image editing part. Version management would still be a problem I think, and since I have a workable way to get around this there is no reason for me to change, but it would feel a bit safer to not have to bring everything out of and into the zip file all the time.

If you’re on linux, just write a Makefile that does all this for you.

  • M.

2009/1/11 pelle < (>

Post generated using Mail2Forum (

Actually the scripts are based on a makefile, plus a bunch of makefiles generated from the makefile. But that’s mostly because I did this way back before there was SVG support in VASSAL, so the script also had to render all the changed SVG images to PNG before creating the zip file.


Thus spake “pelle”:

I use a Makefile to handle zipping the archive.

I can see the utility of having VASSAL be able to read a directory as a
module, but then the obvious next request is for VASSAL to be able to
zip a working directory to a module. The problem there is that there could
be all sorts of stuff in your working directory which you don’t want to
(or shouldn’t) include in a module, and VASSAL has no way of knowing what
should go in and what to ignore. (E.g., I’m not particualrly keen on writing
and maintaining code to recognize metadata files for every single revision
control system in existence.)

This makes me think that a Makefile is actually right tool for the job here.


Messages mailing list …

Post generated using Mail2Forum (