[x3d-public] Representation Inspiration [was: Presentation from SVVR2017]

[Andreas Plesch]

On Fri, Apr 14, 2017 at 4:22 PM, Andreas Plesch <andreasplesch at gmail.com>
wrote:

> Date: Fri, 14 Apr 2017 08:54:20 -0700
>> From: Leonard Daly <Leonard.Daly at realism.com>
>> ..
>> <Transform translation='1 2 3' rotation='1 0 0 3.14' scale='3 2 1'>
>>      <Shape>
>>          <Cone></Cone>
>>          <Appearance>
>>              <Material diffuseColor='1 .5 .2' specularColor='.8 0
>> 0'></Material>
>>          </Appearance>
>>      </Shape>
>> </Transform>
>>
>> Could be represented (using an arbitrary, non-XML representation) as:
>>
>> Transform {translation:(1 2 3); rotation:(1 0 0 3.14); scale:(3 2 1);
>>              geometry:Cone; diffuseColor:(1 .5 .2); specularColor:(.8 0
>> 0);}
>>
>> ...
>> For me, what makes this important is that it is a lot like the
>> definitions in A-Frame on an entity. I know that there are a lot of
>> capabilities of X3D that are not being included in this example, but
>> this gives me connection between the two in representing the same objects.
>>
>> I am interested in what others have to say about this connection idea.
>>
>
> Actually, a-frame has transformation hierarchy:
>
> https://aframe.io/docs/0.5.0/guides/#parent-and-child-transforms
>
> A Transform node translates to:
>
> <a-entity position=''>
>   <a-entity rotation=''>
>     <a-entity scale=''>
>       <a-entity geometry='' material='' />
>     </a-entity>
>   </a-entity>
> </a-entity>
>

Actually, this can be combined into

<a-entity position="" rotation='' scale=''><a-box/></a-entity>

since the components are applied in the expected order.

So Transform maps directly into a no-content, only transform <a-entity/>.

However, rotations are given as roll-pitch-yaw in degrees.

https://aframe.io/docs/0.5.0/components/rotation.html

-Andreas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20170414/2f03a70c/attachment.html>