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=20161025;
        h=date:from:to:subject:message-id:in-reply-to:references:mime-version
         :content-transfer-encoding;
        bh=9Eq/KcTrI0CP+Da7BI1H3CihIqzdU5dQ9bONKtbStFU=;
        b=vMQoN4ZEqXoc9PAMwguqdCUYyvKXYXEjuj22A+3VkIeEIamSy5pK/4+6wfr51DHnaN
         MVN4my1CFZ8Mhd7xCyB9djvNh1O/1ftszSltUMiNMFtydnO6NoJNLZg9At+qXA9i1xqg
         k9bMfiOjqXv2wp4mpw2fPjilPYOi3mAoW93vkYk8/rZkrK9oU8ZnG/g1ZkvTixCbcCM8
         8spkAofeY4pyRzWZepWWqv3QDKvJH8L5iC2UIrVNoWIfumbvU73Kc7VVQldwkve1NnPS
         mpTEOxQ81J23Ad90fbh+aRcV+/b1vPrkwUCJWyk8FaLiCO0O7FMfFbHAY/50onE2LMPK
         5YYw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to
         :references:mime-version:content-transfer-encoding;
        bh=9Eq/KcTrI0CP+Da7BI1H3CihIqzdU5dQ9bONKtbStFU=;
        b=gp569XKqHS5fpBxAHym8Q9MRY4sdcDJ7AimoO89SDVLJR+Z7P3rxqCYU4MxWTg4QUq
         cnFVwnSp9Q3ddzSnSdeZpkQe2ZwR3Nv61UVbRtaHmfSPCnk0otjZlA16FkrfgnL6woaC
         zgaNpr7OAri1N+juYO0zXDm5Iu+v9tK/sJmkVtLomlukKBNHnUWuCdqwvEkmx7H3XGBW
         0phXfc8qM7rumBDEscGjRboM7Yu3DL6DimaN7hhSzcBQ6H4n39bak/oDNHikfLkKbl4N
         WKFHgF7tJwhD4W8WaFkGLY2y9o9UMai5VfiMascIULxprI+HlJkHyCAY1u+7LHGzkFwP
         LvJw==
X-Gm-Message-State: AIVw113URbjj9OndoDmQAzTkBokhQrKKij+JY9JUxX2TzhKAHmUaKuNa
	MUYoP5dI5QO9Yvm9
X-Received: by 10.25.205.205 with SMTP id d196mr73698lfg.131.1499890182692;
        Wed, 12 Jul 2017 13:09:42 -0700 (PDT)
Date: Wed, 12 Jul 2017 22:09:39 +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] PCB, load element bug (know then but not why)
Message-Id: <20170712220939.d84b50bbcfc12076301d1ac7@gmail.com>
In-Reply-To: <alpine.DEB.2.00.1707122040160.27212@igor2priv>
References: <20170711005040 DOT d96eccaffe490027849789c3 AT gmail DOT com>
	<20170711020955 DOT 0108aaea AT akka>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1707110515450 DOT 27212 AT igor2priv>
	<20170711110940 DOT 84467c71877716992ddc3b11 AT gmail DOT com>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1707121629340 DOT 27212 AT igor2priv>
	<20170712201339 DOT bdab1cbf6238d8da3354e439 AT gmail DOT com>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1707122040160 DOT 27212 AT igor2priv>
X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.31; 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

> > You have or are planning a tree like structure like this: root object layout --> sub circuits --> footprints --> pads --> drawing primitives?
> >
> > In sort of any object could appear anywhere? To connect with netlist it must be possible to find footprints by refdes and pin number but otherwise what is counted as a pad os circuit is more about where they are saved?
> 
> What I already have:
> 
> board -> primitives
> 
> board -> subcircuit -> primitives
> 
> What I plan to have:
> 
> board -> subcircuit -> subcircuit -> ... -> primitives

At this point you only have to add a mechanism to tell which subcircuit is a footprint or pad. Then of course they need to be stored somewhere in a structured way.

> This also means a hierarchic pcb could reflect a hierarchic netlist which 
> in turn could be derived from a hierarchic schematics (low prio, long 
> term plan).
> 
> Pins & pads: I will implement what I've developed for tEDAx: there won't 
> be a special pin or pad object any more, but there will be logical 
> terminals. A terminal will have an ID, similar to pin or pad number now, 
> and other, optional metadata (such as symbolic name). You would just tag 
> any primitive within a subcircuit to belong to a specific terminal ID. 
> Or in other words, your "pin 1" could constructed of a via, your "pad 2" 
> could be a line, a polygon or even an arc, and your "pad 4" can be a 
> combination of any of the above.

Termal pads with irregular shapes are common. I do understand the details, you tag some object within sub circuit to tell they are a terminal but the actual sub circuit is a pin or pad?