Hi Matt, The registration for the Collada exporter is in the file chimera/share/ExportCollada/ChimeraExtension.py http://plato.cgl.ucsf.edu/trac/chimera/browser/trunk/libs/ExportCollada/Chim... The ChimeraExtension.py file for each Chimera extension is imported when Chimera starts. I believe that is all that is needed to have the format appear in the File / Export Scene… menu. I don’t know how you intend to get extra input parameters for exporting Blender Collada. None of the Chimera export formats take extra input parameters. So the Export Scene… user interface just presents a file save dialog. If you need some other GUI the easiest approach is not to use File / Export Scene…. Instead make your own “Export Blender Collada” in the Tools / Utilities menu. To see how to do that look at some other example Chimera extension that has a Tools menu entry, like the Icosahedron tool http://plato.cgl.ucsf.edu/trac/chimera/browser/trunk/libs/Icosahedron/Chimer... Tom
On Sep 25, 2015, at 12:15 AM, Dougherty, Matthew T wrote:
I have modified the collada exporter to work with blender to the point I need to fork it off. I want to call it Blender, as opposed to the existing Collada exporter and overwrite that code. It is mostly the collada chimera exporter, but has additional UI inputs to make it better integrate with blender.
How do I register it so it lists like the other scene exporters? Is it entirely within the existing collada code extension, or is there another call or init that needs to be made outside the collada extension directory?
Matthew Dougherty National Center for Macromolecular Imaging Baylor College of Medicine