X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Message-ID: <1384391726.2064.16.camel@AMD64X2.fritz.box> Subject: Re: [geda-user] Fwd: OT-but-related: CERN developers committing to work on KiCAD From: Stefan Salewski To: geda-user AT delorie DOT com Date: Thu, 14 Nov 2013 02:15:26 +0100 In-Reply-To: <1384389572.7082.0.camel@pcjc2lap> References: <527C9C90 DOT 4080203 AT estechnical DOT co DOT uk> <20131108163938 DOT GA9549 AT recycle DOT lbl DOT gov> <1384389572 DOT 7082 DOT 0 DOT camel AT pcjc2lap> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.8.5 Mime-Version: 1.0 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 On Thu, 2013-11-14 at 00:39 +0000, Peter Clifton wrote: > It looks pretty sweet... > > If it were possible to make use of this code as a separate library, that > would really be awesome. > The problem may be the data structures. Of course there should be no problem for plain pins. But for pads -- I guess their shape may be defined differently for KiCAD and gEDA/PCB. PCB Pads can even built clusters -- multiple rectangular or rounded overlapping pads overlapping with round pins. So we can have really complicated shapes, not always convex. My router is also concerned by pad shape -- it was my initial goal to clearly separate the router algorithm from the code related to the PCB board, but I failed. Currently code for pcb board import is mixed with code for routing -- I know that that is not good, but I simple ignore that problem for now. Of course we can replace each pad with a convex hull of pins -- things may become difficulty when traces should jump over pads... And -- I was told that KiCAD (currently) does not support copper arcs, they build it with line segments. Maybe they have a good reason for that?