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=date:from:to:subject:message-id:in-reply-to:references:mime-version
         :content-type:content-transfer-encoding;
        bh=2NPv0SKaWUZXwXDzfeY2VnNyjTrE51HEHk1cg+mgFaE=;
        b=xNTwlsN1fawJYA1IZUjUYsKEsEAUV0jGJ8QBH0609E6fI1Mt1XYFkt7GZc24xjc3Xh
         aTDmGp67HUOCQCOmgDozzEpRkIkl+7fEcUGyDRPTp9jO5PVpRXXHyb/oLEj/ud+61XBC
         1pPxzjCsVUKuRpT7cYq8jf8DsERInECoe+xXTjEJLe6x1Ji0D3rhSW2HJ3N/n6laT2G6
         1UJMR/99Oi2B8kY+PnPez016bgMjs2cwnkA5OOT7WyQZvrBbGWu4vCx5en89eKuchbjc
         hP8/KW9oewFvdwu/zOnShbuRhAJUda7EPojL0HwDM9xp1PRYkdo6zp7/B47gRcmF2jpL
         vlvA==
X-Received: by 10.180.186.195 with SMTP id fm3mr7795371wic.1.1443979042186;
        Sun, 04 Oct 2015 10:17:22 -0700 (PDT)
Date: Sun, 4 Oct 2015 19:17:17 +0200
From: "Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] GTK3, Glade interface designer (router, auto?)
Message-Id: <20151004191717.bf8223417541a9306bfbd9ea@gmail.com>
In-Reply-To: <1443975731.671.52.camel@ssalewski.de>
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>
	<CAC4O8c_g7e562Gaotrbi6gLfjP6cJU1ys=MtEkDE7bSh4F9dfg AT mail DOT gmail DOT com>
	<1443975731 DOT 671 DOT 52 DOT camel AT ssalewski DOT de>
X-Mailer: Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
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

"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.
> 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
> 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. 
> 
> 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.
> 
> 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.
> Maybe you can -- there may exists some really smart ideas in his code.
> And the advantage of his code was that it works inside of PCB program
> already.
> 
> When you are generally interested in routing, you may consider the
> router of Alfons Wirts. Was something like freerouting.com, lately with
> copyright trouble but KiCad support, I have never really followed that
> project.