X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.98.4 at av01.lsn.net Message-ID: <5508941F.2050809@ecosensory.com> Date: Tue, 17 Mar 2015 15:52:47 -0500 From: John Griessen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.4.0 MIME-Version: 1.0 To: geda-user AT delorie DOT com Subject: Re: [geda-user] pcb alternatives References: <5508413E DOT 4000405 AT ecosensory DOT com> <20150317182617 DOT 22729 DOT qmail AT stuge DOT se> <20150317192343 DOT 26859 DOT qmail AT stuge DOT se> In-Reply-To: <20150317192343.26859.qmail@stuge.se> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Reply-To: geda-user AT delorie DOT com On 03/17/2015 02:23 PM, Peter Stuge wrote: > Which are the primitives you have in mind? I'm sure he had physical components of a pcb as fabbed, such as a circle defined with a property that makes it print as silk screened ink or get etched as a circle of copper, as the next attribs to add. I'm saying design the software so it fits with logical thinking of the end result -- and I think I've heard John D. say similar before. The parsing rules of high level board components kick off so early in teh pcb code as is... That makes it hard to add to and understand. It may not get much volunteer sign ups to say it needs a total rewrite, but at least when considering adding for what's needed to do blind vias, we might take into account refactoring work being done already by Roland Lutz and others... They're dissecting gschem so it can be reassembled better. Same is good for PCB.