<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>I have updated the 'development' branch on GitHub of XSeen
(<a class="moz-txt-link-freetext" href="https://github.com/DrX3D/XSeen/tree/development">https://github.com/DrX3D/XSeen/tree/development</a>). This branch
supports the 'model' node that brings in glTF geometry, textures,
and animation. It is also possible to start the animation. This is
the full animation that is stored in the glTF file, including skin
deformation based on joint animation. The test example shows that
for the glTF "monster".</p>
<p>This version also adds preliminary support for the A-Frame Asset
manager. This is very similar to DEF/USE except that it is a finer
grain and the assets are pre-declared as opposed to defined in a
node.</p>
<p>All of this is documented at
<a class="moz-txt-link-freetext" href="http://tools.realism.com/specification/xseen">http://tools.realism.com/specification/xseen</a></p>
<p><br>
</p>
<p>I need to tackle animations of various fields. A-Frame does it as
(illustrating with X3D nodes for clarity)</p>
<p><tt><Group></tt><tt><br>
</tt><tt> <Transform translation=...></tt><tt><br>
</tt><tt> :</tt><tt><br>
</tt><tt> :</tt><tt><br>
</tt><tt> </Transform<br>
<TimeSensor .../><br>
<PositionInterpolator .../><br>
<ROUTE ... /><br>
<ROUTE ... /><br>
</Group></tt><br>
</p>
<p>Though A-Frame wraps up all of the X3D nodes needed for animation
into a single node.<br>
<br>
Using that idea with a slight change, I would like to know what
people think of this version. If you don't like, please state why
it is not good.</p>
<p><tt><br>
</tt><tt> <Transform translation=...></tt><tt><br>
<Animate start='' end='' interpolatorType=''
field='translation' ... /><br>
</tt><tt> :</tt><tt><br>
</tt><tt> :</tt><tt><br>
</tt><tt> </Transform></tt></p>
<p>This version puts the Animate node as a child of the node whose
has a field being animated. Multiple Animate nodes could be
children if there are multiple fields to animate. Each node that
has an animatable field could potentially have an Animate node as
a child. This eliminates ROUTEs (at least for this purpose). It is
really clear what is being animated and its range and animation
characteristic. There would be (as yet undetermined) fields so
that multiple Animate nodes could be synchronized.</p>
<p>If you believe that this won't work, please describe a situation
where it would fail - the more detail you can provide, the better.</p>
<p>I am not stating that this will be my solution, but so far it
seems to be "best" (easy to use, coding clarity, extensibility,
and a few less descriptive concepts).<br>
</p>
<p><br>
</p>
<div class="moz-signature">-- <br>
<font class="tahoma,arial,helvetica san serif" color="#333366">
<font size="+1"><b>Leonard Daly</b></font><br>
3D Systems & Cloud Consultant<br>
LA ACM SIGGRAPH Chair<br>
President, Daly Realism - <i>Creating the Future</i>
</font></div>
</body>
</html>