<div dir="auto">You mean like an X3D JSON to A-frame translator? I could go for that. Where's the A-frame spec or a complete example or set of examples that covers everything?</div><div class="gmail_extra"><br><div class="gmail_quote">On Apr 14, 2017 4:23 PM, "Andreas Plesch" <<a 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"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Date: Fri, 14 Apr 2017 08:54:20 -0700<br>
From: Leonard Daly <<a href="mailto:Leonard.Daly@realism.com" target="_blank">Leonard.Daly@realism.com</a>><br>..<br>
<Transform translation='1 2 3' rotation='1 0 0 3.14' scale='3 2 1'><br>
<Shape><br>
<Cone></Cone><br>
<Appearance><br>
<Material diffuseColor='1 .5 .2' specularColor='.8 0<br>
0'></Material><br>
</Appearance><br>
</Shape><br>
</Transform><br>
<br>
Could be represented (using an arbitrary, non-XML representation) as:<br>
<br>
Transform {translation:(1 2 3); rotation:(1 0 0 3.14); scale:(3 2 1);<br>
geometry:Cone; diffuseColor:(1 .5 .2); specularColor:(.8 0 0);}<br>
<br>...<br>
For me, what makes this important is that it is a lot like the<br>
definitions in A-Frame on an entity. I know that there are a lot of<br>
capabilities of X3D that are not being included in this example, but<br>
this gives me connection between the two in representing the same objects.<br>
<br>
I am interested in what others have to say about this connection idea.<br></blockquote><div><br></div><div>Actually, a-frame has transformation hierarchy:</div><div><br></div><div><a href="https://aframe.io/docs/0.5.0/guides/#parent-and-child-transforms" target="_blank">https://aframe.io/docs/0.5.0/<wbr>guides/#parent-and-child-<wbr>transforms</a><br></div><div><br></div><div>A Transform node translates to:</div><div><br></div><div><a-entity position=''></div><div> <a-entity rotation=''></div><div> <a-entity scale=''></div><div> <a-entity geometry='' material='' /></div><div> </a-entity></div><div><div> </a-entity></div></div><div><div></a-entity></div></div><div><br></div><div>While a-frame has all the a-nodes (a-sphere ..) it is best to really think about those as shortcuts to entity plus components <a-entity geometry='sphere'>.</div><div><br></div><div>So shape translates to <a-entity geometry='' material='' /></div><div><br></div><div>DEF and USE translates more or less to mixins:</div><div><br></div><div><a href="https://aframe.io/docs/0.5.0/core/mixins.html" target="_blank">https://aframe.io/docs/0.5.0/<wbr>core/mixins.html</a><br></div><div><br></div><div>The hardest part may be to reflect the x3d event flow but I developed some ideas when I first explored a-frame and remember that it looked not unpromising (but I did not write down or even conceptualize anything more concretely). Components can be written to just listen to (in), or just emit (out) events, or do both (in,out). There is an initialize phase.</div><div><br></div><div>Prototypes translate more or less to this non core component:</div><div><br></div><div><a href="https://github.com/ngokevin/kframe/tree/master/components/template/" target="_blank">https://github.com/ngokevin/<wbr>kframe/tree/master/components/<wbr>template/</a><br></div><div><br></div><div>One question is if it would be better/easier/robust to develop a x3d -> aframe translator or actually define the x3d nodes as custom a-frame entities.</div><div><br></div><div>Andreas</div><div><br></div><div><br></div><div> </div></div>
</div></div>
<br>______________________________<wbr>_________________<br>
x3d-public mailing list<br>
<a href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a><br>
<a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" rel="noreferrer" target="_blank">http://web3d.org/mailman/<wbr>listinfo/x3d-public_web3d.org</a><br>
<br></blockquote></div></div>