<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-AU link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I’d like to attach on another request.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>A document guiding what the changes are – specifically the old
type names, the new type names, if any method signatures have changed, a list
of those changes too.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>There’s a couple of us sitting on the outside with region
modules that will need to be updated accordingly, and I’d have a preference if
this was as painless as possible.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Regards,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Adam<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:
"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> opensim-dev-bounces@lists.berlios.de
[mailto:opensim-dev-bounces@lists.berlios.de] <b>On Behalf Of </b>Dahlia
Trimble<br>
<b>Sent:</b> Monday, 18 August 2008 6:23 PM<br>
<b>To:</b> opensim-dev@lists.berlios.de<br>
<b>Subject:</b> Re: [Opensim-dev] Standardizing types in OpenSim<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'>Thanks for addressing those
issues John :)<br>
<br>
+1<o:p></o:p></p>
<div>
<p class=MsoNormal>On Mon, Aug 18, 2008 at 4:13 PM, Hurliman, John <<a
href="mailto:john.hurliman@intel.com">john.hurliman@intel.com</a>> wrote:<o:p></o:p></p>
<p class=MsoNormal>Thank you everyone who has responded, it sounds like there
is a common<br>
set of concerns that can be addressed.<br>
<br>
* Taking advice from this thread, I split libOpenMetaverse into<br>
OpenMetaverseTypes.dll and OpenMetaverse.dll, with the latter depending<br>
on the former. OpenMetaverseTypes.dll is a very small library (64KB)<br>
only containing UUID, Vector2, Vector3, Vector3d, Vector4, Quaternion,<br>
Matrix4, Ray, Color4, and a static Utils class with common math and<br>
conversion routines.<br>
<br>
* An API freeze will happen immediately on the types library. I'll draft<br>
up a wiki page to put it into more detail, but what this means<br>
specifically is nothing will change names, no function signatures will<br>
change, and the existing functions will behave the same throughout any<br>
new revisions. New structs or functions may be added over time. It's<br>
been in development for two years now, and I think the core<br>
functionality is nailed down.<br>
<br>
* The patch I wrote doesn't attempt to homogenize 100% of the types in<br>
OpenSim. The LSL types serve a different function from the rest of the<br>
types, and the PhysicsVector/Vertex/Triangle set is used in a unique way<br>
that can't easily be replicated with a common type library. However,<br>
there is a lot of room to go from five or six different implementations<br>
down to two or three, and this patch errors on the side of caution in<br>
that regard.<br>
<br>
* libomv (and libomvtypes) will continue to be BSD licensed and do not<br>
include any GPL licensed code. There is a separate GPL library for prim<br>
meshing, but there is no dependency from libomv to the GPL mesher or<br>
back, and the GPL code does not exist in the libomv SVN anywhere. It<br>
will be released as a separate project for those who wish to use it.<br>
<br>
The libomv team has been happy with the move toward independent modules<br>
that break a lot of cyclic dependencies, and is generally going to be<br>
the trend for new development in that library (including a Capability<br>
server implementation). Let me know if anything else needs to be<br>
addressed with the new types library. Some work needs to be done on my<br>
end now to recreate the patch against the new OpenMetaverseTypes.dll.<br>
<span style='color:#888888'><br>
-John</span><o:p></o:p></p>
<div>
<p class=MsoNormal><br>
<br>
-----Original Message-----<br>
From: <a href="mailto:opensim-dev-bounces@lists.berlios.de">opensim-dev-bounces@lists.berlios.de</a><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'>[mailto:<a
href="mailto:opensim-dev-bounces@lists.berlios.de">opensim-dev-bounces@lists.berlios.de</a>]
On Behalf Of Melanie<br>
Sent: Friday, August 08, 2008 7:50 PM<br>
To: <a href="mailto:opensim-dev@lists.berlios.de">opensim-dev@lists.berlios.de</a><br>
Subject: Re: [Opensim-dev] Standardizing types in OpenSim<o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal>Hi,<br>
<br>
I have to second the move for independence. Much time, also mine,<br>
has gone into removing or avoiding libsl references in core. Libsl<br>
has it's place in LLClientStack, where it provides connectivity to<br>
the one client that actually uses that protocol.<br>
<br>
Countless hours have been spent to refactor _from_ libsl tyoes _to_<br>
axiom, and the LSL implementations are different again, and need to<br>
be, if we want scripts to run unmodified, and, thinking onwards,<br>
achieve SL interoperability on a binary level.<br>
<br>
Libomv seems to be a requirement only for the one use case of<br>
emulating SL, for any other scenario not using the SL client, that<br>
lib creates a huge amount of code overhead. Much of it isn't used in<br>
OpenSim as it stands.<br>
<br>
Actually, it should even be broken up further.<br>
<br>
libMetavrseTypes: Quaternion, Vector3, Color4, LLUUID, etc<br>
libPackets: _Packets_.cs and the needed stuff to support using it.<br>
libOpenMetaverse: All the rest, that OpenSim doesn't ever need.<br>
<br>
Then libMetaverseTypes, which should have an API stability guarantee<br>
and whose types should be made serializable again, could be used<br>
throughout.<br>
<br>
libPackets would be used in the LLClientStack exclusively<br>
<br>
libOpenMetaverse would not be needed by this project.<br>
<br>
Melanie<br>
<br>
_______________________________________________<br>
Opensim-dev mailing list<br>
<a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
_______________________________________________<br>
Opensim-dev mailing list<br>
<a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><o:p></o:p></p>
</div>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>