[simspark-devel] Simspark SVN directory structure

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html style="direction: ltr;">
<head>
</head>
<body style="direction: ltr;" bgcolor="#ffffff" text="#000000">
Hi all!
This is the current
version of my proposed directory structure. Please express your
opinions about it. I think I'll start the migration soon (any
volunteers?!). (Hey, is there any way for migrating rcssserver3d CVs to
simspark in Sourceforge without losing CVS history?)
 

The structure:
spark/ 
    doc/ 
    plugin/
    lib/ 

        kerosin/
        oxygen/ 
        salt/ 
        zeitgeist/ 
    spark/ 
    utility/ 
    test/ 
        coretest/ 
        ... 
        (test apps) 
    data/   
        rsg/  (including common rsg files like boxspheres/ directory,
and probably rsg/jointtest(?)) 
        ros/  (exists only if there are any general ros files, sample
ros files might go inside simspark-utilities/samplesim) 

        scripts/ 

    windows/
    macosX/ 

 

simspark-utilities/
(nobody should use soccer plugins here.) 

        gendot/ 

        samplesim/   (a
simspark clone which runs a simulation with a very simple area in a
simple monitor with no soccer specific content) 

           ros/
           rsg/   
(agents such as legged sphere and car agents are here)(Well, humanoid
agents might be considered as general agents too?!) 

           plugin/ 

        sampleagent/ 
(agentspark, but with no soccer specific behaviours (nao and soccer bot
behaviours) 

        monitorspark/ 
(a simple general monitor: the old monitor spark but with no soccer
specific content, like what is used in samplesim)
(may be called
samplemonitor instead of monitorspark) 

 


gui/  (previously
rsgedit, to be extended as the simspark's GUI (still no comment?!!) 
    res/ 
    doc/ 
 
rcssserver3d/ 
    doc/
    rcssagent3d/   
(agentspark but only with nao and soccerbot behaviours. it might become
a more soccer oriented agent in future?!) 

    rcssmonitor3d/
(monitorspark or ZigoratAssistant, to become a beautiful soccer
monitor!) 

    rcssserver3d/   
(simspark. we could create a simspark symbolic link during installation
as a compatibility feature.) 
    plugin/ 
    data/ 
        rsg/ 
        ros/ 
    linux/ 
    windows/ 
    macosX/
 

 

About the build system:
it seems that we are going to use SCons instead of autotools. If there
is anybody who knows enough about SCons and can do the migration
quickly, we can do it during the SVN migration. If not, I think we
should keep using autotools for now and start creating SCons scripts
simultaneously.
 
And in the current
suggestion, every top-level is a separate package with an independent
build structure. Also, we provide each of them as a separate package.
But, to simplify user experience, we can release all-in-one packages
containing all of these directories which can be built and installed at
once (like the current packages). 

 
 
Good luck,
Hedayat 

</body>
</html>