Mail Archives: geda-user/2015/07/09/14:43:22
> but back-annotation into the schematic is very impractical.
[grabbing a sound-bite to reply to, but breaking the thread a bit]
To be fair, we've had this discussion many times in the past, and came
up with three different types of "back annotation":
1. some sort of two-way street between gschem and pcb, so that gschem
gets updated wrt changes made in pcb. This has been prototyped as
an "in real time" dbus implementation for "live updates", but can be
done with scripts too. I think people who want this really want
the live update part, which many integrated EDA tools provide.
2. A forward-annotate system from pcb to a *second* set of "as built"
schematics. The user could, of course, iterate these as-builts
back to the design set as desired. This lends itself to diffs and
a more "big company" workflow.
3. Moving as-built data out of the schematic so that back-annotation
isn't needed. PCB would have to provide as-built info to the
netlister, which would integrate that with the schematic info to
build a new netlist. We'd still need a #2-type tool though.
(personally, I like #3, and I think it would be a better way to enable
pin/gate swapping in heirarchical schematics, but of course it's the
hardest to implement)
- Raw text -