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=Lu8YygJ3p41AAi+jZ1Z0WHamjSEUXIOLHA3LxjBQonI=;
        b=LgBm+HC5EINitREa1akYomw+BuPtXCDOGmP6fRSNuHRgtqGl/DopOFO24+V2sMSSOy
         EJ5mjQWCs3VmmH3zzqYYXg5i26qAFIQ/5aPwaQArBM21tl6EnCqu6l0hqEM9f4ApJafk
         AZ+JY5fCkLnpCAbfWhN4fs0dH7nWc01LY6pFfCFgOcvy6C7Ut0pUZXz1hAhxlfZZaqR1
         HNso4e6dnwsiDZgQa5DIcZ5Gd1FcNCamxaURsB2Jkm4uDqt5JOiBmzU59Ib7tfQK061E
         8m13tJiSm5piPJKC8W25W8dWweQkzPJAfq3mRWv2UOvEdGYNQGRYplxrclsHKYXMGXWn
         D9VA==
MIME-Version: 1.0
X-Received: by 10.194.8.227 with SMTP id u3mr27292382wja.38.1444012199906;
 Sun, 04 Oct 2015 19:29:59 -0700 (PDT)
In-Reply-To: <5611BFC8.8050402@ecosensory.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>
	<5611BC63 DOT 6030408 AT ecosensory DOT com>
	<5611BFC8 DOT 8050402 AT ecosensory DOT com>
Date: Sun, 4 Oct 2015 18:29:59 -0800
Message-ID: <CAC4O8c86UuKmCRu6s95t2CCHzZku8OwXj-3=-SCzLLT20NEutw@mail.gmail.com>
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]" <geda-user AT delorie DOT com>
To: geda-user AT delorie DOT com
Content-Type: multipart/alternative; boundary=047d7b5d9c073a16c20521524ac0
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

--047d7b5d9c073a16c20521524ac0
Content-Type: text/plain; charset=UTF-8

On Sun, Oct 4, 2015 at 4:09 PM, John Griessen <john AT ecosensory DOT com> wrote:

> On 10/04/2015 06:55 PM, John Griessen wrote:
>
>> One way to do a workflow for an autorouter would be to export an outline
>> of the area to route up to, including some metal layer pieces with
>> netnames
>> to connect to, and all components
>>
>
>
> On second thought, that is probably too much for an external tool to do.
> So the external tool doesn't need to know footprints, just export the
> pins with netnames attached and let the router go,
> then import all except pins.  That's all the same result when the router
> never
> moves footprints.
>
> A router that works inside the layout program could do more.  Imagine tell
> it
> a gravity direction, have some parts placed and routed, or just marked as
> "hand routed", and power busses placed, then let the  router pour circuitry
> into the shape defined by the board outline, and already placed circuitry.
>

It might not have to be inside pcb to do this, it would just need to be
able to read the file format. Keep-outs of this sort are pretty straight
forward with the topo-router I think.  Being in pcb or having some render
capability might be nice if you want to cheat and make the cost function a
little bit interactive.  But generally its not an interactive algorithm,
nothing like push-shove at all.

--047d7b5d9c073a16c20521524ac0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Sun, Oct 4, 2015 at 4:09 PM, John Griessen <span dir=3D"ltr">&lt;<a =
href=3D"mailto:john AT ecosensory DOT com" target=3D"_blank">john AT ecosensory DOT com</=
a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">On =
10/04/2015 06:55 PM, John Griessen wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
One way to do a workflow for an autorouter would be to export an outline<br=
>
of the area to route up to, including some metal layer pieces with netnames=
<br>
to connect to, and all components<br>
</blockquote>
<br>
<br></span>
On second thought, that is probably too much for an external tool to do.<br=
>
So the external tool doesn&#39;t need to know footprints, just export the<b=
r>
pins with netnames attached and let the router go,<br>
then import all except pins.=C2=A0 That&#39;s all the same result when the =
router never<br>
moves footprints.<br>
<br>
A router that works inside the layout program could do more.=C2=A0 Imagine =
tell it<br>
a gravity direction, have some parts placed and routed, or just marked as<b=
r>
&quot;hand routed&quot;, and power busses placed, then let the=C2=A0 router=
 pour circuitry<br>
into the shape defined by the board outline, and already placed circuitry.<=
br></blockquote><div><br></div><div style=3D"">It might not have to be insi=
de pcb to do this, it would just need to be able to read the file format. K=
eep-outs of this sort are pretty straight forward with the topo-router I th=
ink.=C2=A0 Being in pcb or having some render capability might be nice if y=
ou want to cheat and make the cost function a little bit interactive.=C2=A0=
 But generally its not an interactive algorithm, nothing like push-shove at=
 all.</div><div>=C2=A0</div></div></div></div>

--047d7b5d9c073a16c20521524ac0--