<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:12pt"><div>Dear Adam:<br><br>This seems like a good idea as all of your ideas are and I support it. Lets move forward.<br><br>Perhaps one way to move forward is to help to encourage patches that meet this vision. I am thinking of an example with notes and TODO so that others can take the example subroutine and add patches to follow your vision.<br><br>Charles<br></div><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><font size="2" face="Tahoma"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> "Frisby, Adam" <adam@deepthink.com.au><br><b><span style="font-weight: bold;">To:</span></b> "opensim-dev@lists.berlios.de" <opensim-dev@lists.berlios.de><br><b><span
style="font-weight: bold;">Sent:</span></b> Tue, December 15, 2009 3:04:56 AM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [Opensim-dev] Refactoring SceneObjectGroup - Introducing Components<br></font><br>
<style>
<!--
_filtered {font-family:"Cambria Math";panose-1:2 4 5 3 5 4 6 3 2 4;}
_filtered {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}
_filtered {font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;margin-bottom:.0001pt;font-size:11.0pt;font-family:"Calibri", "sans-serif";}
a:link, span.MsoHyperlink
{color:blue;text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:36.0pt;margin-bottom:.0001pt;font-size:11.0pt;font-family:"Calibri", "sans-serif";}
span.EmailStyle18
{font-family:"Calibri", "sans-serif";color:windowtext;}
span.EmailStyle19
{font-family:"Calibri", "sans-serif";color:#1F497D;}
.MsoChpDefault
{font-size:10.0pt;}
_filtered {margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{}
_filtered {}
_filtered {font-family:Symbol;}
_filtered {}
_filtered {}
_filtered {}
_filtered {}
_filtered {}
_filtered {}
_filtered {}
_filtered {}
_filtered {}
_filtered {font-family:Symbol;}
_filtered {}
_filtered {}
_filtered {}
_filtered {}
_filtered {}
_filtered {}
_filtered {}
_filtered {}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
-->
</style>
<div class="Section1">
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">Bumpity Bump. If I don’t hear
any comments on this, I’m going to assume the proposal is sound and have carte
blanche to break OpenSim at my whim. ;) </span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">(find the original post for the
attachment.)</span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">Regards,</span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">Adam</span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> </span></p>
<div style="border-style: none none none solid; border-color: -moz-use-text-color -moz-use-text-color -moz-use-text-color blue; border-width: medium medium medium 1.5pt; padding: 0cm 0cm 0cm 4pt;">
<div>
<div style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0cm 0cm;">
<p class="MsoNormal"><b><span style="font-size: 10pt; font-family: "Tahoma","sans-serif";" lang="EN-US">From:</span></b><span style="font-size: 10pt; font-family: "Tahoma","sans-serif";" lang="EN-US"> opensim-dev-bounces@lists.berlios.de
[mailto:opensim-dev-bounces@lists.berlios.de] <b>On Behalf Of </b>Frisby, Adam<br>
<b>Sent:</b> Friday, 11 December 2009 3:48 AM<br>
<b>To:</b> opensim-dev@lists.berlios.de<br>
<b>Subject:</b> [Opensim-dev] Refactoring SceneObjectGroup - Introducing
Components</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Hi Folks,</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">I’ve got a fairly complicated proposal to deliver here today
– the short of it is; I’d like to go ahead and replace the current Scene Object
representation model – at a fairly comprehensive & complete level. Some of
you have had the misfortune of working with SceneObjectPart/SceneObjectGroup
and should understand what I am talking about.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">There are several stages to this proposal – but I would like
to talk about today the first big one (and a small outline of the larger
project – the reason for this being some of the later details require a little
more nutting out before I have a complete proposal for them).</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">So – the larger proposal in a nutshell; I would like to:</p>
<p class="MsoListParagraph" style=""><span style="font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal; -x-system-font: none;">
</span></span></span>Merge SceneObjectGroup & SceneObjectPart</p>
<p class="MsoListParagraph" style=""><span style="font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal; -x-system-font: none;">
</span></span></span>Enable full inheritance & linking (ie,
hierarchical linking)</p>
<p class="MsoListParagraph" style=""><span style="font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal; -x-system-font: none;">
</span></span></span>Make programming with SceneObjects possible
& reasonable from the outside (ie have a clean API).</p>
<p class="MsoListParagraph" style=""><span style="font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal; -x-system-font: none;">
</span></span></span>Provide the ability to extend SceneObjects with
“components†to introduce new properties and behaviours.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">The item I’d like to talk about today would be implementing
Components. Components are small C# classes that may be attached to any
SceneObject arbitrarily. </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">A component is any class inheriting from IComponent –
IComponent carries only two properties; a serialisation property (returns the
current ‘state’ for serialisation purposes), and a type property (which
recognises the ‘type’ of component that it is) – components allow you to attach
arbitrary data to an object for the purposes of interacting with a region
module. For instance, a “Mesh†module (which is my current best example) would
have a MeshComponent that included all the extra data to tag an object with
related to meshes – which would get serialised and passed around with the main
object. When deserialized – a “Factory†handles making sure the MeshComponent
is deserialized with the main object.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">I’ve attached a document which is my current state of the
whole proposal which includes some examples & more detail. Please note that
Phase 2 is not finalised yet – and some decisions were discussed about changing
two facets in particular.</p>
<p class="MsoListParagraph" style=""><span style="font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal; -x-system-font: none;">
</span></span></span>Enabling inheritance of components+sceneobject
to make speedy-classes for common use cases (eg PrimObject inherits
PrimComponent and SceneObject)</p>
<p class="MsoListParagraph" style=""><span style="font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal; -x-system-font: none;">
</span></span></span>Allowing more than one factory potentially; for
manufacturing said speedy-classes.</p>
<p class="MsoListParagraph" style=""><span style="font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal; -x-system-font: none;">
</span></span></span>Note that these shorthand classes would still
use the standard .Has / .Get methods; they would just return ‘this’ where the
particular component type is concerned.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">To begin with – I would like to implement components as an
extra non-serialised property of the SceneObjectPart; this will occur very
shortly after 0.7 is tagged; which I would like to do once ROBUST covers all
the main services (I heard something about late-december/early-jan); this first
stage should not break anything in particular – however once that Is complete,
I would like to migrate properties into components in order to modularised the
codebase better.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">An example of this would be PrimData – primdata is unique to
the Second Life use case, and irrelevant to others; in this case, we’ll move
PrimData into a commonly accessed component (eg
“SceneObject.Get<PrimData>.Hollow = 0.9f;â€) – once the move to components
is complete for the common data; then creating the final SceneObject class
which merges SceneObjectGroup+Part should be a fairly painless process.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Please take a read of the document attached for more
information – and I am very keen to hear anyones thoughts as to use cases that
this model will make more difficult; or could not support. The goal with this
project is to make OpenSim support more with less – allowing third party
modules to really take OpenSim as a framework to the next level; and make a
more modular server for other clients & platforms.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Thanks!</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Adam</p>
</div>
</div>
</div></div>
<!-- cg8.c201.mail.mud.yahoo.com compressed/chunked Tue Dec 8 08:02:38 PST 2009 -->
</div></body></html>