<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Can we autogenerate an incrementing browser # and stick it into the outer scenegraph as a div id?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>John</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Sent from <a href="https://go.microsoft.com/fwlink/?LinkId=550986">Mail</a> for Windows 10</p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='border:none;padding:0in'><b>From: </b><a href="mailto:yottzumm@gmail.com">John Carlson</a><br><b>Sent: </b>Thursday, January 31, 2019 9:05 PM<br><b>To: </b><a href="mailto:brutzman@nps.edu">Don Brutzman</a>; <a href="mailto:vmarchetti@ameritech.net">Vincent Marchetti</a>; <a href="mailto:puk@igraphics.com">Richard F. Puk</a>; <a href="mailto:x3d-public@web3d.org">X3D Graphics public mailing list</a><br><b>Subject: </b>Requirement for v4. one X3D element per Frame</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>>Can we think of it in terms of IFrames? An Iframe per canvas? Then put one X3D element per IFrame<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>>>"The main requirement for this comes from scripting...how to access the right field if it’s loaded more than once.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>>>Which may be a good reason not to support fields in Scripts or Scripts at all.” (no Scripts)<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>>“I think the selector in question is on the scene or X3D element. I am not sure if my code fully supports inlines, plus I am reusing the scene (allowed???).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>>>Yet another reason not to support regular JavaScript in X3D.” (Scripts)<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Suggestion for V4: Only support one X3D element per frame/iframe, otherwise we are schizophrenic (They’re coming to take me away, oh no!). 0, or 2 or more X3D elements are allowed, but not supported.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Are there other ways of seeing this? The use case is showing a scenegraph 4 times, twice as X3DOM, twice as X_ITE, twice as JS/DOM and twice as XML, trying to script various elements in scene.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Can someone see a fault in this? Should I start porting my code over to this to see any difficulties? I know IFrames are difficult, but I think we should show our multicanvas apps with multiframes.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Almost bedtime.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>John<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>