Blender Import/Export Script?

[DevUrandom]

Commited pie_import.py 1.1a in r2239.

[kage]

i've finished the export script to a point where it and the import script are completely compatible with each other in any direction (import -> export -> import will be the same as just importing). they both should also be fully spec compatible with pie 5 and pie 2.

however, now that this is done, i'm putting all work in this area on the backburner for now -- some of my choices have made the scripts unwieldly to modify in some aspects, and for me, the process has become very tiresome, and thus certain features have not yet been implemented, such as a separate validation script (currently it's partially integrated into the exporter), a teamcolor wizard, general intuitiveness planned for all included scripts, etc. beyond that, i've got too many other projects i need to dust off, atm.

if and when i find that enough people are asking about how to use these scripts properly, i'll write up a concise guide, though if anyone wants to write a guide, i'll be more than happy to walk them through all aspects. also, until i find that enough people are asking about some missing components, such as teamcolor editing, this project will remain on my back burner, though anyone else is obviously more than welcome to continue work, and seek insight from me regarding the scripts' inner workings.

the contents of blender-pie.zip should be extracted before commiting to remain compatible with the current svn tree, but everything needed to use the scripts is included in that zip.

also attached are two python mini-scripts that are of fairly little general use, but may serve as an example of how to interface with pie.py (pie.py from the zip must be in the python path for these scripts to work). the names of both scripts aren't very good, since neither of them actually "find" files, but will filter supplied filenames: find-bad-pies.py when given a list of filenames will find the ones that, as far as the pie parser (pie.py) is concerned, aren't valid -- the only noted limitation of the parser is that it assumes only one directive, or chunk of data (such as point, poly, connector, or bsp data) per line, thus some valid pies aren't viewed as valid, though those are rare. find-poly-nums.py was created to find out if there were any pies that contained any polygons with more than 4 sides: as of at least 2.0.6, in the official dist, there are none (thus the script generates no output).

here's an example of how to use these scripts on a unix system (both scripts only accept filenames as arguments):
`find /usr/src/warzone2100-2.0.6/data/ -iname "*.pie" | xargs ./find-poly-nums.py`

[Giel]

Committed in r2420 (the find-* scripts as well).

[kage]

cool, thanks