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=UonPasFnDvqf3qHm6OQX1EDyw698gJRClmL7fJet4Uw=;
        b=NwB7hMwLUh0SH6cSx4frsiIuRvYU9EcF2H7RhC1i/G2GhWk2ihFvqGNNyK+5LBx2x1
         Re/IXgt4tgN4/TxKWRIXQWD0Um6vvayK8T2P9KpDlksSxwm3xo/OSRijH2UWpdSi0Mgw
         4CiGlhKD8SNy2TH4FauQMiqgOfeHJGuR2/um/81o8ADR7eEy50xbEQ2iFQinSZ776vs+
         raJb+5WFsL+5Akuut7b367jmTwRN8lizNWjOGWAi9ar4on9jcGoe9bdnqkMFWunEe/V4
         LfiaEbJTFyKuvEfG6QuYtbVOJBjVXr+l8nUe5vpB8808VgDTDBxJJFwhVBaqImui6ecK
         +qtw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to
         :references:mime-version:content-type:content-transfer-encoding;
        bh=UonPasFnDvqf3qHm6OQX1EDyw698gJRClmL7fJet4Uw=;
        b=B4xoLV8vLt2US/eOvLQNdJNfWee1lyAU2g+CEAzTkWv570H3iK1FNQil3sojKxhGzN
         qtI4qW/IAP88IyQCyC/rzs+JmXDK4ATQfs901sp1vGUWKwIQycBNxYWN4iWDZv5I3cy5
         VIleSWf3A/ti8VFamJEhqYFSwq7+R2q64JEIg1uhzA8C0sRku6QEpKUq00Np7MOhtMvo
         QHOOwugRTpG8VB/F66MS2ctJ97/5aotr+WOwESN7y/jNXj50u1gJC2+tj5Xz52P+UrKb
         d45snFlGoIAz0LLUmm06yCi00i0wJGnPq76iu9WkLgfFp/pj2uOl9wrcMZjC716OtsZe
         /6vQ==
X-Gm-Message-State: AG10YOS1M4UelUWoLf9MfhjAj01KmK6L4S4CDIGoyIkKcmhOuIZLzrpR+U9Ww/20vQO/CA==
X-Received: by 10.28.54.159 with SMTP id y31mr2825782wmh.87.1453982649416;
        Thu, 28 Jan 2016 04:04:09 -0800 (PST)
Date: Thu, 28 Jan 2016 13:04:07 +0100
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] The nature of gEDA layers (forgot board layer)
Message-Id: <20160128130407.601fd5e69c09d63f4c8949e9@gmail.com>
In-Reply-To: <56A9E416.8080500@ecosensory.com>
References: <alpine DOT DEB DOT 2 DOT 00 DOT 1601180756390 DOT 9035 AT igor2priv>
	<201601261804 DOT u0QI4KEQ009550 AT envy DOT delorie DOT com>
	<E7D351BF-5BBB-41AC-B996-D5E27079A82C AT noqsi DOT com>
	<CAC4O8c-ZyNnCzCDHXkYYabSD4fG8vf+CKmhMycNJujGMPKzQDQ AT mail DOT gmail DOT com>
	<s6nr3h49hrq DOT fsf AT blaulicht DOT dmz DOT brux>
	<DDB07351-7C94-4B5C-99FA-83750CD4592A AT noqsi DOT com>
	<20160126233332 DOT dec2f06f5c74354a3841989c AT gmail DOT com>
	<s6n1t93h4ub DOT fsf AT blaulicht DOT dmz DOT brux>
	<20160127091746 DOT 1c7a976c2752f913921688ac AT gmail DOT com>
	<s6npowne74w DOT fsf AT blaulicht DOT dmz DOT brux>
	<20160127141334 DOT c738feb9dbeb54a7dec3dff8 AT gmail DOT com>
	<s6n37tjt1tv DOT fsf AT falbala DOT ieap DOT uni-kiel DOT de>
	<56A8F74B DOT 8080304 AT ecosensory DOT com>
	<CAC4O8c9UKLsh5FAAwUMEtHThKH-w3gUmCU2i9dRW9igkyRt-TQ AT mail DOT gmail DOT com>
	<CAJZxidDmjMtd_fKvR5qZVRa+hwDUbvfaz79oZjkBgDuE1m8RBg AT mail DOT gmail DOT com>
	<56A961BC DOT 3040405 AT ecosensory DOT com>
	<CAJZxidC=nbxAinOtpfGHHqwPXbEMrhfat7jKgA9KBp3EVVg4_Q AT mail DOT gmail DOT com>
	<s6nbn863xlu DOT fsf AT blaulicht DOT dmz DOT brux>
	<56A9E416 DOT 8080500 AT ecosensory 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

> >> >My experience has always been that hard to read spaghetti code is the
> >> >result of dealing with special cases that arise from having data structures
> >> >and functions that weren't designed quite right. Making things more generic
> >> >reduces the number of special cases and allows for the maximum reuse of
> >> >structures and functions.
> >> >
> >> >As I stated in my opening remark, feel free to take or leave my
> >> >suggestions. Obviously I think it would be wise to heed them
> > So do I.

> So, if one generic container of data holds a 2D conductor on insulator pattern, and one holds
> solder mask and one holds top-to-bottom-via connectivity they don't all get talked about as layers or it
> is confusing.

I forgot the board layer. As is now board is usually modeled by an outline and via/pin which may or may not have plated edges. via/pin is handled a little bit different from other drawing primitives and are not added as drawing primitives to a particular layer although it is well known they make a circular cut out in all board layers.

Someone suggested an extra connectivity layer and for an ordinary plated hole the annular ring plated on the hole edges connect all layers. Any drawing primitive on a copper layer overlapping this annular ring will connect. Basically these annular rings are at same mechanical position as board. A proper model of the layer would require two layers of different material at same mechanical position: board with drilled holes which are equal to round cut out and a layer with annular rings connecting layers.


Nicklas Karlsson