Small code restructuring to Houdini reader/writer for "hook in" code points for studio-specific workflows

PiRSquared17 / alembic

Automatically exported from code.google.com/p/alembic

Other

0 stars 0 forks source link

Small code restructuring to Houdini reader/writer for "hook in" code points for studio-specific workflows #190

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

Similar to Maya, would be nice for reader code to have an empty function for 
users to add their own workflow specific behavior and properties
See ticket  179 
http://code.google.com/p/alembic/issues/detail?id=179&sort=priority&colspec=ID%2
0Type%20Priority%20Status%20Milestone%20WorkOrder%20Owner%20Component%20Estimate
InDays%20Summary

Original issue reported on code.google.com by ble...@gmail.com on 8 Jul 2011 at 2:19

GoogleCodeExporter commented 9 years ago

From the meeting, noted as a p2 and nice to have for 1.0 release

Original comment by scottmmo...@gmail.com on 11 Jul 2011 at 11:23

Added labels: Priority-P2
Removed labels: Priority-P1

GoogleCodeExporter commented 9 years ago

We ended up solving this case by making attribute remapping as part of the 
standard parameter interface of the Houdini plug-ins.

Original comment by steve.lavietes@gmail.com on 26 Aug 2011 at 12:12

Changed state: WontFix