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=date:from:to:subject:message-id:in-reply-to:references:mime-version
         :content-type:content-transfer-encoding;
        bh=OfVM/3BapalkYfktpR4eorcSaxm/ClGkmiyLSz+Z+T0=;
        b=qK0KbJVSg1FtgIqEM5YMlm2wSzybcmV3EpaW7qVD5/sByXKSasdgRo5Eazp/zZjU6i
         s25PXdHk1gQiHgnccWzc4PiEO0QCmQ4vkXKHPtMgY5f84VRXmxlba5PvjHOuBwSGcHsz
         G5UvlHwKnBm4KwalWMX8m5WzMCfY1uO4fIUh+QE4cQdEo04MwcmlJKq/uM09cyEpIpxl
         +3yg4ZwMefhLgYeFhaC1rZqadJjEvWprDyT1KcyQjdYPs1mwo/T3xeiP9+gS3InpufsJ
         mAFt22wBo4AnK2QJ+MSsfyeOcj5thUj1noTp/27YFlxrllcoQrx2UevteRLDq+QONZWf
         Q5HQ==
X-Received: by 10.180.187.244 with SMTP id fv20mr16436134wic.23.1442150337791;
        Sun, 13 Sep 2015 06:18:57 -0700 (PDT)
Date: Sun, 13 Sep 2015 15:18:52 +0200
From: "Nicklas Karlsson (nicklas DOT karlsson17 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: <20150913151852.7ca8ed54d2c8036e3e83222d@gmail.com>
In-Reply-To: <20150913140631.1da1b78d@jive.levalinux.org>
References: <20150913140631 DOT 1da1b78d AT jive DOT levalinux DOT org>
X-Mailer: Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
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

> I finished the documentation of my proposed data structure. I pushed it
> into the home/lev/apollon branch. There are slight changes from the
> former version.
> 
> Please give me feedback. This is my first push into the repository, so I'm
> also open to comments about usual commit messages, etc.
> 
> I also attach a pdf of my document.
> 
> The next step is to make a decision on data structure, and how to implement
> that in gEDA/pcb.

Holes usually span all layers but a buried via only span some layers. There is also the case with plugged vias, with hole in the board but not the copper or?

The concept of a padstack seems good.

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

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.