X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
Date: Wed, 24 Oct 2012 14:42:24 -0400
Message-Id: <201210241842.q9OIgOlN001120@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: geda-user AT delorie DOT com
In-reply-to: <20121024113238.GP32696@fi.muni.cz> (message from Jan Kasprzak on
	Wed, 24 Oct 2012 13:32:38 +0200)
Subject: Re: [geda-user] Trace width - best practices?
References: <20121023192443 DOT GK524 AT fi DOT muni DOT cz>
 <CAKakQccEOLFD0bbe6ydry-6YN7xsvjJAcbrTSt6DAYHJN-ohrA AT mail DOT gmail DOT com> <20121024113238 DOT GP32696 AT fi DOT muni DOT cz>
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


> However, I can offer my students to do some improvements to gEDA as
> their semestral project, if you (and they!)  are interested.  The
> problem is somebody would have to mentor them, and from my
> experience, the results can be of varying quality: there are
> excellent students, but there are also bad ones, who cause only a
> loss of mentor's time in exchange for an unusable result.

I'm generally available to explain the code on the #geda IRC forum.

> 	Can optimizers be applied to manually routed traced as well?

Yes, there's a checkbox in the menu for whether that happens or not.

> 	OK, I will try to route the wide paths manually, but I am probably
> no match for the pcb autorouter :-)

You'd be surprized - I typically do *not* use the autorouter because I
can do a better job (although not nearly a *faster* job, assuming the
autorouter can complete the task at all)