X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
Date: Thu, 26 Jul 2012 12:54:19 -0400
Message-Id: <201207261654.q6QGsJFk017955@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: geda-user AT delorie DOT com
In-reply-to: <jursf1$hda$1@dough.gmane.org> (message from Kai-Martin Knaak on
	Thu, 26 Jul 2012 18:49:37 +0200)
Subject: Re: [geda-user] pcb footprint update hack
References: <20120719182728 DOT GA12447 AT slana DOT eecs DOT oregonstate DOT edu> <201207191846 DOT q6JIkbTb030133 AT envy DOT delorie DOT com> <20120719160003 DOT 3a3fb538 AT svelte> <201207192322 DOT q6JNMhYj012483 AT envy DOT delorie DOT com> <50089DC4 DOT 7020006 AT ecosensory DOT com> <201207200133 DOT q6K1XP90019375 AT envy DOT delorie DOT com> <20120721005807 DOT 42aba8c7 AT akka> <500A0E11 DOT 7090809 AT ecosensory DOT com> <jursf1$hda$1 AT dough DOT gmane DOT org>
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> > element and PCB element down to the polygon-on-a-layer level.
> > And 2-way updating gschem-->PCB-->gschem-->PCB.
> 
> Anyone currently working on this?

I've blue-skied a plan for this, but nobody's working on it at the
moment.

Scroll down to "Back Annotation" on this, and read the last paragraph:

	http://www.delorie.com/pcb/pin-mapping.html

  "Another idea is to have PCB be the "keeper of the pin
   assignments". Each time it runs gnetlist, it exports the current
   pin mapping. Gnetlist uses the current mapping as a starting point,
   and allocates pins from the pin mapping in the database (or
   provided by pcb) based on what pins are available."

It's not quite back-annotation, but it solves the same problem in a
forward-annotation way.  There would need to be a "sch+pcb -> sch"
filter to go along with it, though, for back-documentation at least.