<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Johns suggestion of supporting
CSS-style references to source or destination nodes is
interesting. If the usage is restricted to ID values (#foo), then
it is essentially the same as existing X3D. If the usage is for
class values (.foo), then there is the possibility of dynamically
adding or removing nodes from fan-in or fan-out by adding or
removing CSS classes. <br>
<br>
In normal CSS usage, the actual style applied can be a chain of
specific nodes, classes, and IDs. Would the same be done here? For
example <br>
<style><br>
x3d #main_scene .viewpoints <br>
</style><br>
<br>
could refer to all viewpoint nodes in the main scene. An X3D ROUTE
that identified that string as the destination would change all
viewpoints. While this is not hard to do (for example jQuery does
this), it can cause considerable overhead if you have to check the
entire scene graph for matching nodes on every animation step. <br>
<br>
My initial thought is to not go down this route; however, that
just may be my concern on run-time performance and not being
creative enough to see all of the good possibilities.<br>
<br>
<br>
Leonard Daly<br>
<br>
<br>
<br>
</div>
<blockquote
cite="mid:CAGC3UEn2SXzYXkAWGWMJvZg_7fGVrStDgo6kyk+AR-Y4veAssg@mail.gmail.com"
type="cite">
<p dir="ltr">I'll second the proposal. Also I'd like to propose
adding CSS selectors for values of the fromNode and toNode
attributes on ROUTEs if not already in the standard. Thus if
you have a node with id="foo" you could use a route with
toNode="#foo". Class attributes would work similarly for fan in
fan out.</p>
<p dir="ltr">John</p>
<div class="gmail_quote">On Mar 20, 2016 11:23 AM, "Andreas
Plesch" <<a moz-do-not-send="true"
href="mailto:andreasplesch@gmail.com">andreasplesch@gmail.com</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<p dir="ltr">Since Don mentioned that nobody has proposed
introducing an 'id' attribute, let me then propose adding an
'id' SFString attribute to all nodes for x3d 4.0.</p>
<p dir="ltr">The reason is simply compatibility with the DOM
on web pages in the case where x3d nodes are interpreted as
DOM elements.</p>
<p dir="ltr">Andreas<br>
</p>
</blockquote>
</div>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<font class="tahoma,arial,helvetica san serif" color="#333366">
<font size="+1"><b>Leonard Daly</b></font><br>
X3D Co-Chair<br>
Cloud Consultant<br>
President, Daly Realism - <i>Creating the Future</i>
</font></div>
</body>
</html>