Re: [vos-d] [www-vrml] RE: [x3d-public] X3D Game Engine?

2007-03-15 Thread Reed Hedges
chris wrote: 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

Re: [vos-d] Message handler problem

2007-03-15 Thread Peter Amstutz
That's something that was introduced by the new event tables implementation in 0.24. The solution is to make the registration function a templated class, and for the subclass to call the base class registration function with the subclass type to ensure that the method handlers are associated

Re: [vos-d] Message handler problem

2007-03-15 Thread Reed Hedges
For one thing, apparently you can't do this: class Base { public: virtual void pure() = 0; templateclass T register() { VobjectBase::registerHandlerT(message, handler); } void handler(Message *m) { ... } }; class VirtualDerived : public virtual Base { public:

Re: [vos-d] Message handler problem

2007-03-15 Thread Peter Amstutz
On Thu, Mar 15, 2007 at 04:11:41PM -0400, Reed Hedges wrote: Peter Amstutz wrote: That's something that was introduced by the new event tables implementation in 0.24. The solution is to make the registration function a templated class, and for the subclass to call the base class

Re: [vos-d] Message handler problem

2007-03-15 Thread Peter Amstutz
Try templateclass T register() { VobjectBase::registerHandlerT(message, T::handler); } (note T::handler) This should work, this is exactly how it works in s5. On Thu, Mar 15, 2007 at 04:49:17PM -0400, Reed Hedges wrote: For one thing, apparently you can't do this: class Base {

Re: [vos-d] XOD questions

2007-03-15 Thread Peter Amstutz
No, and it shouldn't do that -- the goal is to have the XML DOM structure reflect the VOS structure in a meaningful way. If you spread essential information for a single vobject all over the document such that it requires that you must process the entire document before being able to do

Re: [vos-d] XOD questions

2007-03-15 Thread Reed Hedges
Peter Amstutz wrote: No, and it shouldn't do that -- the goal is to have the XML DOM structure reflect the VOS structure in a meaningful way. If you spread essential information for a single vobject all over the document such that it requires that you must process the entire document

Re: [vos-d] XOD questions

2007-03-15 Thread Len Bullard
How is XML restricting you? It doesn't care how you use the tree. There are things that look silly to an XMLer that may have a legitimate application. Bits like parent name='' children/children/parent look like someone didn't understand structure given by XML, but they aren't illegal and

Re: [vos-d] XOD questions

2007-03-15 Thread Peter Amstutz
On Thu, Mar 15, 2007 at 06:15:39PM -0400, Reed Hedges wrote: The reason I ask is that I want to load some 3D objects from a COD file, but then insert some non-3d children into one of those objects, and extend its types. This is the kind of thing that VOS is all about :) Practically speaking,

Re: [vos-d] XOD questions

2007-03-15 Thread Len Bullard
Be fair, Peter. It is the X3D instance you have to import, not the schema. The schema is baroque to put it mildly. I'm not sure if it is used for import. BS Contact has a validating switch, but I've not tried it. The schema is useful for the x3d-edit utility, but even then, not too many peole

[vos-d] http://research.sun.com/projects/darkstar/

2007-03-15 Thread HEBLACK, J
http://research.sun.com/projects/darkstar/ Should the page above be checked for the release or is that not something of use here? Project Darkstar is a research effort focused on the design of massive-scale, latency-optimized systems like online games. Written entirely in the Java programming

Re: [vos-d] Message handler problem

2007-03-15 Thread Ken Taylor
Ken Taylor wrote: Ken Taylor wrote: Reed Hedges wrote: Peter Amstutz wrote: Try templateclass T register() { VobjectBase::registerHandlerT(message, T::handler); } (note T::handler) Same problem -- it can't use the method in the base class when the