X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Message-ID:	<1445008372.2017.37.camel@ssalewski.de>
Subject:	Re: [geda-user] GTK3, Glade interface designer (router, auto?)
From:	Stefan Salewski <mail AT ssalewski DOT de>
To:	geda-user AT delorie DOT com
Date:	Fri, 16 Oct 2015 17:12:52 +0200
In-Reply-To:	<CAC4O8c_o6zem5Kfr89BR3jBZBiNj78vR80-4W+B7YhHOiY2=Ww@mail.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>
	<CAC4O8c_g7e562Gaotrbi6gLfjP6cJU1ys=MtEkDE7bSh4F9dfg AT mail DOT gmail DOT com>
	<1443975731 DOT 671 DOT 52 DOT camel AT ssalewski DOT de>
	<20151004191717 DOT bf8223417541a9306bfbd9ea AT gmail DOT com>
	<CAC4O8c9Bi5HJfcW6wUgm_+4O2gs4vDdBMbS2hF_0dCqnBuJahQ AT mail DOT gmail DOT com>
	<1443997480 DOT 2068 DOT 32 DOT camel AT ssalewski DOT de>
	<CAC4O8c-bnGky=Nab59-pOTJkB8Q9Tc5t5hqE+dnEF-777hUjMg AT mail DOT gmail DOT com>
	<1444070851 DOT 1014 DOT 20 DOT camel AT ssalewski DOT de> <muv4ua$hat$1 AT ger DOT gmane DOT org>
	<1444157156 DOT 1949 DOT 52 DOT camel AT ssalewski DOT de> <56141CCE DOT 2030301 AT ecosensory DOT com>
	<1444165764 DOT 1949 DOT 78 DOT camel AT ssalewski DOT de> <mv4l1j$c2c$1 AT ger DOT gmane DOT org>
	<CAC4O8c_o6zem5Kfr89BR3jBZBiNj78vR80-4W+B7YhHOiY2=Ww AT mail DOT gmail DOT com>
X-Mailer:	Evolution 3.16.5
Mime-Version:	1.0
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

On Sun, 2015-10-11 at 14:42 -0800, Britton Kerin
(britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com] wrote:
> On Wed, Oct 7, 2015 at 6:39 PM, Kai-Martin Knaak <kmk AT familieknaak DOT de>
> wrote:
> 
> > Stefan Salewski wrote:
> > 
> > > The toporouter as described in in the PhD thesis of Tal Dayan from
> > > 1997 assumes that there is an empty area for routing, which is only
> > > restricted by the size of pads and pins. So each already existing
> > > trace is a problem.
> > 
> > I suspected so. So this is worse than just a not yet coded feature.
> > Unfortunately, doing some portions in advance manually is key to deal
> > with many special cases. Examples:
> > 
> 
> Yes I like to do manual first too.  To make it useful, what's needed is
> first a "discovery pass"
> on the existing board to take it back to topology.  I think you can't put
> that much burden
> of keep-outs on cost function or geometry portion of the algorithm and have
> it work right.
> I've very excited to try to write this if someone else doesn't beat me to
> it:)
> 
> Britton

Yesterday I have launched the router again -- first time after two
years. I have forgotten a lot, but a plain "ruby router.rb" gave me some
fresh pictures, so it seems still be working with Ruby 2.2, CGAL 4.6,
Boost 1.57 and cairo 1.14.

For your idea of allowing prerouted manual traces: One solution would be
to cover that traces with pads and pins, so autorouter will know that
the area is occupied. That is some work coding it. For very special
cases that may make sense. But generally I think that the effort is not
really justified, and it will restrict the autorouter very much. Why do
you think you need manually routed traces at all? Generally we can tell
the autorouter to do all well. Matched pairs and Stripline/Microstrip
transmission lines may be very problematic of course. But for those one
can reserve areas by placing a large pad somewhere, or by reserving
complete layers for that.

I will try to put the Appolonius wrapper on my page this weekend, and
maybe I will put a packet with all necessary wrappers and a built script
together. Then testing will be easier. I am currently trying to remember
how I did the traces export for the example picture on my page...

- Raw text -