www.delorie.com/archives/browse.cgi | search |
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=qGgtFoL6Or7SGXcU70XE/6/+lmzCvgZOKoWCgWBGjXM=; | |
b=Tdvz4190I4uOz98gnBWkdKZyakcRIKWiEqA36SzJvMtTZjiz0tN/ZgJLNB7FHxeNjg | |
Eakwj3c6LyyZzdOGjK5fcw2Tn3VpWLpt5KGVBjZRL+np32YHtHWFxE0EVnabAMovDX1w | |
xQQGd6yug6my3pG/rReaCLAp3nIf5kJPXS5AvUCbQGq6wLhBb1vwEe1dxsdfGZxGSM+o | |
9ZGLq/Xs2RUrgO8Mq/nPru8jRIVtx2/4hSzd1fBo+CRThc5Qwa2Y3G/r5CS0ezhBeF9H | |
Ym0LcuECErEkiXHb3yFB1vEQjuJjUSedIvqZ/lbC79xRY/T0loglH1VQcABgEZM9F9UM | |
3G/Q== | |
X-Received: | by 10.180.92.225 with SMTP id cp1mr6436667wib.2.1441990949059; |
Fri, 11 Sep 2015 10:02:29 -0700 (PDT) | |
Date: | Fri, 11 Sep 2015 19:02:24 +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] About reinventing the wheel, and how to avoid it |
Message-Id: | <20150911190224.5b50175919e00b91df2ccf53@gmail.com> |
In-Reply-To: | <201509111624.t8BGOPYV000685@envy.delorie.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> | |
X-Mailer: | Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu) |
Mime-Version: | 1.0 |
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 |
> > Where geda-gaf describes topology in a general way that has few > > restrictions, > > I.e. schematics don't have to worry about copper spacing rules, so > doesn't bother with rules. 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.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |