/*Markus Rollmann <rol...@un...>*/ wrote on 02/23/2008
12:47:31 PM:
> Hi Hedayat,
Hi Markus,
> Thanks for moving the changes from the simspark to the soccer3d CVS ;-)
:) You're welcome!
> The problem is that you moved the changes in one single step into the
> soccer3d repository. That makes it a bit hard to review and discuss
> these changes. I'll try to look through the changes and test the build.
There are some reasons for it:
1. I didn't know that they need discussion, or if anybody is interested
in that! ;)
2. I liked to finish this ASAP since I won't have that much free time in
the following weeks and I should concentrate on other things for awhile.
3. As far as I know, they don't change the functionality of the current
server. They just provide many features which can be used. At least I
tried my best to retain 100% compatibility with the past.
Thanks for looking through the changes and testing the build. That's
really needed.
> It would be cool to move rsgedit over as well ;)
:) I may do it soon. However, from now on, I'll try to convince you that
the best thing for now is to port soccer3d updates in the current
simspark code to simspark (some bug fixes, some new features, and some
compile fixes) and drop the core libraries (oxygen, kerosin, zeitgeist)
and then the general plugins (in spark/plugins) from soccer3d repository ;)
Then, regardless of the speed of transition to simspark, there will be
always one code tree distributed in simspark and soccer3d repositories.
Porting code from one repository to the other is really undesirable. It
brings the sense of wasting a lot of time without doing anything new :(.
Free time worths a lot more! Personally, I'm almost sure that I'll never
port any new changes from simspark to soccer3d!
And something I forgot, I didn't port anything from simulation/parts to
soccer3d. Is there anything there that should be ported to soccer3d?
Thanks again,
Hedayat
>
>> As far as I know, the current CVS HEAD should be completely working.
>> You may notice that you get 2 new errors when running the server,
>> that's fine! :) Those are generated by sparkResetScene (spark.rb),
>> and since at the startup there is still no simulationserver when
>> sparkResetScene is called, it prints those errors.
>
> I'll look into that.
>
> cheers,
> Markus
>
|
