| www.delorie.com/archives/browse.cgi | search |
--089e0122f088133a200528b27892 Content-Type: text/plain; charset=UTF-8 On Tue, Jan 5, 2016 at 11:53 PM, Nicklas Karlsson ( nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com] < geda-user AT delorie DOT com> wrote: > > I recently did a tiny bit of work on the parser in pcb. Of course we > > should continue to support it, but it's going to be tough to extend it > > much. It's already overloaded in weird ways (e.g. thermals are parsed as > > flags, with their own non-flex sub-syntax, even though they don't set any > > actual flags). If you do extend it you do hard work and still only pcb > can > > read it. Of course you still have to teach the innards of pcb about your > > extensions in order for them to do anything useful. > > A good start might be to write down what need to be stored even though > they are not implemented right now and maybe never will be: > 1. Padstack, probably as collection of ordinary drawing primitives. > 2. Local copy and reference so update is possible. > 3. Net and possible segment attribute for route style, width. > 4. Net clerances between any net. > 5. Net clerance classes although (4.) could be extended before entering > pcb. > 6. Trace impedance. > 7. Differential impedance? > 8. Pin swapping! > 9. Slot swapping. > Lev did something very like this last time this got discussed as sql schema. I don't think it had all the above but some of it. Britton --089e0122f088133a200528b27892 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo= te">On Tue, Jan 5, 2016 at 11:53 PM, Nicklas Karlsson (<a href=3D"mailto:ni= cklas DOT karlsson17 AT gmail DOT com">nicklas DOT karlsson17 AT gmail DOT com</a>) [via <a href= =3D"mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT com</a>] <span dir=3D"l= tr"><<a href=3D"mailto:geda-user AT delorie DOT com" target=3D"_blank">geda-use= r AT delorie DOT com</a>></span> wrote:<br><blockquote class=3D"gmail_quote" st= yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span= class=3D"">> I recently did a tiny bit of work on the parser in pcb.=C2= =A0 Of course we<br> > should continue to support it, but it's going to be tough to exten= d it<br> > much.=C2=A0 It's already overloaded in weird ways (e.g. thermals a= re parsed as<br> > flags, with their own non-flex sub-syntax, even though they don't = set any<br> > actual flags).=C2=A0 If you do extend it you do hard work and still on= ly pcb can<br> > read it.=C2=A0 Of course you still have to teach the innards of pcb ab= out your<br> > extensions in order for them to do anything useful.<br> <br> </span>A good start might be to write down what need to be stored even thou= gh they are not implemented right now and maybe never will be:<br> =C2=A0 1. Padstack, probably as collection of ordinary drawing primitives.<= br> =C2=A0 2. Local copy and reference so update is possible.<br> =C2=A0 3. Net and possible segment attribute for route style, width.<br> =C2=A0 4. Net clerances between any net.<br> =C2=A0 5. Net clerance classes although (4.) could be extended before enter= ing pcb.<br> =C2=A0 6. Trace impedance.<br> =C2=A0 7. Differential impedance?<br> =C2=A0 8. Pin swapping!<br> =C2=A0 9. Slot swapping.<br></blockquote><div><br></div><div style=3D"">Lev= did something very like this last time this got discussed as sql schema.= =C2=A0 I don't think it had all the above but some of it.</div><div>=C2= =A0</div><div style=3D"">Britton</div><div><br></div></div></div></div> --089e0122f088133a200528b27892--
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |