Chris Evans wrote:
> However, like I said I have no experience with this and
I'm not sure
> where to start. Do you mainly work with external
scripts? What about
> version control? Is there a way to keep certain
code/scripts private?
>
> If anyone could nudge me in the right direction, it
would be
> appreciated.
I've been trying to implement some sort of version control
for a long
time. It has been on the shelve for a while, but since last
week I'm
back in development. What I do is have a miaw tool, that
will export a
directorfile to a 99% text based representation, using a lot
of textfiles.
One textfile for the score, a few textfiles per castmember
(depending on
the membertype), a textfile for the publish settings, a
textfile for the
moviextralist etc..
The same tool miaw, can also reliably create .dir & .cst
files from such
a textbased representation. The idea is that you throw the
text based
representation of your director+cast files into a version
control system
(I like subversion), and that because everything is split up
in multiple
textfiles, it gets very easy to work with different
programmers. You
commit into the same repository, and when you want to grab
the other
guy's changes, you update your textbased representation
(which will now
be his & yours merged, with the merging done by your
version control
system), and you recreate .dir & .cst files from the
textbased
representation.
This might be a bit overkill for some projects. If you want
to start
simpler, I think having a way to keep scripts external, so
you can at
least put those into a version control system is a great
first step.
I hope to one day release this tool miaw. For now I'm still
shaving off
the sharp corners. It will be windows only, because it
uses AutoIt3
scripting to get at the hard to reach places of director
(get/setting
publish settings, etc)
Bye, Lucas
_______________________________________________
dirGames-L mailing list - dirGames-L nuttybar.drama.uga.edu
http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l
|