Mail Archives: geda-user/2015/10/25/16:09:32
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-694492957-1445803884=:7137
Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE
On Sun, 25 Oct 2015, Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user=
@delorie.com] wrote:
>
>The geometry code in search.c and find.c is messy.=C2=A0 There's no geomet=
rical
>abstraction and everything is done from ad-hoc calculations off the traces
>themselves.=C2=A0 There are bugs.
>
>I'd like to add a module that does simple 2D geometry, e.g. Vec Line LineS=
ec
>Circle Ellipse Arc etc. as purely geometrical objects.
I fully agree. I am bumping into this again and again, last with the drag=
=20
cycling feature. Simple things like "do these two line segments=20
intersect?" don't seem to have generic, simple functions that could be=20
called from higher level code.
>
>Igor I think you're doing similar stuff perhaps we could coordinate.
Yup, we should.
>The alternative would be to use some existing geometry library e.g. CGAL,
>Gemotry Engine, GEOS.=C2=A0
>They are arguably much more than needed but on the other hand Stephan's
>toporouter already needs something like that anyway.
I think the toporouter uses gts.
I have a half-finished coordgeo gpmi package in the pcb-rnd code,=20
originally I wanted to get that handle all these, but I got lazy.
Regards,
Igor2
--0-694492957-1445803884=:7137--
- Raw text -