>
> libcrystalspace.a exists and "file" detects it just fine, so I don't know
> what's going on there. libzlib.dll is an empty (size-0) file, so I really
> don't know what's going on there.
>
*snip*
> Even stranger -- the first make run made a size-0 wxterangreal.exe.
> Re-running "make" on the ter
In the case of dbus, it probably makes sense to represent dbus
sources as sites and vobjects, and dbus messages become vos messages. If
there's a semantic equivalent to a dbus thing in VOS, you have the dbus
vobject send it to a vobject to translate it.Then all the dbus
concepts map to vos con
On Sun, Feb 25, 2007 at 10:53:16PM -0500, Peter Amstutz wrote:
> Yea, that's reasonable. It should be a core:error method though, and
> you'll want to come up with an error code and maybe raise an exception
> on the caller.
Yes, I'll have it throw an exception. RemoteError I think. What should
OK... now it gets through the whole build without "errors," but it doesn't
end up making the csplugin dll. I get some crap like this during the
csplugin build:
/bin/sh ../../../libtool --mode=link
g++ -O1 -D_REENTRANT -D_MT -mthreads -g -Wall -I/c/vos-projects/current/vos
/inplace/include -mthre
>Assuming you are speaking about the step from VRML to X3D here:
>They have not cut off support for the external API. The thing about X3D
>is, that they've combined what was the EAI (external authoring
>interface) and the Browser Script Interface in VRML into the SAI (scene
>access interface) in X3
Yes, the UDP-based transport protocol is documented here:
http://interreality.org/cgi-bin/moinwiki/moin.cgi/VipDocumentation
I don't expect this to change much, although the implementation may need
to be cleaned up and documented more thoroughly.
On Mon, Feb 26, 2007 at 02:31:49PM +0900, chris
> However, they got too caught up in VRML itself. First
> they build a nice standards 1.0 that let you set up a scene graph. Then
> they add animation, events, prototypes, for nodes and an external api for
> interacting with the scene. All very good, but they also added internal
> scripting
