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=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=xWCQl+yw5DiEAVmcg57mT5TRTEHBBQV7ZsrANqfiOus=; b=oS/6aIlthIDn7wlQyuesPbq1Y3ghlbG7F7zji5V8jhJaoLwPxSHm/JQmVHDIWj2xKe lSlblGyjeC+esbrLT6uBpcR+Urzp6lfq8PxXOTyyjzrOQTQQ5CrZGgeqXLxXuXCU2ZPZ JDd88tm+x48Z+t6Zix1b/WplAPDX94305HLfH8mS/f3rc1P4AGnWdXHuQXBkuqPevNUT 9dPwi98NEh92iYGYS8deqHjEeEU6PxQ/9UFZHGnfeksCkRPjZLlkl9Cl69knQwsPBr8h bE8fWBdc2RWnaBE5dH3LKChz4riDYHlEmJxMCHV9nZzsPpCWoeg2Z2Hi09kNYMyIN6Fd HtLw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=xWCQl+yw5DiEAVmcg57mT5TRTEHBBQV7ZsrANqfiOus=; b=XM+8s36bdD3dWC4MZ2JYW11Wefh7Q79qq0qEmuIyg/BsELVuGaYRDAZpqTtTcsTLH8 TwORVt5z1AZXq0A1Bwu5mor89iStBNFoNVFmTESBfPwzVMW74ywB37p7DT/VgIlwqnob zfV475c7EBwCvYFvxNcWgkty3ISOBEtgSWirTnP6lFbiQD+i/hY0lLfu8V3DUyAtl9zN uSMnRVOHjTlqi1UHxsYhu4YPEuJk11ytSmbyWfOhFfr3UtwjsEvcRUqciAhVmIdUas5G S7UhjiXP29ueP+lByJ2qc+9IekH3CfHp6ndLoSgP3CmrPpVsPXEaRxoDNfDNDgjfqa7c oPlA== X-Gm-Message-State: AG10YORZ24Puj1O8i4RnSigYBUsHw+2jjab7J5aEQy2qj5gSjAyNLzfLJ2IIv/0P7HuD9co7eoBq1x/XRiU4+Q== MIME-Version: 1.0 X-Received: by 10.50.4.101 with SMTP id j5mr6856427igj.47.1454028484643; Thu, 28 Jan 2016 16:48:04 -0800 (PST) In-Reply-To: <201601282337.u0SNbl82007592@envy.delorie.com> References: <20160126233332 DOT dec2f06f5c74354a3841989c AT gmail DOT com> <20160127091746 DOT 1c7a976c2752f913921688ac AT gmail DOT com> <20160127141334 DOT c738feb9dbeb54a7dec3dff8 AT gmail DOT com> <56A8F74B DOT 8080304 AT ecosensory DOT com> <56A961BC DOT 3040405 AT ecosensory DOT com> <56A9E416 DOT 8080500 AT ecosensory DOT com> <20160128200126 DOT 0fe1bb26d5c28e59d56dfd0e AT gmail DOT com> <201601282134 DOT u0SLYET7002642 AT envy DOT delorie DOT com> <201601282337 DOT u0SNbl82007592 AT envy DOT delorie DOT com> Date: Thu, 28 Jan 2016 19:48:04 -0500 Message-ID: Subject: Re: [geda-user] The nature of gEDA layers From: "Chad Parker (parker DOT charles AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Content-Type: multipart/alternative; boundary=001a11c31c84521471052a6e633d 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 --001a11c31c84521471052a6e633d Content-Type: text/plain; charset=UTF-8 Clearly I've demonstrated my ignorance regarding the DRC, and it wasn't really my intent to discuss BBVias. I hope that I can ask some intelligent questions about these topics, but perhaps I will do that in a different thread at another time. My purpose in speaking up this time was really just to suggest a model for how the to think about layers, so for the moment I will stick to that. BBVias need to have pads only on the relevent layers, which requires > some change, as well as the drill changes. Is this not also true for through-hole components? They don't really need to have pads on an internal layer unless you're connecting a trace to it on that layer. Although, I can't think of an instance in which I have ever seen a through-hole pad stack that omitted any inner layer pads, so perhaps there's a reason I'm not aware of. I'm sure someone will be eager to enlighten me :) > Remember, it's not just gerber, it's also gcode, png, ps, and whatnot. > I have tried to keep that in mind, and the variety of output formats that need to be supported seems to be to be a strong justification for keeping things simple and generic. If you base your data structures and primitives on a particular output format, then you may well be making it more complicated to produce all of the other output formats. With that said, if you base your data structures on a particular format, at least you can output that format easily. Poorly designed data structures could make it difficult to output every format! (please note that I am not making any judgements about the current code base here. As I've already said, my familiarity with it is 0.) Someone needs to do the work. > Yup. This is really what it all comes down to. It's easy to sit here and theorize about how things ought to be done. But I've always found work to be a lot easier if I have a solid plan of what I'm going to do and where I'm going before I start. Hopefully that's what this discussion will be. Cheers, --Chad --001a11c31c84521471052a6e633d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Clearly I've demonstrated my ignorance regarding the D= RC, and it wasn't really my intent to discuss BBVias. I hope that I can= ask some intelligent questions about these topics, but perhaps I will do t= hat in a different thread at another time.

My purpose in speaking up= this time was really just to suggest a model for how the to think about la= yers, so for the moment I will stick to that.

BBVias need to have pads only on the relevent layers, which requires=
some change, as well as the drill changes.=C2=A0

Is t= his not also true for through-hole components? They don't really need t= o have pads on an internal layer unless you're connecting a trace to it= on that layer. Although, I can't think of an instance in which I have = ever seen a through-hole pad stack that omitted any inner layer pads, so pe= rhaps there's a reason I'm not aware of. I'm sure someone will = be eager to enlighten me :)
=C2=A0
Remember, it's not just gerber, it's also gcode, = png, ps, and whatnot.

I have tried to keep that in mind, and the variety of output format= s that need to be supported seems to be to be a strong justification for ke= eping things simple and generic. If you base your data structures and primi= tives on a particular output format, then you may well be making it more co= mplicated to produce all of the other output formats. With that said, if yo= u base your data structures on a particular format, at least you can output= that format easily. Poorly designed data structures could make it difficul= t to output every format! (please note that I am not making any judgements = about the current code base here. As I've already said, my familiarity = with it is 0.)

So= meone needs to do the work.

Yup. This is really what it all comes down to. It's e= asy to sit here and theorize about how things ought to be done. But I'v= e always found work to be a lot easier if I have a solid plan of what I'= ;m going to do and where I'm going before I start. Hopefully that's= what this discussion will be.

Cheers,
--= Chad
--001a11c31c84521471052a6e633d--