2009/6/30 Tim Edwards <[email protected]>: > Dear Svenn, > >> Just adding a bit more to this thread in the hope that Tim will get >> time to have svg export directly from xcircuit. > > Since you sent this gentle reminder to me, I did a web search on > SVG and found a lot more in the way of example code than I did > previously. Enough to get started on an SVG export (and possibly > import as well---that is, have the option to completely replace > PostScript with SVG). I have been experimenting with writing bits
Hi Tim, for what it is worth, I don't know if I would be happy if you _replaced_ the old .ps file format with a .svg. I have so far only used .svg to be able to get my drawings from the unix world into the Microsoft world. You wrote somewhere that postscript needs to be self content, and this has lead to all xcircuit files being viewable, printable and editable even if the rest of the underlying library has been missing. I have had problems with xcircuit and multi-file projects in the past, so this feature had been important to get schematics out for reviewing. Would SVG make xcircuit easier to handle in a project environment? You know the one where one engineer put together a module in one directory and another engineer binds this module into a toplevel on a different hierarchy? In the end, it is the netlist that matters, but getting there is sometimes difficult with xcircuit as the symbols of the missing modules are present, but that is only the self-content shaddow, not the real thing. -- Svenn _______________________________________________ Xcircuit-dev mailing list [email protected] http://www.opencircuitdesign.com/mailman/listinfo/xcircuit-dev
