delorie.com/archives/browse.cgi   search  
Mail Archives: geda-help/2016/07/28/18:48:39

X-Authentication-Warning: delorie.com: mail set sender to geda-help-bounces using -f
Date: Thu, 28 Jul 2016 18:48:29 -0400
Message-Id: <201607282248.u6SMmTxw006065@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: geda-help AT delorie DOT com
In-reply-to: <20160728192015.4fc84ce8@debian.olsr> (geda-help@delorie.com)
Subject: Re: [geda-help] pcb: blind via
References: <20160728160657 DOT 7f68f787 AT debian>
<20160728174027 DOT 453b2b41 AT debian DOT olsr> <20160728192015 DOT 4fc84ce8 AT debian DOT olsr>
Reply-To: geda-help AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-help AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com

> > I need the Info for VIA, is the Layer Part of the VIA.
> > I need a new Button to break VIA on specific Layer.
> > 
> > * Botton for disable Via on Layer x.
> > * Modify pcb-file with this Info.
> > * Modify Gerber-file with this Info.
> 
> I think the blind via is one of the important features, not nice to
> have!  If some body show me the point in the code, is try to insert
> the code.  But, only in C or Python. I will not learn a new
> language.

There's a couple parts of the problem, which end up scattered among
various parts of pcb...  and I think someone has done part of the work
already, a bit of searching should find a patch.

* How is a blind/buried via represented internally?  Can that
  represent all possibilities that a FAB house can make?

* How do you edit them in the GUI, or even draw them on the screen?

* What changes to the file format will be needed?  Are they backward
  compatible?

* What about DRC, optimizers, autorouters, and exporters?  Do they
  need changes to handle them?

* What about the gerber exports?  How do we break down the drills so
  that FABs "just know" what to do with them?

What makes this a tough problem is that you have to have at least a
*bad* solution to *all* of the above, to be able to use it at all.  A
*good* solution still needs to cover *all* the above.  Getting part
way through and hitting a problem can be very discouraging, but if
you're up to the challenge, we can point out the specific source files
you'll need to deal with.

And PCB at the moment is pure C, although we prefer you avoid things
that aren't also C++ (i.e. don't use a variable named "class" ;)

If you're interested, find the "tracking the latest" info here:
http://pcb.geda-project.org/obtaining.html

That will get you a source tree you can build and play with.  Also,
the geda-users mailing list or #geda on OFTC are good places to talk
about the PCB internals.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019