X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Virus-Scanned:	Debian amavisd-new at papyrus.altaweb.hu
Date:	Sun, 13 Sep 2015 16:11:11 +0200
From:	"Lev (leventelist AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] Apollon
Message-ID:	<20150913161111.524dce3f@jive.levalinux.org>
In-Reply-To:	<20150913151852.7ca8ed54d2c8036e3e83222d@gmail.com>
References:	<20150913140631 DOT 1da1b78d AT jive DOT levalinux DOT org>
	<20150913151852 DOT 7ca8ed54d2c8036e3e83222d AT gmail DOT com>
X-Mailer:	Claws Mail 3.11.1 (GTK+ 2.24.27; amd64-portbld-freebsd10.1)
MIME-Version:	1.0
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id t8DEBJKd026123
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, 13 Sep 2015 15:18:52 +0200
"Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via
geda-user AT delorie DOT com]" <geda-user AT delorie DOT com> wrote:

> Holes usually span all layers but a buried via only span some layers.

Yes. There is the start_layer_id and the end_layer_id to specify which
prepreg _AND_ conductive layers shall the fab house drill. Or do you think
anything else?

> There is also the case with plugged vias, with hole in the board but
> not the copper or?

I don't know what is plugged via, but

http://www.pcbcic.com/docs/Via_and_SMask_design_guide4.pdf

says that a plugged via is filled with insulator material. This can be done.

I don't really understand what is the use of a via without copper. Can you
elaborate?

> The concept of a padstack seems good.

Thanks. That is the goal.
 
> Currently there are symbold in gschem and footprints in pcb, 4.5.2.3
> "component" is this the same as footprint?

Component is a logical data structure with default data of an instance of a
footprint on the board. Footprints (as in gEDA/pcb) is defined as sub-pcbs.
I'm just thinking of attaching primitive objects to the component itself, but
I think adding a pcb relation makes sense.

> Sometimes a local change on only one of several footprints of the
> same type is needed and if footprint is stored only once this must be
> work around in some way.

This is good that you brought this up. It would be nice if apollon/pcb could do the
same as gschem. Hierarchy.

Take this user story:

1. You are editing your top level pcb.
2. You find out that you need some change on one particular instance of
a footprint.
3. You press on "Down footprint"
4. You now edit this footprint.
5. When you satisfied with your changes, you can either
6a. Save this footprint, and all the instance will be changed, or,
6b. Save as something else, and replace the sub-pcb in the relation table.
This will affect only that particular instance.
7. You get a beer.

Later, you can export your sub-pcb to your library.

How's that sound?

Lev

-- 
73 de HA5OGL
Op.: Levente

- Raw text -