X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=T2UE8D4xCRNy8cD5jOwjUgzl8p80hbojHwEtWpT2F78=; b=Lmy/9kpOlA+5hsyVEByzjnE4CxmprpwdWtLcqEn88sjNU1OZdiDpJaR9uLidh0vkVo W8scHu+VIOMvVXfaXuf2I9IDJEJ23YoomgHnWV8x5gG3k3se0RqAQrVQB9BrUrYp3LF9 UQhydJQ99Di34t+7AwsDmHlpWbv/NVtOCRqcY9KjrRAbbh8mp5puQyx9rgvDGxbrEvZV mDLka7ZxGtaDzNoqOJpDx6CLJ81enPFi7+iOSnBg09zwosCPpNVp5dXye0fxY1vGDuGS rxOLBLaBi0R4rY7tcb9ShS3T3SuUsSVcRyNnDIawIEc8sUYi/M+KQ+c4VxiTN0ylQfxz +Sew== MIME-Version: 1.0 X-Received: by 10.180.93.168 with SMTP id cv8mr8415428wib.54.1443993412621; Sun, 04 Oct 2015 14:16:52 -0700 (PDT) In-Reply-To: <20151004191717.bf8223417541a9306bfbd9ea@gmail.com> References: <20151003210701 DOT de392b925f54dadb0a5fedd8 AT gmail DOT com> <1443903758 DOT 1873 DOT 13 DOT camel AT ssalewski DOT de> <56104A0A DOT 9020507 AT xs4all DOT nl> <1443909591 DOT 1873 DOT 18 DOT camel AT ssalewski DOT de> <1443975731 DOT 671 DOT 52 DOT camel AT ssalewski DOT de> <20151004191717 DOT bf8223417541a9306bfbd9ea AT gmail DOT com> Date: Sun, 4 Oct 2015 13:16:52 -0800 Message-ID: Subject: Re: [geda-user] GTK3, Glade interface designer (router, auto?) From: "Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Content-Type: multipart/alternative; boundary=f46d043c7fba6ade4805214deaad 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 --f46d043c7fba6ade4805214deaad Content-Type: text/plain; charset=UTF-8 On Sun, Oct 4, 2015 at 9:17 AM, Nicklas Karlsson ( nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com] < geda-user AT delorie DOT com> wrote: > "The code is easy, short, and mostly based on that PhD thesis." If it is > based on PhD thesis it probably have a very good theoretical base, can you > bring some light ont this? > > The only thing I have against curved traces is the extra time needed tom > make tghem. > > Nicklas Karlsson > > > > On Sat, 2015-10-03 at 15:16 -0800, Britton Kerin > > (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com] wrote: > > > How is your work on the topo router coming? I have a good blob of > > > free time > > > coming soon and I'm planning to spend it on router. > > > > > > It looks like your router does the layer part, and what's left is the > > > the > > > interlayer > > > stuff? Are there still crashers in the intra-layer part? > > > > I have worked only in 2013 on that router. Was much fun and I was > > impressed by the results. But there was nearly no interest by others, I > > think here on the list was one moderately positive comment, and in a > > German forum where I mentioned the router there was no reaction at all. > Well I thought it was all really exciting, but it wasn't obvious how it could be integrated with pcb (being in Ruby). But now some serious efforts are being considere to make a much more accessible file format (via sql and YAML) so it could be provided as a stand-alone tool that would be useful to pcb users. > > People seem to prefer manually routing, and many seem to not like > > curved traces. > > > > I do not really understand your term "intra-layer". My router is using > > arbitrary numbers of layers, and it connect the layers with > > automatically placed vias. Testing was done with two layers. I have > > some problems remembering details, have not touched it for more than > > too years. I think no crashes. The problem is, that there can remain > Great! I had the impression from pics on your site and something Kai said that just the rubber band part was done. > > unrouted traces due to space constraints. So some user interaction > > would be needed, for example for moving parts. Coding that part would > > be the fastest way to make that router useful, but coding that part is > > not really much fun and take some time. And when no one is interested > > at all? Making the router working without user interaction may be more > > interesting, that would include moving components. But that is more > > difficult and would need some time for coding. > I take it the remaining traces are really hard to subsequently add by hand? Are there options other than moving parts to make is useful, maybe somehow less ambitious or cost function rewards "ports" or something? > > But I think I will continue at some time. The code is easy, short, and > > mostly based on that PhD thesis. But I have never cleaned it up > > unfortunately, and for latest CGAL and Ruby 2.2 some fixes may be > > necessary. Porting to Nim would be nice, but for that I would have to > > create bindings for CGAL first. Porting to C++ would be an option too > > of course, then I need no CGAL bindings, and integration in PCB program > > is easier. But that would be no fun for me. > I would rather it stay Ruby, rather than be ported to any of those other things. In addition to not being fun it would make it less accessible I think. I looked at the Ruby at the time and it seemed quite nice. > > > > Have you ever looked at the code of Anthony's toporouter? I tried a few > > hours in 2012 and early 2013, but really understood nearly nothing. > I tried yes. Your Ruby is far more readable and maps much more clearly to the thesis. > > Maybe you can -- there may exists some really smart ideas in his code. > Like what? > > And the advantage of his code was that it works inside of PCB program > > already. > Honestly I have big doubts that it ever fully worked, or he would have hung around to collect the plaudits rather than insulting everyone and vanishing like he did. As for inside pcb, hopefully this will not be so big a deal soon. It's a batch-mode algorithm anyway. --f46d043c7fba6ade4805214deaad Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Sun, Oct 4, 2015 at 9:17 AM, Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com] <geda-use= r AT delorie DOT com> wrote:
"= ;The code is easy, short, and mostly based on that PhD thesis." If it = is based on PhD thesis it probably have a very good theoretical base, can y= ou bring some light ont this?

The only thing I have against curved traces is the extra time needed tom ma= ke tghem.

Nicklas Karlsson


> On Sat, 2015-10-03 at 15:16 -0800, Britton Kerin
> (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]= wrote:
> > How is your work on the topo router coming?=C2=A0 I have a good b= lob of
> > free time
> > coming soon and I'm planning to spend it on router.
> >
> > It looks like your router does the layer part, and what's lef= t is the
> > the
> > interlayer
> > stuff?=C2=A0 Are there still crashers in the intra-layer part? >
> I have worked only in 2013 on that router. Was much fun and I was
> impressed by the results. But there was nearly no interest by others, = I
> think here on the list was one moderately positive comment, and in a > German forum where I mentioned the router there was no reaction at all= .

Well I thought it was all = really exciting, but it wasn't obvious how it could be integrated with = pcb (being in Ruby).=C2=A0 But now some serious efforts are being considere= to make a much more accessible file format (via sql and YAML) so it could = be provided as a stand-alone tool that would be useful to pcb users.
<= div>=C2=A0
> People seem to prefer manually routing, and many seem to not like
> curved traces.
>
> I do not really understand your term "intra-layer". My route= r is using
> arbitrary numbers of layers, and it connect the layers with
> automatically placed vias. Testing was done with two layers. I have > some problems remembering details, have not touched it for more than > too years. I think no crashes. The problem is, that there can remain

Great!=C2=A0 I had the impres= sion from pics on your site and something Kai said that just the rubber ban= d part was done.
=C2=A0
> unrouted traces due to space constraints. So some user interaction
> would be needed, for example for moving parts. Coding that part would<= br> > be the fastest way to make that router useful, but coding that part is=
> not really much fun and take some time. And when no one is interested<= br> > at all? Making the router working without user interaction may be more=
> interesting, that would include moving components. But that is more > difficult and would need some time for coding.
I take it the remaining traces are really hard to s= ubsequently add by hand?=C2=A0 Are there options other than moving parts to= make is useful, maybe somehow less ambitious or cost function rewards &quo= t;ports" or something?
=C2=A0
> But I think I will continue at some time. The code is easy, short, and=
> mostly based on that PhD thesis. But I have never cleaned it up
> unfortunately, and for latest CGAL and Ruby 2.2 some fixes may be
> necessary. Porting to Nim would be nice, but for that I would have to<= br> > create bindings for CGAL first. Porting to C++ would be an option too<= br> > of course, then I need no CGAL bindings, and integration in PCB progra= m
> is easier. But that would be no fun for me.

I would rather it stay Ruby, ra= ther than be ported to any of those other things.=C2=A0 In addition to not = being fun it would make it less accessible I think.=C2=A0 I looked at the R= uby at the time and it seemed quite nice.
=C2=A0
>
> Have you ever looked at the code of Anthony's toporouter? I tried = a few
> hours in 2012 and early 2013, but really understood nearly nothing.

I tried yes.=C2=A0 Your Ruby i= s far more readable and maps much more clearly to the thesis.
=C2= =A0
> Maybe you can -- there may exists some really smart ideas in his code.=

Like what?
=C2=A0=
> And the advantage of his code was that it works inside of PCB program<= br> > already.

Honestly I hav= e big doubts that it ever fully worked, or he would have hung around to col= lect the plaudits rather than insulting everyone and vanishing like he did.= =C2=A0 As for inside pcb, hopefully this will not be so big a deal soon.=C2= =A0 It's a batch-mode algorithm anyway.
=C2=A0
--f46d043c7fba6ade4805214deaad--