www.delorie.com/archives/browse.cgi   search  
Mail Archives: geda-user/2015/09/11/13:50:05

X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-TCPREMOTEIP: 207.224.51.38
X-Authenticated-UID: jpd AT noqsi DOT com
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: [geda-user] About reinventing the wheel, and how to avoid it
From: John Doty <jpd AT noqsi DOT com>
In-Reply-To: <201509111707.t8BH7kS8004233@envy.delorie.com>
Date: Fri, 11 Sep 2015 11:49:37 -0600
Message-Id: <F1D09E6E-3D3C-4354-A712-DE464449B212@noqsi.com>
References: <alpine DOT DEB DOT 2 DOT 00 DOT 1509111150410 DOT 2482 AT lichen> <B94E2C24-8B63-46FC-A551-9E4B14B817C9 AT noqsi DOT com> <201509111624 DOT t8BGOPYV000685 AT envy DOT delorie DOT com> <20150911190224 DOT 5b50175919e00b91df2ccf53 AT gmail DOT com> <201509111707 DOT t8BH7kS8004233 AT envy DOT delorie DOT com>
To: geda-user AT delorie DOT com
X-Mailer: Apple Mail (2.1878.6)
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t8BHo2kj012603
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 Sep 11, 2015, at 11:07 AM, DJ Delorie <dj AT delorie DOT com> wrote:

> 
>> It could be a lot easier to add copper spacing rules in the
>> schematic. I guess attaching spacing attribute to nets possible
>> refering to a specific category for example "InverterOutputVoltage"
>> may solve it in the schematic but it must also be transferred to the
>> layout.
> 
> Sure, attaching text to objects is easy if the application doesn't
> need to understand the text.  gschem doesn't impose any copper spacing
> rules on schematics, so it doesn't care what text you add relating to
> copper spacing rules.  It's just text.
> 
> PCB has to enforce the rules, so it needs to both understand the
> desired rules and know how to impose them on the design.  That's a
> much harder task than just keeping track of some text.

We have DRC for geda-gaf appropriate for its function. Somewhat configurable for the application, and the user can use judgement as to what to pay attention to. Its model of what the user is doing is restricted, but since it doesn’t actually enforce anything that’s annoying but harmless. If anyone wants to fix the annoyances they can write a new script. This avoids the “one man’s bug is another’s feature” problem. But the user need not rewrite and maintain gnetlist, just one script, or perhaps part of one. Simply overriding some internal function with an add-on is sometimes sufficient when a “standard” gnetlist script needs a little help.

I found gnet-spice and gnet-spice-sdb inadequate for my purposes, so I wrote gnet-spice-noqsi. That limits nobody and does not interfere with any existing flow. I am interested in liberation, not control.

> 
> I'm not denigrating the usefulness of being able to put arbitrary text
> anywhere; we added that to pcb (somewhat) as well.  But don't think
> that being able to add a chunk of text is the same as doing something
> useful with that text.
> 

Having the text is a prerequisite. If you don’t have it, you can’t do anything with it. Liberty does not get jobs done, but it gets out of the way.

“100% of shots not taken don’t go in.” -Wayne Gretzky

John Doty              Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com



- Raw text -


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