<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Dear X3D community,<br>
<br>
although this is a question concerncing the X3DOM integration model,
I post this quesion to the X3D mailing list, because I know that the
consortium is really interested in adopting this integration model
in a future version of X3D.<br>
<br>
I am be interested in the intended behavior when synchronization
between the DOM representation and internal X3D scene graph is
necessary. The X3DOM paper is not really explicit here.<br>
<br>
Let me use the simple DEF/USE example from x3dom.org as example:<br>
<a class="moz-txt-link-freetext" href="http://examples.x3dom.org/example/x3dom_defUse.xhtml">http://examples.x3dom.org/example/x3dom_defUse.xhtml</a><br>
<br>
The scene has to <Shape> nodes, one defining the Shape below
Transform#bar, one that is reusing the Shape below Transform#bar.<br>
<br>
Now I remove the defining node (using jQuery syntax):<br>
<span style="color: rgb(34, 34, 34); font-family: Consolas, 'Lucida
Console', monospace; font-size: 12px; font-style: normal;
font-variant: normal; font-weight: normal; letter-spacing: normal;
line-height: normal; orphans: auto; text-align: start;
text-indent: 0px; text-transform: none; white-space: pre-wrap;
widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px;
display: inline !important; float: none; background-color:
rgb(255, 255, 255);">$("Transform#bar Shape").remove();</span><br>
<br>
Now I have an invalid X3D scene in the DOM with a single
<Shape> node pointing to a definition that does not exists.
The currently included X3DOM implementation 1.6.2-dev produces an
error, stops rendering (displaying both shapes) and gets inactive (I
guess this is a bug) . Former versions would just render the "USE"
node using the previous definition.<br>
<br>
What the intended behavior? I could think of three behaviors:<br>
<br>
1. The USE node has a dangling reference. Consequently nothing is
rendered at all (corresponds to a reinitialization of the scene
state based on the new DOM representation)<br>
2. The USE node becomes the DEF node (the DOM corresponds to
removing the node via SAI and then serializing the scene)<br>
3. The USE node is still rendering the referenced shape but the
definition does not appear in the DOM (the run-time corresponds to
removing the node via SAI, but the DOM representation differs)<br>
<br>
The first behavior seems the most logical variant for me. <br>
<br>
Any opinions on this?<br>
<br>
Thanks,<br>
Kristian<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<pre class="moz-signature" cols="72">--
_______________________________________________________________________________
Kristian Sons
Deutsches Forschungszentrum für Künstliche Intelligenz GmbH, DFKI
Agenten und Simulierte Realität
Campus, Geb. D 3 2, Raum 0.77
66123 Saarbrücken, Germany
Phone: +49 681 85775-3833
Phone: +49 681 302-3833
Fax: +49 681 85775–2235
<a class="moz-txt-link-abbreviated" href="mailto:kristian.sons@dfki.de">kristian.sons@dfki.de</a>
<a class="moz-txt-link-freetext" href="http://www.xml3d.org">http://www.xml3d.org</a>
Geschäftsführung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender)
Dr. Walter Olthoff
Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes
Amtsgericht Kaiserslautern, HRB 2313
_______________________________________________________________________________</pre>
</body>
</html>