search

andrewhwood / alembic

Automatically exported from code.google.com/p/alembic
Other
0 stars 0 forks source link

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

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
From discussions with Disney and Dreamworks, it feel slike a good idea for a 
few spots in the reader and writer code for "insert your customizations here" 
type function calls.. Possibly go so far as to provide a sepearate .cpp file 
that is nearly empty except for the function defitions so that studios will 
have a trivial merge-with-new-alembic-lirbary operation.

Original issue reported on code.google.com by cookingw...@gmail.com on 6 Jul 2011 at 3:12

GoogleCodeExporter commented 9 years ago 
AbcImport
AbcExport
Alembic_In
Houdini reader

This item relates slightly to #181 "add second "bucket" for facility-specific 
workflows", because if we do #181, we'd likely want a tiny reference or a 
comment naming the user parameters methods.
This item also relates to doc, because in explaining how to adapt Alembic for 
use we'd like to reference than names of these hook points.

Original comment by ble...@gmail.com on 7 Jul 2011 at 10:11

GoogleCodeExporter commented 9 years ago

Original comment by ble...@gmail.com on 7 Jul 2011 at 10:12

GoogleCodeExporter commented 9 years ago

Original comment by ble...@gmail.com on 8 Jul 2011 at 2:08

GoogleCodeExporter commented 9 years ago 
This task is far too broad.

When external developers present us with functionality they would like we can 
either
integrate it directly or create the hook to make it easier to merge their 
feature later.

Anything else is mind reading, which might be unusable by them anyway.

Original comment by miller.lucas on 28 Jul 2011 at 9:23

GoogleCodeExporter commented 9 years ago 
I think there are several easy options that give a starting point for external 
developers.

On the writing side AbcWriteJob::eval () can call out to a currently empty 
method for each writer type (e.g. MeshWriter). You can have setup () call out 
so that external developers can add their properties. Likweise as 
CallWriteVistor () invokes write () the write () method can call out to a 
currently empty method the developers could use.    I think it'd be enough to 
have the write () methods pass the O<geomType> and the dag path.

Original comment by ble...@gmail.com on 29 Jul 2011 at 8:18