Recommended items necessary to design modules for Vassal ?

although the latter items were “interesting to read”, it really still doesn’t answer my underlying question, since there definitely is some code involved in creating a module.

And the example text they have for the one module just doesn’t seem to really get into the nitty-gritty of developing modules (and it seems, based on reading in other forums, the help docs haven’t been updated in quite some time either).

Thus what I was hoping for is a good reference to the code that goes into the modules so one can develop games.

Thanks

Thomas,

*********** REPLY SEPARATOR ***********

On 16/01/2008 at 9:29 PM tomvilfroy wrote:

Not quite sure what you mean by ‘code’ here. ‘Coding’ as such is not required. That is not to say that to get the most out of Vassal, you don’t need to set up an intricate interlocking set of Key Commands and components responding to them. It just requires care, organisation and an attention to detail, but no actual ‘coding’.

Unfortunately, ‘they’ have been so busy developing Vassal that ‘they’ have not got round to writing guidelines for creating modules. In fact, most of ‘them’ do more work building Vassal than build modules, so in fact it is ‘you’ module guys who need to get organized and get the module design doco in order. A new documentation project has recently got underway to address this need.

Your assistance with the documentation project would be gratefully received. Some docs written by a new user covering the issues you have would be very useful. Experienced users often have difficulty writing doco for newbies.

Regards,
Brent.


Brent Easton
Analyst/Programmer
University of Western Sydney
Email: b.easton@uws.edu.au


Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

Thus spake “tomvilfroy”:

Most modules contain no custom code. None. That’s why no one mentioned it.


J.


Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

As for “no code necessary” Well I must be missing something since obviously not everyone is designing the modules either. So there must be something to it.

And saying to “write the docs” when one has no idea doesn’t help matters. It’s one thing when you know WHAT you are doing, totally different when one is lost.

I’m not saying it is trivially easy to do. You have to be prepared to spend some time to learn the system. Many people do not have the mindset to put together a module. It takes many hours of sometimes mind numbingly boring work, but is ultimately very satisfying. But no coding is necessary.

If you are willing to invest the time to learn the VASSAL module editor, you will gain valuable insights into the
shortcomings of the current documentation that we more experienced developers are just not able ti see. If you could share these insights and help the documentation team to incorporate your findings, this would be valuable for all.

Regards,
Brent.


Brent Easton
Analyst/Programmer
University of Western Sydney
Email: b.easton@uws.edu.au


Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)