<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Also note that this is built into web browsers now, not only JQuery:<div class=""><br class=""></div><div class=""><a href="https://developer.mozilla.org/en-US/docs/Web/API/Document/querySelectorAll" class="">https://developer.mozilla.org/en-US/docs/Web/API/Document/querySelectorAll</a></div><div class=""><br class=""></div><div class="">I can imagine it would be pretty fast in native code, if that’s what it is.</div><div class=""><br class=""></div><div class="">John</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 20, 2016, at 8:46 PM, John Carlson <<a href="mailto:yottzumm@gmail.com" class="">yottzumm@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Thanks for commenting Leonard, I thought it was going to be left behind in the id/class discussion<br class=""><br class=""><blockquote type="cite" class="">On Mar 20, 2016, at 8:32 PM, Leonard Daly <<a href="mailto:web3d@realism.com" class="">web3d@realism.com</a>> wrote:<br class=""><br class="">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 class=""><br class=""></blockquote><br class="">Only check the scene graph when the members of the selection change.<br class=""><br class=""><blockquote type="cite" class="">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 class=""></blockquote><br class="">Agreed. Let’s wait for a good use case. Necessity is the mother of invention. We can write a route expander in the meantime.<br class=""><br class="">John<br class=""><br class=""></div></div></blockquote></div><br class=""></div></body></html>