| ID: | 3893 |
| From: | ge...@igor2.repo.hu |
| Date: | Thu, 2 Apr 2020 16:10:09 +0200 (CEST) |
| Subject: | Re: [pcb-rnd] drc: implement dru files |
| in-reply-to: | 3892 from Alain Vigne <al...@gmail.com> |
This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-1919249368-1585836115=:10103 Content-Type: TEXT/PLAIN; CHARSET=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Content-ID: <alpine.DEB.2.00.2004021604251.10103@igor2priv> On Thu, 2 Apr 2020, Alain Vigne wrote: >See https://uk.beta-layout.com/pcb/technology/specifications/ >for "English description". I prefer "graphical description", but OK.=C2=A0= I copy >& paste, here: Sorry, there's a misunderstanding.=20 My porposal: you do the DRU interpretation part and I do the pcb-rnd-side= =20 coding. My example DRU files contain fileds like mdPadPad with a single coord=20 value and psFirst with an unitless numeric value and mtIsolate with a list= =20 of coord values. What's needed is exact rules, things we need to check, one by one, using=20 pcb-rnd terminology, written in English, using these named fields from the= =20 DRU file for parameters. That'd be the DRU->English translation from which= =20 I can then do the scripting. (It's actual work that unfortunately needs to= =20 be done by someone and I don't think could be substituted by pasting parts= =20 of some spec. If you can do that, that means there's enough demand on DRU= =20 for me to invest my time on the scripting.) Regards, Igor2 --0-1919249368-1585836115=:10103--
Reply subtree:
3893 Re: [pcb-rnd] drc: implement dru files from ge...@igor2.repo.hu