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=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=KeDb62ZErdCtxIlDR6Vv29Sw58efkjCbuNRfCLmc250=; b=KDIZ/vBdsA91EkGHnxPSuVNmQLYhOBTw48TJoggUwhUYwVW6srjidMKHG5Ww9+7v3r hpUV7cuuqhWa1II/gEW0E3Z2kwutpDgvxhIyYurHu4jrLpMdqN5s+CqSHjlhe913mX8x Lz47XDqKgdNoAMA4h8ldZvb9hPWkeE+bjpf2Qbm9nv6yoyNCOXojhSDjSfP4iZp9FnjL 0LibriJuu8Ur2eeiKJjiufidvzB1qQGxJy5VBXXEoxOsJ344y53fMFxgVYWvpoVvCEpn dNgQYs2CnbuUi1ZXitP9nWJ9MFtFXlpIlmpi7/4TG+Kiyb4MbmpgBT8/ofqAlNQ6B0dN qasQ== MIME-Version: 1.0 X-Received: by 10.112.124.164 with SMTP id mj4mr16595996lbb.3.1435621804583; Mon, 29 Jun 2015 16:50:04 -0700 (PDT) In-Reply-To: References: <20150629113018 DOT GH19654 AT fi DOT muni DOT cz> <1435581145 DOT 1447 DOT 19 DOT camel AT ssalewski DOT de> <1435592698 DOT 1607 DOT 17 DOT camel AT ssalewski DOT de> <1435599996 DOT 2704 DOT 20 DOT camel AT ssalewski DOT de> <201506292033 DOT t5TKXq06009463 AT envy DOT delorie DOT com> <13D3A00C-EA98-458A-BC3F-213653FA806A AT noqsi DOT com> <20150629212401 DOT GD28458 AT localhost DOT localdomain> <175C24CA-D7F9-4DD0-BC8C-09A2784BA6C1 AT noqsi DOT com> Date: Mon, 29 Jun 2015 23:50:04 +0000 Message-ID: Subject: Re: [geda-user] gEDA/gschem still alive? From: "Evan Foss (evanfoss AT gmail DOT com)" To: geda-user AT delorie DOT com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t5TNo9wq001093 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 John Doty : That said I would rather specify trace properties than component distances. One of them is more explicit than the other. If anything for thermal reasons the ability to specify distances as a minimum between components would actually make more sense. On Mon, Jun 29, 2015 at 11:47 PM, Evan Foss wrote: > John Doty : I agree with you. If I do anything it would just be adding > extra attributes to gschem and then making another tool to collect > them. Something to work in parallel to the netlisters. > > In the meantime don't worry I am too busy chasing down BSDL file stuff. > > On Mon, Jun 29, 2015 at 9:47 PM, John Doty wrote: >> >> On Jun 29, 2015, at 3:24 PM, Vladimir Zhbanov (vzhbanov AT gmail DOT com) wrote: >> >>> On Mon, Jun 29, 2015 at 02:54:33PM -0600, John Doty wrote: >>>> >>>> On Jun 29, 2015, at 2:33 PM, DJ Delorie wrote: >>>> >>>>> >>>>>> John, I have frequently marked off in the comment field how long/wide >>>>>> traces can/should be. It would be nice if there was some meaningful >>>>>> way to pass that to PCB. That would involve gschem changes in minor >>>>>> ways. I am not asking anyone to implement this. Just defending a >>>>>> position. >>>>> >>>>> File->Import imports all attributes as element attributes. I don't >>>>> know of anything that *does* anything with it though, aside from some >>>>> BOM scripts. >>>>> >>>> >>>> Yeah, but the problem is that it can’t import attributes of net >>>> segments, since they aren’t in one of the gnetlist views. Gnetlist >>>> can’t even see the segments, only the glommed-together nets. And then, >>>> nets aren’t “elements”. >>> It obviously can do it, since libgeda API has means for it. Once again, >>> see my scheme script above in the thread. >>> >> >> That’s using the gschem API, not the gnetlist API. >> >> John Doty Noqsi Aerospace, Ltd. >> http://www.noqsi.com/ >> jpd AT noqsi DOT com >> >> >> > > > > -- > Home > http://evanfoss.googlepages.com/ > Work > http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/ -- Home http://evanfoss.googlepages.com/ Work http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/