
Alvin Penner wrote:
Jon A. Cruz wrote:
high that they are some "cut along this curve" approach, rather than a "punch out all black dots" raster format.
yes, that sounds reasonable, so you mean like a multi-segmented polyline. that probably would not be that hard to confirm, if one didn't mind getting one's hands dirty with some brute force dumping of raw data.
That's what my project Cuft was about. It dumps the binary data from GSD files into human readable XML or TXT.
http://code.google.com/p/cuft/
If you dump a gsd file to a txt document you will see the various comments I have smattered around for what I think the structures in the file represent.
There are a few reasons that the file changes in more than one place. NURBs are more complex moving an endpoint probably doesn't just move two control points like it does with beziers. And each drawing object in GSD stores a number of data items including the curve data and the bounding box. Changing the curve usually changes the bounding box too.
Please check out Cuft. :-)
Aaron Spike