> > I'm at least going to try implementing a postscript export module. I > though about doing a two-stage conversion of the data to postscript - > first select the objects the postscript exporter is capable of > transforming to postscript code, second use the exising render module > to create an image for the remaining objects. Now compose a postscript > document out of the two parts. > > The question is, as you noted, how to handle the camera in this case. > Is there a way to "apply" a camera to a dx object hierarchy to gain > "2d" objects? > > There's another possibility of the place the postscript exporter could > be done - as a different sort of hardware renderer. But here I have two > questions: > - is there a intermediate object representation created for hardware > renderers (i.e. a polygonal representation?) > - are text and higher level objects (spheres, etc.) preserved? > > > I'll have a look at the VRML exporter as you suggest. Any other > suggestions are highly appreciated!
It may be worth a look at the source code for GMT (Generic Mapping Tools). This produces vector Postscript output, with embedded images & PS fonts etc for text overlaid. GMT supports output similar to rubbersheet, (though no control of object opacity). GMT is open source & I believe that all the commands generating PS output use a common C library, which may save reinventing some wheels for OpenDX. (I've been using GMT for some years, only got into DX in the last few months as GIS ran out of functionality for some things I needed to do) http://gmt.soest.hawaii.edu/ Cheers Brent Wood __________________________________________________ Do You Yahoo!? Yahoo! Tax Center - online filing with TurboTax http://taxes.yahoo.com/
