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=eFVDrezaWJJosXM1PGEDg3I1jBzfPtDvyvaJkH8o9GA=; b=xD2/ORtJ1qP08Dx23ec4se0ortorlc2cac315+AZUt3a0PjTmYAa5mNQ3vOoJPszfV tmN+e+rkD276O1b2hjbavPGJZrVtnmJYRyqghLvvqv+TVIgiD2Wf9MMkmASW5MEGRn9M LHvIUTwwlnOQH9ePGKnxuwNG91RxAPAglJNjpv1tBnml00VeQbo5WbuCe+1QMXExROQK Bve1bK8Ir5ojMrjq7pqk8/aMCvuzINWqd9aCvgrRJjafdPr0T5PZzuGOZnYjtINXaFNd bI5quT2nxvWJI0e+U+qZ6sruOOO6AAYZzuxXUGZH0h7wVgG96jwOc++jdhjrtzSa+DIV Eq6Q== X-Received: by 10.28.172.193 with SMTP id v184mr1688006wme.94.1452083195699; Wed, 06 Jan 2016 04:26:35 -0800 (PST) Date: Wed, 6 Jan 2016 13:26:30 +0100 From: "Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Subject: Re: [geda-user] A fileformat library (Blind vias, pad stack) Message-Id: <20160106132630.cb09e4544f9073b171978ac3@gmail.com> In-Reply-To: References: <1512221837 DOT AA25291 AT ivan DOT Harhan DOT ORG> <20160105182120 DOT 3237F809D79B AT turkos DOT aspodata DOT se> <8E0210CD-0694-4717-A7B1-3224E39691DA AT sbcglobal DOT net> 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 > I think this is a common misunderstanding. The reason PCB doesn't support > burried/blind via is like 5% file format and 95% all-internal-code-in-pcb. > (The 5-95 split is an educated guess, not a fact, but I believe it's not > far from reality). The 95% includes everything from find.c and DRC to > export HIDs and GUI HIDs. > > If we want blind/burried vias, we'll need to find how it is to be > represented in a save file eventually, but the bulk of the work won't be > around that part. > > Regards, > > Igor2 What do you think about group together a bunch of the ordinary drawing primitives and call it a: connection point, pad stack or pin? Do it need a new file format? Or could it be done with current file format maybe treated similar as a footprint? Further out: The same concept could be used both for ordinary pins and vias, only method to add them and what primitives to build them from would be different. Even though a drilled plated hole or a square of copper is the most common it would also be very general for the special cases. Since there usually are at least a different first pin and in some cases a few more different connection points it would probably be useful to put them in a library with sub folders for different package type: LQFP, QFN, DIP, ... Nicklas Karlsson