X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Tue, 1 Sep 2015 03:51:09 +0200 (CEST)
X-X-Sender: igor2 AT igor2priv
To: geda-user AT delorie DOT com
X-Debug: to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu"
From: gedau AT igor2 DOT repo DOT hu
Subject: Re: [geda-user] back annotation proposal (RFC)
In-Reply-To: <ms2sqg$rs6$3@ger.gmane.org>
Message-ID: <alpine.DEB.2.00.1509010339310.6924@igor2priv>
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> <alpine DOT DEB DOT 2 DOT 00 DOT 1508310637471 DOT 6924 AT igor2priv>
 <ms2sqg$rs6$3 AT ger DOT gmane DOT org>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
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



On Tue, 1 Sep 2015, Kai-Martin Knaak wrote:

> gedau AT igor2 DOT repo DOT hu wrote:
>
>> I generally like most of this. I have some constraints, tho: your
>> idea needs massive gnetlist backend coding, which means a lot of
>> scheme coding.
>
> Are you aware that Roland Lutz's rewrite of the netlister comes with
> no use of scheme at all? It sort of replaces scheme by python in the
> backends.

Thank you for the info.

To be honest this still doesn't really solve my problem: that I'd still 
need minor gschem UI changes. It'd solve another problem that I may not 
even have if I didn't want a generic pin mapping thing. ... which I 
probably don't want.

I see two ways. Either DJ's idea which would be a large scale change and 
will solve pin mapping slotting only, but not footprint change in pbc 
(or capacitor value change in simulation) for example. That'd be added 
later on top of that somehow. Or my hack that solves the back 
annotation of all the pin changes and other parameter changes but is not a 
generic slot/option mapping system.

DJ's idea needs gentlist changes _and_ gschem UI changes.

My idea needs only gschem UI changes.

Since my idea directly solves problems I want to get solved and is 
generally a smaller change outside of pcb-rnd, I still prefer that over 
the big pin mapping thing that only indirectly solves soem aspects of my 
problem.

Regards,

Igor2