<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
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:<br>
<ul>
<li>modules in OpenSim/Region/Modules get their own private DLL</li>
<li>OpenSim/Region/Environment/Modules get lumped into ONE gigantic
DLL</li>
</ul>
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.<br>
<br>
i think it would make sense to<br>
<ul>
<li>have all region modules living in the same neighborhood (i'd
prefer OpenSim/Region/Modules), the current layout is a bit confusing</li>
<li>break up the region module super-DLL so that each region module
gets a DLL of its own</li>
</ul>
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)<br>
<br>
what is the general opinion on this? i'd be willing to undertake the
refactoring (including tackling the prebuild.xml dragon).<br>
<br>
DrS/dirk<br>
<pre class="moz-signature" cols="80">--
dr dirk husemann ---- virtual worlds research ---- ibm zurich research lab
SL: dr scofield ---- <a class="moz-txt-link-abbreviated" href="mailto:drscofield@xyzzyxyzzy.net">drscofield@xyzzyxyzzy.net</a> ---- <a class="moz-txt-link-freetext" href="http://xyzzyxyzzy.net/">http://xyzzyxyzzy.net/</a>
RL: <a class="moz-txt-link-abbreviated" href="mailto:hud@zurich.ibm.com">hud@zurich.ibm.com</a> - +41 44 724 8573 - <a class="moz-txt-link-freetext" href="http://www.zurich.ibm.com/~hud/">http://www.zurich.ibm.com/~hud/</a>
</pre>
</body>
</html>