<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
As a data point, I am subclassing SOG. It works great, except for a few
minor glitches in SOG which could be fixed, including in the XML parts.
I'm also doing my own IClientAPI classes.<br>
<br>
As context, I'm developing several simulation visualization modules,
e.g. traffic and scientific simulations. I'll put them in UCI's regions
in OSGrid within the next couple of weeks, if anyone is interested.<br>
<br>
I'm coming to the conclusion that inworld scripting is cute but
ultimately limited by design -- even if the scripting engine was
already solid and on steroids. Plugging things in the server is
infinitely more powerful. So I am extremely interested in how this
discussion about SOG/SOP will pan out. <br>
<br>
I'm looking at OpenSim both as an API *and* as a server, and would like
to continue to do so. The API mode is for developing interesting
behaviors; the server mode is for rich user interaction.<br>
<br>
Diva / Crista<br>
<br>
Stefan Andersson wrote:
<blockquote cite="mid:BLU134-W44109124E6D23CF85DC8ED5630@phx.gbl"
type="cite">
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>Incidentally, that was the aim of the SOG, to push object
changes to its parts, but it just didn't pan out.<br>
<br>
Also, it should be noted that, at the time we were thinking of OpenSim
as an 'API', not a "Server" - I don't know if people today are even
subclassing and specializing SOPs for themselves today - seems everyone
is taking the "attaching behaviours to generic objects" route.<br>
<br>
So maybe a lot of our initial presuppositions on how OpenSim would be
used has been turned moot. I have no problem with that. :-D<br>
<br>
Best regards,<br>
Stefan Andersson<br>
Tribal Media AB<br>
<br>
Join the 3d web revolution : <a moz-do-not-send="true"
href="http://tribalnet.se/" target="_blank">http://tribalnet.se/</a><br>
<br>
<br>
<br>
<br>
<hr id="stopSpelling">
<br>
> Date: Fri, 29 Aug 2008 10:39:55 -0400<br>
> From: <a class="moz-txt-link-abbreviated" href="mailto:sdague@gmail.com">sdague@gmail.com</a><br>
> To: <a class="moz-txt-link-abbreviated" href="mailto:opensim-dev@lists.berlios.de">opensim-dev@lists.berlios.de</a><br>
> Subject: Re: [Opensim-dev] SOG/SOP<br>
> <br>
> Michael Wright wrote:<br>
> > Well where it gets complicated is when all the children need
to have references to their parents. So that the proper positions etc
can be set.<br>
> > <br>
> > That was another task of the SOG, to keep track of the
children and make sure the correct position etc were resolved for the
children. <br>
> > <br>
> > What we had before the current SOG/SOP was a SceneObject that
could have child SceneObjects. But it got very complicated. But again
its likely that was due as much to the implementation, as to the idea. <br>
> > <br>
> > But its actually been a while since I've had a really good
look at the current SOG/SOP so I guess I should do that and see exactly
what is happening where, before I comment too much.<br>
> > <br>
> > I think one thing we all agree on is that the current setup
has problems and there has to be a better way of doing it.<br>
> <br>
> The rel/absolute bits (pos, vel, acc, rot, ang vel) seem to be the
crux<br>
> of why that back reference is needed. And the crux of why we need
to do<br>
> it that way today is that we determine absolute position on read
of an<br>
> attribute.<br>
> <br>
> If we change the problem around and calculate them on write of a
parent<br>
> attribute (i.e. obj.Position triggers a cascade of changes to set
it's<br>
> children's AbsolutePosition), I think we can get rid of the back<br>
> reference. It also has the added benefit of making the read case
just<br>
> reading existing attributes, and take the cost of the reference
frame<br>
> change on the write case, which seems a more logical place to
impose<br>
> that tax.<br>
> <br>
> -Sean<br>
> <br>
> -- <br>
> Sean Dague / Neas Bade<br>
> <a class="moz-txt-link-abbreviated" href="mailto:sdague@gmail.com">sdague@gmail.com</a><br>
> <a class="moz-txt-link-freetext" href="http://dague.net">http://dague.net</a><br>
> <br>
> <br>
<br>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Opensim-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a>
<a class="moz-txt-link-freetext" href="https://lists.berlios.de/mailman/listinfo/opensim-dev">https://lists.berlios.de/mailman/listinfo/opensim-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>