[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: gEDA-user: Which are the biggest looking gEDA warts?

Andy Peters wrote: 
On Feb 25, 2007, at 4:53 PM, Ben Jackson wrote:

On Sun, Feb 25, 2007 at 05:07:59PM -0600, John Griessen wrote:


No back-annotation.


This is VERY important to me. As part of general cleanup after finishing a layout, I renumber all of the reference designators in geographical order. This gives technicians a fighting chance to find parts on a cluttered board.

I'll just comment that it would be quite easy to implement this. There is already a Renumber() action in pcb. It will renumber all the refdes's in geographical order and produce a log file showing what was renamed to what. That file is designed to be fairly easy to parse with code and it would be pretty simple to complete the loop with a tool that applied that to a set of gschem schematics.

To try it out,  save off a copy of your .pcb file (just to be safe), and run

:Renumber()

from within pcb. It will prompt for a file to log results in. Look at that file, compare to what the pads_backannotate script looks for and you'll see that it is probably under an hours worth of work if you are a perl programmer to make pads_backanotate become pcb_backannotate.

On the topic though, I think it would be generally useful to teach gschem itself (or maybe another tool which uses libgeda for loading the .sch files and manipulating the database) to read some sort of annotation file. Then instead of lots of foo_backannotate files that all have to parse .sch file, we can just create files which translate from pads, pcb, or whatever ECO type files to the annotation file format that gschem wants and hopefully that will represent a stable target.

-Dan


_______________________________________________
geda-user mailing list
geda-user@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user