i've been looking at where region modules live in our source tree ---
OpenSim/Region/Modules and OpenSim/Region/Environment/Modules --- and
how they get bundled:
- modules in OpenSim/Region/Modules get their own private DLL
- OpenSim/Region/Environment/Modules get lumped into ONE gigantic
DLL
off the 3 modules living in OpenSim/Region/Modules 2 might be good
candidate for forge project: python and SvnSerializer. the third really
belongs to the Terrain region module and seems to contain the default
terrain effects.
i think it would make sense to
- have all region modules living in the same neighborhood (i'd
prefer OpenSim/Region/Modules), the current layout is a bit confusing
- break up the region module super-DLL so that each region module
gets a DLL of its own
this would make the whole region module business much more, err,
modular (and, who knows, perhaps we'd even have one day a build system
like the "make menuconfig" one found in the linux kernel tree)
what is the general opinion on this? i'd be willing to undertake the
refactoring (including tackling the prebuild.xml dragon).
DrS/dirk
--
dr dirk husemann ---- virtual worlds research ---- ibm zurich research lab
SL: dr scofield ---- [email protected] ---- http://xyzzyxyzzy.net/
RL: [email protected] - +41 44 724 8573 - http://www.zurich.ibm.com/~hud/
|
_______________________________________________
Opensim-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/opensim-dev
