VOS, according to their thread, is working on a VRML/X3D Importer
_
From: chris [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 14, 2007 7:02 PM
To: [EMAIL PROTECTED]
Cc: www-vrml; [EMAIL PROTECTED]; VOS Discussion;
[EMAIL PROTECTED]
Subject: Re: [www-vrml] RE: [x3d-public] X3D Game
Lauren,
you were clear enough - I was just reinterpreting a bit because I don't
think I have seen
such a thing for x3d. But there are some potential candidates as a starting
point, such as vos, vrspace or deepmatrix, to
perhaps link with an X3D browser. I just don't know enough about them
to comm
On Wed, Mar 14, 2007 at 08:01:47AM -0700, Ken Taylor wrote:
> Ah, I sort of remember a post about that... but I thought it was simply for
> cross-language code generation. But if it's meant to also include
> human-readable documentation, and information for vobject structure
> validation, then tha
A normal message is between two concrete vobjects. An update message is
sent from a concrete vobject to update its replicas. For example, a
property sending out a change notification. It's not a "normal"
message, because the actual C++ object the message is delivered to is
not a concrete Vob
I'm sure if I spend more time tracing the code i could figure this out
myself, but I'm in a lazy mood...
What's the difference in the way Messages and UpdateMessages are handled by
the VOS library? Why can't everything be treated as a plain Message?
-Ken
Reed Hedges wrote:
> Ken Taylor wrote:
> >
> > Next I had an idea that it would be useful to document MetaObjects
in a
> > way that the VOS API doesn't cover. Specifically, things visible by the
> > "external" world accessing a VOS site -- not necessarily things internal
to
> > the VOS library
Reed Hedges wrote:
> OK, cool. We have needed that kind of thing for a long time. We had a
> simple way of doing this called OTD (object type definition) a while
> ago, but then all the code change and all the OTDs went out of date :)
http://interreality.org/wiki/ObjectTypeDefinitions
http://int
Ken Taylor wrote:
>
> Next I had an idea that it would be useful to document MetaObjects in a
> way that the VOS API doesn't cover. Specifically, things visible by the
> "external" world accessing a VOS site -- not necessarily things internal to
> the VOS library
OK, cool. We have needed th
Hey all, just a heads up to a couple things I put on the wiki recently:
First, a braindump about portals. http://interreality.org/wiki/WorldPortals
Comments are welcome!
Next I had an idea that it would be useful to document MetaObjects in a
way that the VOS API doesn't cover. Specifically, t
