<!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">
Justin,<br>
<br>
The hypergrid is a great example of how to make new architectures on
top of opensim, but it's not a good example of how to write
applications with opensim, which is what most people will want to know.
Technically, there is no difference between one and the other, it's all
done by using and extending opensim. Psychologically there is a big
difference between something like the hypergrid and something like the
traffic simulation app. Most people will feel that they want to write
something like the traffic simulation, but the hypergrid feels like
infrastructure that they aren't interested in doing.<br>
<br>
So what we really really need is a few good examples of app-flavored
modules. I have two in line for this, I will use them to write a
tutorial. But not before the API stabilizes. For example the change you
guys are doing in SOG/SOP is critical for these apps; they extend SOG.
(I'm all for improving the SOG situation, so don't read this as a call
for not making the proposed changes... I'll just wait.)<br>
<br>
Crista<br>
<br>
Justin Clark-Casey wrote:
<blockquote cite="mid:491C39CB.8080007@googlemail.com" type="cite">
<pre wrap="">Michael Wright wrote:
</pre>
<blockquote type="cite">
<pre wrap="">+1000000.
I think we all/most want to see core smaller than it is. Its just
getting to the point of having stable API's so we can start moving
things out.
And totally agree that we should do more to get the message out that
opensim is a platform, that just has a reference application included
that makes it act basically like SL.
</pre>
</blockquote>
<pre wrap=""><!---->
+lots
I think to some extent this is also pending a revision of the region module system to make it easy to plug in external
modules with their own configuration files (OpenSim.ini.example is getting to be a monster). Of course, we've been
saying that for ages now - consider it a long feature lead up :)
I've never actually tried to build a completely external region module myself so perhaps it's not as tough as I think.
Cristina, your forge code will provide a good example of this (assuming that you have region modules).
Of course, from your work it sounds like there are also framework areas that could be better modularized.
</pre>
<blockquote type="cite">
<pre wrap="">
*/Cristina Videira Lopes <a class="moz-txt-link-rfc2396E" href="mailto:lopes@ics.uci.edu"><lopes@ics.uci.edu></a>/* wrote:
Gosh, I don't know how many more times I have to say this: the
opensim API is just wonderful! Just look at the hypergrid code, and
you will see. It's all done via inheritance, delegation, and region
modules. Rather than looking at it as an annoyance, I have found it
to be an exciting constraint to code it up with minimum interference
on the core. All patches I have submitted in the last couple of
weeks have been to make things friendly for subclassing, that's all.
My only comment to you core developers is that I see several things
in the core that probably shouldn't be there. Cores should be as
small as possible.
When people finally realize that opensim is only casually an
application that looks like SL but, more importantly, a framework
that can be extended, I think we will start to see a lot more
deviation from SL. The message is still not out there. (I promised
to put out my traffic sim code as an example, but then the hypergrid
got control over me...)
Diva / Crista
<a class="moz-txt-link-abbreviated" href="mailto:stefan@tribalmedia.se">stefan@tribalmedia.se</a> wrote:
</pre>
<blockquote type="cite">
<pre wrap=""> Quoting James Stallings II <a class="moz-txt-link-rfc2396E" href="mailto:james.stallings@gmail.com"><james.stallings@gmail.com></a>:
</pre>
<blockquote type="cite">
<pre wrap=""> This is the interoperability fast-track - I love it.
</pre>
</blockquote>
<pre wrap=""> Personally, I love the fact that Diva claims it's all been very simple
to code, due to the modularity and malleability of OpenSim. We should
all pat ourselves on the back and keep the torch of decoupling high
wherever we run.
<3
/Stefan
_______________________________________________
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>
<pre wrap=""> _______________________________________________
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>
------------------------------------------------------------------------
_______________________________________________
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>
<pre wrap=""><!---->
</pre>
</blockquote>
<br>
</body>
</html>