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=yetKXWTU/hsqfmsm/8qNMBb8PXvv9qzNWBqSxxVbsuc=;
	b=Xmljuwy9WnkyzgsBatb8/WUOZt96mfBlkN/oyfXZdcG0/sqmG71QCQVOoTP7glb1cS
	cnEHK/8vbu/MDJIGrnlbUjr3OMD9heexaR/1QVuMHkYllT1H52wMnOTW1+fMJSfTSPlb
	JYp9kc20BLfEOc1AsMI3qxDMCBgFbpzehXZDBA0njLDEVys72+JkDM92qzq9q3C6fJMf
	f3RDXmaM7xvcIyjdHFeLVKwbFk+qq76zUeObTjNLJ3PN3RAuJGV/t0Ds8tFM/HB8O0wt
	oAa2I4KP9/a/7s5CTRe1tdFeLBIe0NW51DiWfPGLQISjEmmgZ7tS7oYERFYhRGv6xZe+
	vkEg==
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=yetKXWTU/hsqfmsm/8qNMBb8PXvv9qzNWBqSxxVbsuc=;
	b=X5br/TbwDuduftOIu/DCM5ReFJrXe2RTYa8a06VNzqRRPPAeVsPVZKHaXNNbT1NeAH
	fXHslwt2QBUkCas46uiLjSenDLn8/A/OutdGshLYZSlgd35oqR+mKNQ3oF62OCwGEtJ2
	1Atk0tSXg8DTDbtDxlZvcTm4UYOm3dznFuZdiiGwgXhJUTPk8kK6xxMTh3pP5OGIXjUE
	JRPxwtFgeoMO9iemNHiBsIzOzc5t9bJL2/zY/RqLNqVx7x1QvyrGKiXoxiDwDpTDOAcc
	p6BIcyNhjD2D80218wVV8TXVa/p7yyjz2098MlI4GyFYbONm9f3qohGLTnRIDK7JP6nn
	ygDA==
X-Gm-Message-State:	AG10YORk6V/v+wgCmpNeBz6Zx4xUGB9yW4J3/ASkf+0bJbYyyGuwPW5wqc2+3yY0w7YT7Q==
X-Received:	by 10.28.137.135 with SMTP id l129mr11821983wmd.38.1453113395082;
	Mon, 18 Jan 2016 02:36:35 -0800 (PST)
Date:	Mon, 18 Jan 2016 11:36:33 +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] Blind/buried vias, padstack
Message-Id:	<20160118113633.594d1406d3ee58af7736acb8@gmail.com>
In-Reply-To:	<alpine.DEB.2.00.1601181056200.9035@igor2priv>
References:	<20160118093035 DOT 7ecd3b5ee5f5d3ae1e8dc91a AT gmail DOT com>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1601181056200 DOT 9035 AT igor2priv>
X-Mailer:	Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu)
Mime-Version:	1.0
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

> On Mon, 18 Jan 2016, Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com] wrote:
> 
> > If there is a quick fix for blind/buried vias without change of file format I think this is a good solution right now.
> >
> > I however think it is good with a discussion of a more general mechanism for via/pin/pad and in particular possibility with a library of these for different package types. Even though there are cases then a more general mechanism is needed I think old style maybe with some modifications could be kept as a short hand notation. A library of vis/pin/pad is especially useful then adding new footprints and then small adjustments are needed.
> 
> If there's enough developer resource available for PCB, a full redesign of 
> the related internal structures is a good idea IMO. Looking at the 
> history of such big refactorings, I am a bit pessimist about whether PCB 
> really has enough resources to finish such an effort in reasonable time. 
> Let's hope I'm wrong.

I think it would be good if angles are kept instead of line lengths then moving lines in rubber band mode but have to decided to look at clearance right now.

Right now it is about figuring out what would be need to create a really good layout program which should be convenient to work with.

What do you think about the idea with possibility to create of via/pin/pad with arbitrary drawing primitives on any layer?
A short hand notation for the most common tasks similar as pin/pad today?
To put via/pin/pad in a library with folders for different package types?
Possibility to use pin/pad from library then creating a footprints different sizes?
Store a local copy but possibility to update from library?
Possibility of local change on single pin if necessary?
Cut out on any layer with the ordinary drawing primitives available today?
Cutout in layers above footprint to indicate size of component?


Nicklas Karlsson

- Raw text -