<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
If we want to watch the birth of a so-called Web 3D, welcome Diva and
welcome Hypergrid. <br>
If we want to have a clone of SL, but with the option of different
grids, welcome all development aid, including Hypergrid, as this is
also a dream of LL. <br>
But if we only want to have a bad clone of
the SL in standalone, we can stop the development now, nothing more is
needed to have a game for some hours. <br>
<br>
For me I support and
I want to watch the birth of the Web 3D, I already attended the birth
of
the web, even before that, I work with some BBSs, then I went to the
web 2, and I do not want to lose the opportunity and maybe I am not the
onlyone, from the inside wanting to attend the birth of the future Web<br>
<br>
Ideia Boa<br>
<br>
<br>
Dahlia Trimble wrote:
<blockquote
cite="mid:ab84ceb10904171241re8aac31od247ff62d9e9b28@mail.gmail.com"
type="cite">Personally I prefer OpenSim in standalone mode, and my
preference is for it to be a personal simulation server allowing
multiple dissimilar clients to attach and share a simulation; one which
may deviate quite a but from the normal SL experience. I realize I'm in
a minority with this position compared to other core developers, and as
such I do a majority of my development and testing in grid mode and
with hypergrid using various viewers, primarily those based on the LL
viewer, but also using other viewers not derived from the LL viewer.
<div><br>
</div>
<div>Many of the users of OpenSim have their own ideas about how the
platform should evolve, and hypergrid appears to (at least anecdotally)
be a popular feature. It also requires substantial changes to the core
architecture for proper implementation, and bringing hypergrid and diva
into core has allowed her to make a substantial improvement to many
parts of the code which deal with standalone and grid operation in
addition to hypergrid. I see no lack of benefit to any of our users
from bringing diva and hypergrid into core.</div>
<div><br>
</div>
<div>Anyway, last I checked, time still only moves forward so please
continue to offer suggestions for improvement and they will be
considered :)</div>
<div><br>
</div>
<div><br>
<br>
<div class="gmail_quote">On Fri, Apr 17, 2009 at 9:14 AM, Mike
Dickson <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:mike.dickson@hp.com">mike.dickson@hp.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Justin,
thanks for clarifying the process. And I certainly understand<br>
the interest in Hypergrid and the energy behind it. Charles your message<br>
was also helpful in highlighting to me what is at the center of my<br>
concern. I agree the development process is somewhat chaotic and things<br>
get hacked in based on interest. That's probably completely to be<br>
expected though it may not make for the best platform going forward.<br>
<br>
Using Hypergrid as an example,my preference would be to do it outside of<br>
core. So let me explain that. Something like Hypergrid is going to<br>
require a different usage model from the original core (different<br>
protocols for "teleporting", now the exploration around inventory, etc).<br>
Rather than have the changes to handle that get introduced into core I'd<br>
have preferred to see something like an RFC that documents what is being<br>
proposed, and what "interfaces" need to be changed in order to<br>
accommodate the new use cases. That RFC gets iterated and the<br>
interfaces evolved to make "hypergrid" possible as a pluggable module.<br>
Over time most likely the set of commonly used modules grows and you<br>
ultimately end up with a core framework and a "core" set of modules that<br>
define what the out of the box functionality of an installation is<br>
(standalone, hypergrid, what have you).<br>
<br>
The obvious problem with this approach is that it requires evolving the<br>
core framework which is not nearly as "sexy" as hacking in new features.<br>
I've done both approaches. Certainly a cool demo can go a long way to<br>
sell a concept and often the change the framework process takes enough<br>
time that prototypes don't happen. It's more work to maintain a branched<br>
copy of core while you evolve your prototype into a set of changed<br>
interfaces that support it. Personally I believe that more disciplined<br>
approach is the key to seeing OpenSim get to 1.0. And ultimately be a<br>
better platform for experimentation.<br>
<br>
So I like the concept of hypergrid. I think prototypes like that need<br>
to exist if only to prove that the community is healthy. But I also<br>
believe that how the "framework" is defined and evolves is equally if<br>
not more important (to me at least).<br>
<br>
Just my 2 cents.<br>
<br>
Mike<br>
<br>
On Fri, 2009-04-17 at 15:35 +0000, Justin Clark-Casey wrote:<br>
> But I do have to also point out that OpenSim development is
largely driven by the interest of the developers (since<br>
> there's no single company behind it). If there's a lot of
development interest behind Hypergrid then this is the<br>
> direction that's inevitably going to progress most. If people
coming along contributing code that enhances different<br>
> architectures, then development will also be driven in that
direction.<br>
<br>
<br>
_______________________________________________<br>
Opensim-dev mailing list<br>
<a moz-do-not-send="true" href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
<a moz-do-not-send="true"
href="https://lists.berlios.de/mailman/listinfo/opensim-dev"
target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
</blockquote>
</div>
<br>
</div>
<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>
</body>
</html>