X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Date:	Wed, 30 Dec 2015 08:21:50 +0100 (CET)
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 and it's future with Scheme & Guile was Re: [geda-user]
	Project leadership
In-Reply-To:	<73273554-3E38-4F1F-9423-F731753B41D8@noqsi.com>
Message-ID:	<alpine.DEB.2.00.1512300817590.9035@igor2priv>
References:	<CAM2RGhS4L-ch6FEcLtdSt0vA0BdQZvq+AuFDP+9ea7Ftd=AALg AT mail DOT gmail DOT com> <8444F816-17CE-4A56-A982-4A60DEDA72B8 AT noqsi DOT com> <alpine DOT DEB DOT 2 DOT 00 DOT 1512300544550 DOT 9035 AT igor2priv> <A06FE370-5416-41F5-BBAA-BCF0D975DDD3 AT noqsi DOT com> <alpine DOT DEB DOT 2 DOT 00 DOT 1512300635240 DOT 9035 AT igor2priv>
	<2297464D-0109-4CA8-98D5-AC33BD0B02C5 AT noqsi DOT com> <alpine DOT DEB DOT 2 DOT 00 DOT 1512300723150 DOT 9035 AT igor2priv> <73273554-3E38-4F1F-9423-F731753B41D8 AT noqsi DOT com>
User-Agent:	Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version:	1.0
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

On Tue, 29 Dec 2015, John Doty wrote:

>
> On Dec 29, 2015, at 11:28 PM, gedau AT igor2 DOT repo DOT hu wrote:
>
>>>
>>> I?ve never found a serious limitation in geda-gaf abstractions.
>>
>> I have. See the mailing list traffic of the past few hours.
>
> What schematic object have you been unable to capture in the geda-gaf schematics? What circuit have you been unable to design? All I see is complaints about the work flow, not the underlying abstractions. Those are fully up to designing PCBs, ASICs, plumbing, makefiles, ...

Gschem fails to handle (find, zoom onto, list, highlight, etc.) nets by 
name. I consider this a bug. It keeps me from, guess, finding, jumping 
onto nets using the GUI. This, together with another shortcoming about how 
to handle projects with multiple schs, keeps me from fully exploiting 
back annotation.

Simplest example: pin 1 of U5 is connected to Vcc, and it shouldn't be. 
Gschem can't navigate me to all occurances where this happens so that I 
can easily walk thrhough them and fix them. Instead, I manually have to 
crawl through all schs and find somtimes very hidden connections (e.g. 
burried in net attributes of heavy symbols)

I know you don't need this GUI feature. I do need it. Random EEs I know 
are likely to agree with me.

- Raw text -