On Mon, 2011-04-11 at 13:05 +0100, Andrew Seddon wrote: > 1. Be translated to common EDA formats with relatively simple algorithms > 2. Display nicely on standard SVG viewers > 3. Be easily to manipulate by tools working natively in the format > (this is probably implicit in 1 though) > > Keen to hear why this idea sucks! It doesn't. Some challenges to be met though. If you make schematics == SVG files, you need to ensure that opening and saving from an SVG editor (e.g. Inkscape) won't break the data within. Gschem currently uses special primitives to mark connectivity - nets, pins, buses etc.. I'm not quite clear how that can be mapped to SVG in a way which doesn't loose that information when edited outside of the EDA tool. Perhaps 2x way is too much to hope for though.. and we can just rely on the fact our files will render as an SVG. XCircuit does this with postscript files. Btw - I have a branch lurking about which emits SVG onto the clipboard when copy+pasting within gschem. That lets you paste from gschem straight into Inkscape. The net and pin end-cues aren't quite right with it though. -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me)
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ geda-user mailing list geda-user@xxxxxxxxxxxxxx http://www.seul.org/cgi-bin/mailman/listinfo/geda-user