Toni Alatalo kirjoitti:
sense, the experiments with MXP now are interesting (i started testing
adding support to that to openviewer btw to learn more, dunno if will
have time to complete that soon but we'll see).
well now can login to mxp server with openviewer, just inject an avatar
to
: [Opensim-dev] On solving Authentication and such
By the way,
I've been talking to some people lately around various viewer and protocol
issues, and I have come to realize that we are apparently locked into the
mindset of having the viewer being the 'community application' - I would
propose
+1 from me too. The 2d ui can start as sub set of html for example.
___
Opensim-dev mailing list
Opensim-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/opensim-dev
I think I didn't understand the proposal... or maybe yes.
You are proposing to separate 3D rendering code from 2D (windows and so on)
on the viewer to allow them to choose what rendering engine to use? +1 from
my part
2009/2/24 Tommi Laukkanen tommi.s.e.laukka...@gmail.com
+1 from me too.
If that is the proposal, +1 from me too. to can choose a rendering
engine like OGRE/COLLADA allow a significant improvement in the
client.
2009/2/24 Impalah impa...@gmail.com:
I think I didn't understand the proposal... or maybe yes.
You are proposing to separate 3D rendering code from 2D
I think the proposal is exactly the opposite, at least for the time
being. That is, let's use whatever the LL viewer already has for 3D
rendering, and let's move the non-3D features out onto Web applications.
Gustavo Alberto Navarro Bilbao wrote:
If that is the proposal, +1 from me too. to
There's a fine line to draw here, and if we go too far the immersion
feeling will be affected. So the difficult thing in this approach will
be to draw that line. It would be an interesting academic exercise to
pull out ALL the features from the viewer except its 3D rendering
engine-ness.
I
Hi,
On Tue, 24 Feb 2009 09:45:27 -0800
Diva Canto d...@metaverseink.com wrote:
I think the proposal is exactly the opposite, at least for the time
being. That is, let's use whatever the LL viewer already has for 3D
rendering, and let's move the non-3D features out onto Web
applications.
Definitely a +1.
If one is using a 3d system like Ogre, you could use webkit to display
on the 'overlay' surfaces (Ogre has this concept of transparent
overlays over the 3d view). Even the interface to the viewer proper
could be all web pages and AJAX goop. Then any web page -- any
interface to
First, a big + the separation of concerns. Then some brief remarks and
comments:
Mike Mazur kirjoitti:
This means that the server will provide one client stack implementing
one protocol that deals only with 3D information. Avatar movement,
scene description, agent updates, prim updates, etc.
10 matches
Mail list logo
