On Fri, 2007-09-21 at 21:23 -0400, DJ Delorie wrote: > > There is one other possibility - not sure its a good idea or not - but > > you could write a simple (dumb) .sch / .sym parser and renderer. > > I have a C++ program that turns .sym's into EPS. It's a start. > > http://www.gedasymbols.org/user/dj_delorie/tools/sym2eps.cc
Nice ;) - a brilliant example of how concise it might be! .sch will be a bit harder of course, as you need to pull in the right search paths for components. The more I think of this - the more I think its a job for libgeda. If you don't want to load all gschem, you could just implement the required "draw" functions for the primitive objects. That might get complex to inplement all the details - all the output control rc variables gschem loads. Of course we should save re-inventing the wheel - so just teach gschem to export .png without opening any windows... or split out the code required for drawing to a static linked convenience library so gschem and a hypothetical "geda_thumbnailer" could share it. Peter _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
