X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Message-ID: <53BDCDBA.4060005@sonic.net> Date: Wed, 09 Jul 2014 16:18:18 -0700 From: Dave Curtis User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121028 Thunderbird/16.0.2 MIME-Version: 1.0 To: geda-user AT delorie DOT com Subject: Re: [geda-user] pour clearing around pads References: <201407091750 DOT s69HofTL021912 AT envy DOT delorie DOT com> <53BDBC7A DOT 5070709 AT sonic DOT net> <201407092223 DOT s69MN0iE000952 AT envy DOT delorie DOT com> In-Reply-To: <201407092223.s69MN0iE000952@envy.delorie.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Sonic-ID: C;hF68T78H5BGN/E2zUc16mQ== M;2GDyT78H5BGN/E2zUc16mQ== X-Spam-Flag: No X-Sonic-Spam-Details: 0.0/5.0 by cerberusd Reply-To: geda-user AT delorie DOT com On 07/09/2014 03:23 PM, DJ Delorie wrote: >> And what are the chances of this happening in pcb? Is that a doable >> change? > Someone would have to have the drive and time to do it. I think it's > a fundamental change to the pcb internals, which means it touches most > of the code. > Seems like this is intertwined with a road-map discussion. It comes back to incremental change versus "boil the ocean." I don't have a lot of visibility into what ideas cross over from incremental to infrastructure. OTOH, maybe its good that I don't have that coloring my thought process. Given a "future footprint" specification perhaps there is a way to pull incremental changes out of it that are easy to implement in the current engine, and then as the infrastructure comes on line more pieces of it can be enabled. Or, maybe there is "future footprint" and "transition footprint" format.