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=Oo3LN23LXLg5oWA2Dyq3VKmwZ8WCfH2AcRMATPJY82w=;
        b=ifC3Z33iRR5QFsAK+6uLh6kF8fAyDFdm7ZAQsHlS/E5JmGvTzm/ZGsDWu+nMhZl1vc
         ori2eS/cD0c2h+a4OfJja19hJNPBFKe2dK5rnodGaVuJjJD4q3GcunVqg3YL+6GT7eYt
         Bm2VUfQkQYnc4DRPjW4s0TfYQdftIg0Mrni2JGvarpcQAlq4OcriKBetmOqxYq7Z3Ukx
         J4/UJFTYX1WZvVAmgx2qwZwEPNFOuMthRmaI0plurPTvQ0I9qQUrsyg/YfysjWpfeJ50
         zlt+NZMmI1mCbl4sKWcdpe907474WsKkDfeR87TPujUZviK0vAhMaTf3aJJsoI5u7zZ9
         hKgg==
X-Received: by 10.180.12.206 with SMTP id a14mr17680810wic.25.1445204670153;
        Sun, 18 Oct 2015 14:44:30 -0700 (PDT)
Date: Sun, 18 Oct 2015 23:44:24 +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] Pin mapping (separate symbols from mappings)
Message-Id: <20151018234424.c0551dad9bef0859130239d9@gmail.com>
In-Reply-To: <201510181843.t9IIhmWo025346@envy.delorie.com>
References: <20151018204010 DOT 9cce6a231dcc296256e187bd AT gmail DOT com>
	<201510181843 DOT t9IIhmWo025346 AT envy DOT delorie 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

I read more from you below. Even though schematic is stored in *.sch it would be possible to access a second file with the actual footprint pin mapping.

"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"


> > I think it would be rather good to separate symbols from pin mapping
> > and in such case symbols would have symbolic information only.
> 
> I agree, I wrote something up about this a while ago:
> 
> http://www.delorie.com/pcb/pin-mapping.html
> 
> It assumed there was a new tool that used various heruistics and rules
> to "heavify" a symbol, including adding a pin map:
> 
> http://www.delorie.com/pcb/component-dbs.html