<div dir="auto">I am getting a better sense now that there is a discussion on how to enable the DOM event mechanism for X3D events.<div dir="auto"><br></div><div dir="auto">Currently, as mentioned, x3dom dispatches the same event ('outputchanged') for any x3d output event. An event listener function has to look into the event payload to determine what event happened. </div><div dir="auto"><br></div><div dir="auto">X-ITE does not interact with the DOM. With x_ite_dom.js it does and dispatches dom events for every output event. The dom events are named after the fieldname with a 'x3d_' prefix, for example x3d_isOver.</div><div dir="auto"><br></div><div dir="auto">Routes</div><div dir="auto"><br></div><div dir="auto">I suppose the equivalent to routes for DOM nodes is an event listener which changes the attribute of an element or/and a property of a DOM node. For HTML, routes would not be very useful since the payload value of events is not necessarily designed to become directly the value of an attribute. I think the reason is that events are thought of as part of dynamic, scripted changes and markup and css more for static, declarative content in HTML.</div><div dir="auto">It might be possible to represent (and implement) x3d events and routes with dom events and dom event listeners except for the idea that there is a cascade of many events with a single timestamp.</div><div dir="auto"><br></div><div dir="auto">Not sure how useful this was, Andreas</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br><div data-smartmail="gmail_signature" dir="auto">---on the phone---</div></div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Mar 1, 2019, 7:18 PM Brutzman, Donald (Don) (CIV) <<a href="mailto:brutzman@nps.edu" rel="noreferrer noreferrer" target="_blank">brutzman@nps.edu</a> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thanks for helpful information Andreas. Partial responses:<br>
<br>
On 3/1/2019 2:24 PM, Andreas Plesch wrote:<br>
[...]<br>
> > c. Are ROUTE connections consistent?<br>
> <br>
> Not sure what the question is. Consistent. Perhaps about timestamps?<br>
<br>
Sorry. Intended context is authoring... what does HTML/X3D page/scene look like syntactically, any differences there?<br>
<br>
<br>
> > d. X3DOM is still missing some important/simple Event Utility nodes - is there a problem?<br>
> <br>
> Here are the currently implemented event utility nodes:<br>
> <br>
> <a href="https://github.com/x3dom/x3dom/tree/master/src/nodes/EventUtilities" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">https://github.com/x3dom/x3dom/tree/master/src/nodes/EventUtilities</a><br>
> <br>
> I can help if any are missing or misbehaving but I am not aware of any. Only the dev version has the nodes.<br>
So perhaps we just need to deploy dev versions, and update status spreadsheet?<br>
<br>
X3D Node Inventory Comparison (updated 23 December 2017) shows<br>
implementation coverage of the X3D Abstract Specification<br>
<a href="http://www.web3d.org/specifications/X3dNodeInventoryComparison.xlsx" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">http://www.web3d.org/specifications/X3dNodeInventoryComparison.xlsx</a><br>
<a href="http://www.web3d.org/specifications/X3dNodeInventoryComparison.ddf" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">http://www.web3d.org/specifications/X3dNodeInventoryComparison.ddf</a><br>
<br>
all the best, Don<br>
-- <br>
Don Brutzman Naval Postgraduate School, Code USW/Br <a href="mailto:brutzman@nps.edu" rel="noreferrer noreferrer noreferrer" target="_blank">brutzman@nps.edu</a><br>
Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149<br>
X3D graphics, virtual worlds, navy robotics <a href="http://faculty.nps.edu/brutzman" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">http://faculty.nps.edu/brutzman</a><br>
</blockquote></div>