[Bf-python] request to script importer and exporter writers

Tom M letterrip at gmail.com
Sun Dec 11 05:58:14 CET 2005


For those of you who have import and export scripts currently bundled
with Blender or are planned for inclusion, please edit the table on
the wiki that tells what all your exporter supports.

There are two tables, one for importers and one for exporters

http://mediawiki.blender.org/index.php/Competitive_Analysis/Proposed_include#Exporter_Feature_Matrix

The table is in part based on this table here

http://www.okino.com/conv/filefrmt_3dimport.htm

Use Y for Yes, N for no and a - for not applicable to that format.

The fields mean the following
Native - the native application for the format if relevant if your
script only handles particular versions of a format or if it supports
more in one version than in another, you should make multiple
listings.  (Ie the LWO inporter handles both import and export)

Ext - the standard 3 letter (or whatever) extension for the format obj, lwo etc

Object - whether the exporter handles object level data - this
probably redundant
Mesh - mesh whether the object handles mesh data - may need to split
this since some formats have multiple mesh data types

Mat - does it export materials

uv - does it export uv map coordinates

vert color - does it export vertex color

arm - does it export armature data (bone hierarchy) - this may need to
be split into armature and constraints

animation - does it export animation data - we again may need to
differentiate between different types of animation

skin - does it export weightpainting data

Scene - does it export scene data

Lgt - lights

Cam - Camera

World - world properties, may need to be more specific



LetterRip



More information about the Bf-python mailing list