Mail Archives: geda-user/2016/01/26/16:04:13

X-Authentication-Warning: 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;; s=20120113;
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20130820;
X-Gm-Message-State: AG10YOS+HbHR2+/jI88z20h8Al7qxa6/5PiElDy3WTw1opZHiD79wJIgp7HvbaE9Dn8oabey/tOwF1kPLG6ciA==
MIME-Version: 1.0
X-Received: by with SMTP id 70mr25198473wmx.37.1453842235708; Tue,
26 Jan 2016 13:03:55 -0800 (PST)
In-Reply-To: <>
References: <alpine DOT DEB DOT 2 DOT 00 DOT 1601180756390 DOT 9035 AT igor2priv>
<alpine DOT DEB DOT 2 DOT 00 DOT 1601260416150 DOT 9035 AT igor2priv>
<56A751EC DOT 8030402 AT iae DOT nl>
<20160126124701 DOT 0d061912c7e078ced9d4e6cb AT gmail DOT com>
<CANEvwqgs3YFnt7m8mA1DN6X2KdWbyr4zpXCVH321vDo1f7CyxA AT mail DOT gmail DOT com>
<201601261804 DOT u0QI4KEQ009550 AT envy DOT delorie DOT com>
<E7D351BF-5BBB-41AC-B996-D5E27079A82C AT noqsi DOT com>
<CAC4O8c-ZyNnCzCDHXkYYabSD4fG8vf+CKmhMycNJujGMPKzQDQ AT mail DOT gmail DOT com>
<20160126214417 DOT 2310bcfe61c93ab80b4b8fe8 AT gmail DOT com>
Date: Tue, 26 Jan 2016 12:03:55 -0900
Message-ID: <>
Subject: Re: [geda-user] The nature of gEDA users
From: "Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: geda-user AT delorie DOT com
X-MIME-Autoconverted: from quoted-printable to 8bit by id u0QL40a9019922
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, Jan 26, 2016 at 11:44 AM, Nicklas Karlsson
(nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]
<geda-user AT delorie DOT com> wrote:
>> > But gschem can do schematic capture for ASIC even though that’s not its target. The difference is that gschem doesn’t limit what you can draw. It’s quirky and limits *how* you can express what you need, but I’ve never found it incapable of expressing a circuit. It gives you a few crude primitives and a few ways to compose more complex objects from simple objects. A few layers of that, and you have a 6000 component mixed-signal ASIC.
>> >
>> > Pcb says to the user “my way or the highway”. Gschem says “live with my quirks, and I’ll help you do anything”.
>> Not true, I've just gone through the entire format carefully and pcb
>> actually has very little per-part or per-feature overhead.  It's about
>> as close to a paint program as it can be.  It can do lots of stuff,
>> though admittedly often in quirky ways, just like gschem.  Your major
>> gripe seems to be that you can't "draw" 3D or inter-layer features,
>> because their implementation is bolted onto the fundamentally layer
>> oriented design in a hard-wired way.  It's a true complaint but not
>> very useful, because adding 3D CAD would require a total rewrite with
>> buckets of additional complexity.
>> It's completely possible to go on adding features like blind vias
>> without a total rewrite.
>> Britton
> Did you look at element/footprint file format also? Is it possible to have vias in a footprint? Put the drawing primitives in a footprint at copper or solder mask layer?

Not possible, and I don't think it would be the way to go.  I'd rather
see pcb get better hierarchy support and make this sort of thing the
responsibility of that system.  I do stuff sort of like this now, I
have reusable layouts for common subsystems, and scripts that manage
the names of parts inside them.


- Raw text -

  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019