[glob2-devel] questions to where we stand now

[Leo Wandersleb]

hi

working through the 150 mails i got the following questions:

*did we switch to another system in any part yet?
I know we now use the savannah download where i've put files already

*do you count in my server when considering changes?
if mercurial allows distributed repositories maybe we can
put some parts of one repository (data/maps) on different servers.

(sidenote: a friend is actively developing GitTorrent. As far as I
got it, this allows to have git repositories with automated mirrors
in a bittorrent way.)

*notification on changes?
there was talk about a mail on every commit. well great! i want that!
i know my mail client well enough to filter that to a folder i store
mails only for 2 months in. and knowing what's going on is also
motivating to review the changes and hop on the train and code for glob2.

*maps backwards compatibility
to not discourage our (few) map builders I vote to not waste their work.
it can't be so difficult to convert them. if it is, we should have some
project day when we convert them by hand but lets honor this work!

please don't forget the work to be done with the campaign as this will
be broken, too.

*rewrite of subsystems
I agree with Cyrille this must be done in branches. If branches are not
there for exactly that what are they good for after all?

*animated zones
i love them! only point i found is that they cover the workers/requested
indicator so i'd like to see them be alpha50%

*unit allocation
is my main concern now as there are only few real bugs left.
i guess the problem is that the top building fills up its work force
then the next and so on. this way all free workers get distributed over
the top 10% of the buildings resulting in long ways.
Better would be to give only one additional worker to every building
requesting more per time step so minimization on distances takes more effect.

Greetings and thanks for short answers

Leo Wandersleb