Re: [simspark-devel] Transition from rcssserver to simspark, please help!

[Markus R. <rol...@un...>]

Hi all,

Hedayat Vatankhah wrote:
> The current status of having simspark sources in two places (both 
> simspark and sserver projects) is annoying and will waste time. I'm 
> interested to remove this redundancy, but I need some help to start:
> 
> 1. What is the purpose of simspark precisely? I thought that it is going 
> to hold the core libraries, but I found some soccer plugins there. I 
> want to know if you are going to move rcssserver to simspark completely 
> or not? (Which parts of the rcssserver are going to be a part of 
> simspark and how?)

the original intent was to move the entire codebase over to the simspark 
repository.

Reasons were are modified layout of the source tree. It should have a 
more strict separation between the server and the hosted simulations (in 
the soccer3d CVS generic and soccer specific plugins are in on place) 
and some further cleanups.

> 2. What is the current status of simspark? (about different branches and 
> any other related things)

In effect the new CVS was used to develop some more experimental 
features like

- ODE space and composite body support
- an additional scene importer (RoSim XML)
- compile fixes and cleanups (the server builds and runs under windows)
- some gui specific plugins (input plugins for wxWidgets events)
- rsgedit (a gui for running spark simulations)

Meanwhile most cleanups and features (notably ode space and composite 
bodies) found their way back to the soccer3d CVS. What's left in the 
simspark CVS is a somewhat streamlined directory layout and some more 
cleanups that could also be ported with some effort.

> 3. What should be done?!

We should decide for one repository. Going with the simspark repo 
requires initial porting effort to move the current soccer3d simulation 
and get it running- a lot of work to reach status quo again...

I'd vote for staying on the soccer3d repo for the time being.

regards,
Markus