Add support for arbitrary stack of decomposed transform ops to fully dynamic xform

[GoogleCodeExporter]

The SimpleXform has the nice property that it's very easy to use, and it will 
automatically result in an extremely efficient representation in an Alembic 
Archive.  However, it does not allow you to represent a complex compound 
transform stack as found in Maya (eg, joint-orient, pivot, etc.).

The Xform has the nice property that it can exactly represent a complex 
transform operation stack as found in, eg, Maya, and allows for separate motion 
blocks for each transform operation, allowing exactly-reconstructed 
motion-blur, etc.  However, using it is complex and you must identify all 
non-changing components prior to writing values, which is in general impossible 
without first scrubbing through a sample range and checking for static 
properties.

The best of both worlds can be combined into an easy-to-use, efficient 
structure that exactly mirrors an arbitrary, complex stack of decomposed 
transform operations.  This would be most easily done by adding the vector of 
operations to the SimpleXform and using its Defaulted Property mechanism.

Original issue reported on code.google.com by ard...@gmail.com on 19 Jan 2011 at 12:09

[GoogleCodeExporter]

changing to p0 per our meeting

Original comment by scottmmo...@gmail.com on 28 Jan 2011 at 1:03

• Added labels: Priority-P0
• Removed labels: Priority-P1

[GoogleCodeExporter]

Original comment by miller.lucas on 16 May 2011 at 10:38

• Changed state: Verified