> Yes I think you are a nut :-)
hehe... let me try to convince you otherwise, and you can take it or leave
it (as you said, its best to do it whatever way works best for the
developer)
Here's some advantages to using Subversion:
1. Every time you copy the module, you're making a copy of all the images
within it. For me, my modules might be as large as 1.7 MB. Well if I
want to keep 20 revisions of that, it starts to add up. In reality, if I
just keep the "changes" from revision to revision, well that doesn't take
up the same kind of space.
2. There are times that I've seen module development taken over for a
module. If someone eventually takes over the modules I'm creating, they
will get the SVN repository and with it an entire history of the project.
With it they will be able to tell why something was done a particular way.
They'll have all revisions of the different graphics (and PhotoShop
sources). They'll have copies of emails shared with the copyright holder
discussing the permission to publicly post a module. They'll have a
change log of all the changes from revision to revision. Vassal doesn't
provide a simple way to do this in the module (but you could put a change
log in the zip file manually. But with Subversion, that change log grows
organically without the need to "maintain" it.
3. There's been times that I messed something up and didn't know what. An
example is that suddenly my module stopped reporting movements. Well
after doing a "svn diff" I could tell instantly what got changed before I
even knew where to find it in the Vassal editor (this was at the start of
my first module).
4. Collaboration. If you have someone thats gonna do your graphics for
you, this is cool! They can check in graphics changes, you do a svn
update and then youve got them merged into your project! Doesnt get
more simple than that.
5. SVN Hooks. I dont like doing repetitive things. But I can make
Subversion do them for me. Everytime I check-in a revision, it builds the
new module, and posts it on my website. I could easily have it email a
group of people letting them know that its available too!
6. Keywords. I can embed my subversion revision information in the Vassal
module, and then when a user reports a bug with my module, I can checkout
that specific revision and work against that (or branch, and possibly
merge those changes to fix the bug into my current HEAD revision).
7. Branching, as above, I can also create a branch to tryout something
completely new, and abandon it if I want, or merge those changes into my
HEAD revision.
8. Tagging. When Ive completed development to the point that I have a
production release, I can TAG that revision, and always be able to get the
source for that specific version that gets released.
Is Subversion overkill? I guess its debatable. But even my smallest
modules will be managed with it, cause it makes things so easy.
Cheers
-Tim
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/vassalengine/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
