<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:1075739501;
mso-list-type:hybrid;
mso-list-template-ids:-1805997526 -1 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:\F0D8;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;
mso-fareast-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.5pt;color:#333333;background:#F9F9F9'><o:p> </o:p></span></p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='color:#333333;margin-left:0in;mso-list:l0 level1 lfo1'><span style='font-size:11.5pt;background:#F9F9F9'>Interchange profile hint: this field may be ignored.<o:p></o:p></span></li></ul><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>OK, some good stuff, and a has been extended and retracted over the rears. </p><p class=MsoNormal>So in this, the target could be an inline ‘defname.url’ and the new url would replace the old. Looks like even without any use of routes at all. Just have one anchor in any part of the scene refer to an inline name and url anywhere else in the scene, but not by propagating an event from the sensor to a route then to the node, but by essentially directOut of url from the anchor to the node. This may be more of a problem in the scenegraph and event processing than you anticipate. </p><p class=MsoNormal><o:p> </o:p></p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'><span style='font-size:11.5pt;color:#333333;background:#F9F9F9'>Hint: set parameter to target=frame_name to load target url into another frame.</span></li></ul><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I guess the target is intended to be some url in some node in the current scene. </p><p class=MsoNormal>There is no such thing as an x3d frame in this html usage of the term so taken literally the target must be a frame in the current html page hosting a frame that hosts the current scene. </p><p class=MsoNormal>Very unlikely this will work without a script. </p><p class=MsoNormal>However, I think this addition to x3d anchor functionality is Not Even Worded close to what you are talking about, and I say has not been thought about with enough detail to get any traction at all. </p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Wow, the html a is so cool look at all the stuff, style, and events it carries. Opps well all that stuff is more that I need or want. </p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>So I am up for discussing how to change anchor to allow targeting a url field of another node in the same context by adding target- where default is _self and the target would be inlinenode.url but please notice the syntax and event baggage of the html A. </p><p class=MsoNormal>At first this seems pretty simple but it can get overly complicated fast when instead technically the best way is to use some of the lower level more versatile x3d touchsensors along with routes. </p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Instead you want the anchor to be able to go spraying stuff around the scene like you can only otherwise do with a directOut script. X3d wants to be more organized and organizable than that. </p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>To summarize, it sounds like a simple fix but since x3d has lots more features to cover this operation than does html, then menolike and advise to use other nodes to do this. </p><p class=MsoNormal>Good Luck and Have Fun, </p><p class=MsoNormal>Joe</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:awonnink@hotmail.com">Albert Jan Wonnink</a><br><b>Sent: </b>Saturday, January 26, 2019 7:58 PM<br><b>To: </b><a href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a><br><b>Subject: </b>Re: [x3d-public] Anchor target within scene: code example</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hi Joe,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>“<span style='font-size:10.0pt;font-family:Consolas;color:black;background:white'>There is not any html anchor that tells you to exchange one part of the page for another. You need to use the DOM for that, just as in x3d you use the SAI.</span>”<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Surely you know that code like<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><a href=’someurl’ target=’someframename’> …<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>just does that, replace the content of the frame with another. But if you mean that an anchor cannot do this for other html content, then of course you are right. That is why I use the (i)frame in my argument for comparison. And imo the inline tag could be used for this.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>“<span style='font-size:10.0pt;font-family:Consolas;color:black;background:white'>I guess I haven’t seen that example. But the x3d or html anchor does not care whether an iframe or an inline is referenced, it just knows to unload the current document and load the new, or that the scene is the same, but the viewpoint is new.”<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:Consolas;color:black;background:white'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:Consolas;color:black;background:white'>The specs here (<a href="https://doc.x3dom.org/author/Networking/Anchor.html">https://doc.x3dom.org/author/Networking/Anchor.html</a>) clearly allows referencing an (i)frame on the 2d webpage from an anchor within x3d: “</span><span style='font-size:11.5pt;color:#333333;background:#F9F9F9'>Hint: set parameter to target=frame_name to load target url into another frame.</span><span style='font-size:10.0pt;font-family:Consolas;color:black;background:white'>”</span><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Albert Jan<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>