| ID: | 4473 |
| From: | Majenko Technologies <ma...@majenko.co.uk> |
| Date: | Tue, 27 Oct 2020 10:47:13 +0000 |
| Subject: | Re: [pcb-rnd] KiCad footprints |
| in-reply-to: | 4471 from ge...@igor2.repo.hu |
| replies: | 4476 from ge...@igor2.repo.hu |
--000000000000b0e0ef05b2a4c5a1 Content-Type: text/plain; charset="UTF-8" Yeah, I'm coming to the same realisation now after this discussion. The kicad format is inferior and will need manual conversion for it to be up to my exacting standards anyway, so manual it is. Still, it's good that we have access to large libraries of footprints through our import modules. Maybe we should be liaising with people like SnapEDA to help them build export modules for their systems to directly create lihata files. It would be more convenient for us, plus give us more exposure through the name being visible on big platforms alongside other EDA names... On Tue, Oct 27, 2020 at 3:15 AM <gedau@igor2.repo.hu> wrote: > > > On Mon, 26 Oct 2020, Majenko Technologies wrote: > > >Can we use kicad footprints as direct subcircuits in the footprint > library, > >or can we only import them into a layout then save the footprint to lht? > > Yes, the footprint library is not in any specific file format, you can put > anything in your library that pcb-rnd can load. The only reason we prefer > to have lihata subcircuits there because that won't have artificial > file-format limitations. > > However, using footprints coming from random sources may not be as cheap > as it first seems, there are fundamental (non-programming) problems beyond > data model differences or file format weakness: > > http://repo.hu/cgi-bin/pool.cgi?cmd=show&node=sef > > That said, if using a SEF still looks like the best option... If you are > doing any serious work, you will most likely end up tweaking each > footprint before use and then it's better to convert them to lihata as > first step so you don't need to worry about what details you are going to > lose because of the weaker file format. > > Conclusion: technically we can, but in practice, especially in > professional use cases, it's much less useful than it sounds. > > Regards, > > Igor2 > > > -- *Matt Jenkins* Majenko Technologies https://majenko.co.uk --000000000000b0e0ef05b2a4c5a1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Yeah, I'm coming to the same realisation now after thi= s discussion. The kicad format is inferior and will need manual conversion = for it to be up to my exacting standards anyway, so manual it is. Still, it= 's good that we have access to large libraries of footprints through ou= r import modules. Maybe we should be liaising with people like SnapEDA to h= elp them build export modules for their=C2=A0systems to directly create lih= ata files. It would be more convenient for us, plus give us more exposure t= hrough the name being visible on big platforms alongside other EDA names...= </div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">= On Tue, Oct 27, 2020 at 3:15 AM <<a href=3D"mailto:gedau@igor2.repo.hu">= gedau@igor2.repo.hu</a>> wrote:<br></div><blockquote class=3D"gmail_quot= e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)= ;padding-left:1ex"><br> <br> On Mon, 26 Oct 2020, Majenko Technologies wrote:<br> <br> >Can we use kicad footprints as direct subcircuits in the footprint libr= ary,<br> >or can we only import them into a layout then save the footprint to lht= ?<br> <br> Yes, the footprint library is not in any specific file format, you can put = <br> anything in your library that pcb-rnd can load. The only reason we prefer <= br> to have lihata subcircuits there because that won't have artificial <br= > file-format limitations.<br> <br> However, using footprints coming from random sources may not be as cheap <b= r> as it first seems, there are fundamental (non-programming) problems beyond = <br> data model differences or file format weakness:<br> <br> <a href=3D"http://repo.hu/cgi-bin/pool.cgi?cmd=3Dshow&node=3Dsef" rel= =3D"noreferrer" target=3D"_blank">http://repo.hu/cgi-bin/pool.cgi?cmd=3Dsho= w&node=3Dsef</a><br> <br> That said, if using a SEF still looks like the best option... If you are <b= r> doing any serious work, you will most likely end up tweaking each <br> footprint before use and then it's better to convert them to lihata as = <br> first step so you don't need to worry about what details you are going = to <br> lose because of the weaker file format.<br> <br> Conclusion: technically we can, but in practice, especially in <br> professional use cases, it's much less useful than it sounds.<br> <br> Regards,<br> <br> Igor2<br> <br> <br> </blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"= class=3D"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><b>Matt J= enkins</b><div>Majenko Technologies</div><div><a href=3D"https://majenko.co= .uk" target=3D"_blank">https://majenko.co.uk</a></div></div></div></div></d= iv> --000000000000b0e0ef05b2a4c5a1--
Reply subtree:
4473 Re: [pcb-rnd] KiCad footprints from Majenko Technologies <ma...@majenko.co.uk>
4476 Re: [pcb-rnd] KiCad footprints from ge...@igor2.repo.hu
4477 Re: [pcb-rnd] KiCad footprints from Majenko Technologies <ma...@majenko.co.uk>
4480 [pcb-rnd] edakrill and snapeda (was: Re: KiCad footprints) from ge...@igor2.repo.hu
4482 Re: [pcb-rnd] edakrill and snapeda (was: Re: KiCad footprints) from Bdale Garbee <bd...@gag.com>