X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Message-ID: <1436960577.1072.6.camel@ssalewski.de>
Subject: Re: [geda-user] The new to do
From: Stefan Salewski <mail AT ssalewski DOT de>
To: geda-user AT delorie DOT com
Date: Wed, 15 Jul 2015 13:42:57 +0200
In-Reply-To: <254F9AFE-1A3E-4D88-BABF-E6E0F87A56B1@icloud.com>
References: 
	<CAM2RGhQ70Pex5aNeQ86vKHc7sKf_Vpws69__CPb2QKg6fJTeHg AT mail DOT gmail DOT com>
	 <55A2A0A2 DOT 4080403 AT ecosensory DOT com>
	 <7AE39440-DA68-4491-A965-C1B97D1D86C1 AT sbcglobal DOT net>
	 <20150712213152 DOT 7968b74c AT jive DOT levalinux DOT org>
	 <304D9D86-3CF6-4D61-A5CA-6CE414EA0661 AT sbcglobal DOT net>
	 <20150712224637 DOT 2d4cc2de AT wind DOT levalinux DOT org>
	 <55A2E9B7 DOT 9040502 AT neurotica DOT com>
	 <CAM2RGhSmFhz9=oRaaj2EDL79c5XVmeuwmX_RdLqMv0evEHCyTw AT mail DOT gmail DOT com>
	 <CACwWb3DbmOZbtb9Hrp2JvvG7-toryXuequQA=YV7X6ss762zsw AT mail DOT gmail DOT com>
	 <20150713131707 DOT GA782 AT recycle DOT lbl DOT gov>
	 <CAM2RGhTT__nWCkA4y36rb24yT8xP=o1nR04H=DNqTJiu=naSGA AT mail DOT gmail DOT com>
	 <55A4042E DOT 5060402 AT neurotica DOT com>
	 <CAM2RGhS=5xq0_oN4e0M55Kor4bcnXNn3NfLvRZoi7Vw9Aq1ZXg AT mail DOT gmail DOT com>
	 <55A41B30 DOT 50602 AT neurotica DOT com> <alpine DOT DEB DOT 2 DOT 11 DOT 1507151114560 DOT 2113 AT nimbus>
	 <254F9AFE-1A3E-4D88-BABF-E6E0F87A56B1 AT icloud DOT com>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.12.11 
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t6FBmtcx006177
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 Wed, 2015-07-15 at 12:13 +0100, Chris Smith (space DOT dandy AT icloud DOT com)
[via geda-user AT delorie DOT com] wrote:
> > The problem here is that to gEDA, a net is a non-topological entity.
> You could assign attributes to nets (that wouldn't be that hard to
> implement), but then the "needs to be 20mils" attribute would apply to
> the whole of, e.g, the "GND" net which probably isn't what you are
> intending.
> > 
> > Representing the internal structute of a net in a way that makes
> this kind of attribute useful is much more difficult and would require
> a major addition to what the concept of a netlist entails.
> 
> I don’t think it’s that difficult.  I think all that is needed is:
> 
> 1. in gschem allow a net to be split into multiple segments. At the
> moment a net in gschem is a continuous line that has a number of pin
> connections.  I think it should be a collection of lines between two
> pin connections.
> 
> 2. teach pcb that a pin can be connected to multiple nets.

Yes. We discussed that about 5 years ago already. I think I made a
picture for that, can not find it currently. And John Doty told us that
gschem does support net segments, each with its own attributes indeed,
but the default is joining straight segments. One problem is moving that
information to PCB. Another problem is, that many people said we do not
need and want that. Maybe that was indeed the motivation to start with
my Peted tool.