Hello, A small correction here: Am 1/19/2014 8:58 PM, schrieb Philipp Slusallek: >> [....] like current webtundra too, the case of this diagram: >> https://rawgithub.com/realXtend/doc/master/dom/rexdom-dom_as_ui.svg >> (instead of >> https://rawgithub.com/realXtend/doc/master/dom/rexdom.svg) > > Well, we never store the JS objects, they are only used in the API > from KIARA to communicate the changes to the scene (and back). > We actually do store a high-level representation of an entity as JS object in addition to its XML3D-DOM-object. This has two reasons: First, we can store a reference to the XML3D object in the DOM. By this, we can directly adapt attributes of an entity instance without having to do a DOM lookup by entity ID first. Second, we can also maintain attributes that are not represented in the XML3D object, like for example velocity (which is used to compute position updates which are then propagated to the DOM representation), or in future applications maybe additional semantic information to an entity. The actual scene graph representation of the XML3D object, however, is not stored as separate JS object, but directly copied to the DOM from an external document, which in turn is referenced by an attribute of the entity. The XML3D renderer then renders the object solely from its DOM representation. Best, Torsten
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy