X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Virus-Scanned: by amavisd-new (Uni-Kiel/l3ms-sc) From: geda AT psjt DOT org (Stephan =?utf-8?Q?B=C3=B6ttcher?=) To: geda-user AT delorie DOT com Subject: Re: [geda-user] A fileformat library 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> Date: Wed, 06 Jan 2016 15:21:18 +0100 In-Reply-To: (gedau AT igor2 DOT repo DOT hu's message of "Wed, 6 Jan 2016 12:46:28 +0100 (CET)") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id u06ELOfq029049 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 gedau AT igor2 DOT repo DOT hu writes: > On Wed, 6 Jan 2016, Stephan Böttcher wrote: >> Step 1. teach PCB to read this format within scripts. Throw Errors when >> something is drawn where the current data model does not allow. >> >> Step 1b: allow this format in layout files. >> >> Step 2. teach PCB to write this format. >> >> Steps 3...: change the internal data model to support more and more of cases. > > 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. This thread was about file formats. How a burried via is implemented and presented by the GUI may need a lot ow work. I do not see a problem with a file format that can express more that the tool can not yet support. It help anybody with some spare cycles to work on missing features, if the file format already supports it. At the time that work is done, the file format may need to be extended again. But if we extend the format with a view towards othogonality and extendability, that may not be much of a problem. -- Stephan