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=UmoVMoR8p4MXoLECh3u+dTmQj4fopB5cWdppKKoBrwk=; b=K4QdSGKueoj9ezgjA1rJgun3Lyc63R4O3Y/uz75ZbWNxzLKSDm3tK+APx0ysYvLODa tS5eCNwNV/FTTJUDgka/TPdVVeynPJU+Bz72jdLByhV1Pct5YtaAfWeSm/xmIWbjpG6s d/7EQT/GOA5he0tYeCvg6GpRwiI4wAWrCH0uuntoQ0XAQ07JmIIRhzid3M3VJ2jm8TAm 3A42sYrQANjjsEoeNCJ7cRSwx1T3+0wuMDeQLyHJcZih5T9hR3g/nyNGBsQnbuso213r 31xhLhL12Z3EwBQ7rYenxjn93hOOimX/uyiB1ZTK3TZdknn7RivYW0gHhSdVyeH6vB2P s88Q== X-Received: by 10.112.184.199 with SMTP id ew7mr7528653lbc.134.1452360687813; Sat, 09 Jan 2016 09:31:27 -0800 (PST) Date: Sat, 9 Jan 2016 18:31:26 +0100 From: "Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Subject: Re: [geda-user] (features: layers stack, padstack/vias) Message-Id: <20160109183126.eb5620ceb1eb493124d06495@gmail.com> In-Reply-To: References: <1512221837 DOT AA25291 AT ivan DOT Harhan DOT ORG> <20160106091006 DOT 5F67B809D7A1 AT turkos DOT aspodata DOT se> <20160106133049 DOT 5A0E9809D79B AT turkos DOT aspodata DOT se> <20160106143629 DOT 4D39D809D79B AT turkos DOT aspodata DOT se> <20160106164022 DOT D0D4E809D79B AT turkos DOT aspodata DOT se> <20160106180912 DOT 42ddf4079d91384f206b7c35 AT gmail DOT com> <20160106191433 DOT 5dc5cb59 AT jive DOT levalinux DOT org> <20160106202817 DOT 56197b2c539d426a1b724c9e AT gmail DOT com> <568E09ED DOT 1080508 AT m0n5t3r DOT info> <568E6354 DOT 80302 AT m0n5t3r DOT info> <20160108002640 DOT 03233b24 AT jive DOT levalinux DOT org> <20160108175259 DOT 127a3f073616758434f7edff AT gmail DOT com> <20160109020345 DOT 1e07cb84 AT jive> X-Mailer: Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id u09HVWqv018237 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 On Sat, 09 Jan 2016 10:14:06 +0100 geda AT psjt DOT org (Stephan Böttcher) wrote: > "Lev (leventelist AT gmail DOT com) [via geda-user AT delorie DOT com]" > writes: > > > On Fri, 8 Jan 2016 17:52:59 +0100 > > "Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via > > geda-user AT delorie DOT com]" wrote: > > > >> In preferences-->Layers-->Groups some of the layers are listed but > >> not all are listed. What do you think is missing? > > > > I would add explicitly the insulation layers, and documentation layers, silks, > > etc. I'd add user defined layers as well. I'd add some logic like "XOR this > > layer with that, and use it as conductive 2." > > I'd prefer the format/data model to become more general and orthogonal, > not more explicit layer types. All layers that need to be described > needs an explicit entry in the layerlist and can be drawn on. > > If you want to draw on an insulation layer, just add it. If you do not > want to draw on it, there is little reason to add it. It should not be > required to describe the board, unless the data model/format lacks other > attachment points for its dialectric properties attributes. > > NB: Since the primary target export is Gerber, I propose to implement > the level concept from that standard somehow. Each object shall be > explicitly assigned to a layer, and a level on the layer. Even levels > draw, odd levels clear. Standard library level assignment could be: > > level 10: polygons > level 25: holes in polygons > level 35: clearances around lines > level 40: lines. > level 50: pads > > A Line object would not need to include its clearance directly, but > there would be a second line on the clearance layer. But those two > objects must be linked to each other both in the file format and the > data model, so maybe that is not a good idea. > > OTOH, generic compond objects are require too, for Vias, Elements, and > hierarchy, why not for Lines and Arcs as well? > > In other words, please think more generic not more special case. The > GUI shall encapsulate all that with more specialized tools and > defaults. > > Line( (("attribute" value) ...) (("layer1" level1 width1) ("layer2" level2 width2) ...) ((x1 y1) (x2 y2) ...) ) > > -- > Stephan I agree. With a few drawing primitives, layers and suitable grouping it should be possible represent everything in pcb. As is now only a few pin/pad/via which cover almost all cases on an ordinary circuit board are possible but they have limitations. Nicklas Karlsson