<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Andreas,<br>
<br>
I am not sure if you are looking for comments, advice, discussion,
or just posting a notice. I don't want to go off on a tangent
here. I am rather familiar with how and almost why X3DOM does it.<br>
<br>
<br>
Leonard Daly<br>
<br>
<br>
</div>
<blockquote
cite="mid:CAKdk67ur6CsVnQpt1BcVRy7TvOidEwQpkvxnOGt6uPuDZxgksg@mail.gmail.com"
type="cite">
<p dir="ltr">I am working on adding DOM access to inline scenes
for my Cobweb DOM bridge:</p>
<p dir="ltr"><a moz-do-not-send="true"
href="https://andreasplesch.github.io/cobweb_dom/tests/inline_in_inline.xhtml">https://andreasplesch.github.io/cobweb_dom/tests/inline_in_inline.xhtml</a></p>
<p dir="ltr">The idea is to add the external inline scene DOMs to
the main scene DOM as children of the Inline elements. Once
added, the mutation observer picks up modifications of these
children and does not need to do anything other than it already
does for the main scene.</p>
<p dir="ltr">It works well although I do not know how web browsers
deal with large combined DOMs. Also, a small addition to
Cobweb.js is currently needed.</p>
<p dir="ltr">One effect is that one can use CSS selectors with
querySelector to drill down to specific elements in inline
scenes, even through hierarchies of inlined inlines. See
example. This way the DEF names can be used even if they are
identical across scenes. X3D semantics and functioning is not
affected.</p>
<p dir="ltr">X3dom uses a different approach of prefixes to id/DEF
attributes to enable access to elements in inlines. Not sure if
x3dom could use instead or in addition Selectors ? This would
require adding the Inline DOMs to the main DOM but perhaps this
is already almost done ?</p>
<p dir="ltr">So I am considering also adding the same option of a
namespacename prefix to element IDs but the effort would be
really for compatibility. Thinking about it, while possible
probably not a priority unless there is a compelling use case.</p>
<p dir="ltr">X3D has EXPORT/IMPORT to deal with accessing nodes in
inlines. I think the SAI equivalent is roughly that all nodes
are EXPORTed by default and that in addition to a DEF name it
becomes possible to address a node by its path in the scene
hierarchy. Perhaps something to consider for the standard: X3D
selectors.</p>
<p dir="ltr">Andreas</p>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! <a class="moz-txt-link-freetext" href="http://sdm.link/slashdot">http://sdm.link/slashdot</a></pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
X3dom-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:X3dom-users@lists.sourceforge.net">X3dom-users@lists.sourceforge.net</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/x3dom-users">https://lists.sourceforge.net/lists/listinfo/x3dom-users</a>
</pre>
</blockquote>
<br>
<p><br>
</p>
<br>
<div class="moz-signature">-- <br>
<font class="tahoma,arial,helvetica san serif" color="#333366">
<font size="+1"><b>Leonard Daly</b></font><br>
3D Systems Architect & Cloud Consultant<br>
President, Daly Realism - <i>Creating the Future</i>
</font></div>
</body>
</html>