X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type;
	bh=wlGFJ4sdAu+TLDkxdXND+tvG8LzxsOAdubgYnPeM4Nc=;
	b=TbzswCPVn8m+R3O3qzXd+uqR2XwT1f6i4Q6erBmVUeUAAJGb2jJJAH4nzeR+d+CdxP
	K/C8OsRQuxKd4sFTlOM93p9YPSQKbTwenW3A3lXn0/Q+2E6Bok/aG4EVJhoeKKvSN841
	ICEJge/w0oBJGBUI5x7beeCLE0rRwWTMgXXi1BbAaLcuyx77zCOolIH5qFkbUfV4X+Wo
	vO/vTwOWSLpfksjnE+qmVZQACBj27BkQp9vGrB45gN94p3RQlhlYSyyTALZAjA7D2nXq
	17NA2WvgepST/fpzt1NVduyWxxVTbf3RsbEPgJ+CWLxTNYUm663vX1PjWq4sGILfY8Bo
	Laaw==
MIME-Version:	1.0
X-Received:	by 10.182.199.70 with SMTP id ji6mr54281873obc.3.1426630408919;
	Tue, 17 Mar 2015 15:13:28 -0700 (PDT)
In-Reply-To:	<20150317192343.26859.qmail@stuge.se>
References:	<CAHLh21Cdm=YZuqCQ+gCHSviJquahr6cnAQ-VBLR4BSs-nfHOig AT mail DOT gmail DOT com>
	<CAOFvGD4+4bHXNYLvePi70wb_1A4=dQgb_Ov3xBghoKbXQUsSGA AT mail DOT gmail DOT com>
	<5508413E DOT 4000405 AT ecosensory DOT com>
	<C2997FC5-EE8B-47E4-A8D5-24B6D22B2D64 AT noqsi DOT com>
	<20150317182617 DOT 22729 DOT qmail AT stuge DOT se>
	<CAOFvGD7vgcVoHw6OeE98iA60755n8gbs6jbtv56O5+AcqWM1vQ AT mail DOT gmail DOT com>
	<20150317192343 DOT 26859 DOT qmail AT stuge DOT se>
Date:	Tue, 17 Mar 2015 18:13:28 -0400
Message-ID:	<CAOFvGD6xHWE_M0E7Ho6XWZvROXYq9z7ES3pLq-98XPpPp=9Whg@mail.gmail.com>
Subject:	Re: [geda-user] pcb alternatives
From:	Jason White <whitewaterssoftwareinfo AT gmail DOT com>
To:	geda-user AT delorie DOT com
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 Tue, Mar 17, 2015 at 3:23 PM, Peter Stuge <peter AT stuge DOT se> wrote:
> Jason White wrote:
>> > Which elementary objects would you use instead
>>
>> (1) to contain graphical primitives
>
> Which are the primitives you have in mind?

Only 5 primitives in conjunction with groups that posses attributes
are needed to represent an entire PCB design.
* Line
* Arc
* Polygon
* Circle
* Text

Each primitive defines its coordinates and layer relative to the group
(ie. "one layer above the group" or "on the same layer as the group").
If a group gets moved, so does its contents. Each graphical primitive
then declares what component of the physical layer of represents
(copper, solder mask, silk screen, keepout, etc.). This way the solder
mask is a seperate "layer" than the copper traces, silkscreen, and
etc. All graphical primitives are allowed on every physical layer
(top, bottom, inner 1, inner 2 ...) and on every layer component
(copper, silkscreen, solder paste, etc...).

Examples of Layer Components:
* Copper
* Solder Mask
* Solder Paste
* Silkscreen
* Board Outline
* Drill
* Assembly Drawing
* Keepout

Going about things in this manner makes it so that PCB is dealing with
groups of the basic shapes instead of special objects for each layer.
It is very much what I would like to see from PCB.


I actually had started to collect my thoughts on this matter into a
document. You can read more here if you'd like. Of course its
unfinished, so the descriptions are a bit rough.

* https://drive.google.com/file/d/0BwP0qhqyaTIIV2c1TnJYd2JvQms/view?usp=sharing



-- 
Jason White

- Raw text -