X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=date:from:to:subject:message-id:in-reply-to:references:mime-version
         :content-type:content-transfer-encoding;
        bh=2ZDP9K7rIukxzaY5Smli3Ek41k7vid3x0FFdyLdjZ8c=;
        b=Bkd30yNesVGm9pavzlWBNsQTxGVLeMa/FBiI29Jis6g6pfYUgngmaE1GPYuuSEIuSJ
         NLuvZGuO7kS7xpo8PWz6WG2VmP+9BRZepaWqyktfTEp2D7j0ZIF/xWTF8fnoLTH8fc8H
         BxvX8fGcuCv/IuXvliaZYsruqIcCZ7ZnnpdiPrvfS06W+EaEc7z/9VFQRpvRBouiKrf7
         NFMp3j/noKcMNilBFhvXcy+oFZN59O5zKGb9oVpnq9tRmWpEyZhLJ717JrtTW6H1G8Eu
         HlIzDdw1jfIrHrl1GvQaJoC5K3xehPZz2Ai/9Lk2D1gt9tS0jTIV3zUa0IfOagkEPjdD
         NhWA==
X-Received: by 10.180.108.177 with SMTP id hl17mr2073793wib.45.1441030602386;
        Mon, 31 Aug 2015 07:16:42 -0700 (PDT)
Date: Mon, 31 Aug 2015 16:16:36 +0200
From: "Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] back annotation proposal (RFC)
Message-Id: <20150831161636.d99b3f330903ff90376250f2@gmail.com>
In-Reply-To: <CAM2RGhRcQKdYjR5mKDazQ-TouPK0ydkEgt05tscCcWQh4s0EDQ@mail.gmail.com>
References: <alpine DOT DEB DOT 2 DOT 00 DOT 1508301838470 DOT 6924 AT igor2priv>
	<201508301802 DOT t7UI2twS031311 AT envy DOT delorie DOT com>
	<CAM2RGhRgPQG2WDFVb0SFvMbypyYKS2oYtD=851WHR6fOB4iWdA AT mail DOT gmail DOT com>
	<201508310341 DOT t7V3fcfh022966 AT envy DOT delorie DOT com>
	<CAM2RGhRcQKdYjR5mKDazQ-TouPK0ydkEgt05tscCcWQh4s0EDQ AT mail DOT gmail DOT com>
X-Mailer: Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
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

It is not enough doing the same thing as gnetlist but in reverse is not enough. Changes may come from any direction so it is also necessary to know in which directions change should be made. If footprints are different should there be a forward or backward annotation? If there are unsaved changes?



On Mon, 31 Aug 2015 09:52:17 -0400
"Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com> wrote:

> On Mon, Aug 31, 2015 at 3:41 AM, DJ Delorie <dj AT delorie DOT com> wrote:
> >
> >> That makes a lot of sense for the netlist but what if you change a
> >> footprint? I think there should be another tool that you run in
> >> parallel to gnetlist to handle that.
> >
> > I assume a much more intelligent netlister.
> >
> > The netlister maps what it knows about each symbol to a list of
> > candidate options for "heavifiing" the symbol into a full component.
> > One of these options is the package, and once you somehow choose a
> > package, there's one or more footprints that go with it.
> 
> See to me that is 2 different tools
> 1. To handle migration of the netlist into gschem (I think more of
> this might happen in gschem than Igor2 expects right now but I have to
> sleep on my ideas before saying more)
> 2. To handle changes in symbols and their properties (footprint and etc)
> 
> Tool #1 is doing the same thing as gnetlist but in reverse
> implementing something like minicut from pcb-rnd. I think that is at
> least a fork if not a whole other tool from gnetlist.
> 
> > Part of my idea is that pcb takes all the choices it knows about and
> > gives them to the netlister, so that the netlister can use that to
> > narrow down the options it's left with after dealing with the
> > constraints in the symbol.
> >
> > I.e. if you have a generic AND gate symbol, there's lot of options for
> > the netlister.  But if this is a future iteration, pcb might already
> > know that you picked a 74ALS00 in a SDIP-14 package with the SDIP14M
> > footprint.  It can tell the netlister this when it does an
> > update-import.  It can also tell the netlister what pin mappings were
> > used.
> >
> > If the information in pcb is no longer valid for the device (i.e. you
> > changed a 2-in AND to a 3-in AND), then the netlister would discard
> > pcb's choices and start fresh.
> 
> I have to think about this more. A lot of stuff (like slots in
> symbols) only works for things like 7400 series logic.
> 
> > So, there's a lot of back-annotation information being sent from pcb
> > to the netlister, which lets you do package, gate, and pin swapping in
> > pcb, but none of it ends up back in gschem unless you do something
> > specific to make that happen.