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=pkutrogY6ui34pBUTCGBlX3H5wTYlhGrnXtITPFVono=;
        b=ctFZf4pMiFlPYqGanXHFmwTXkQfoJgG/GXsUEYtycYECIvLkTpxe99SMm+f/UWZXNU
         r4ZBWsUr8M8zGNKv9VgfL3tvhMxGawdqhV3OpxcSk8sQazSibMpuY3G9HYVqpSK7aZs7
         NuOvSkh96zRG9sDZKYOgsA3ZPlKZE3xmnU3YOCocSCI39Yp7EkHjaq4GxbDQdQQQ6tQ9
         ZUdawDHnugsEmPuLuU/4cXozmIfaKxM+cicIqLfF9XxNPRtvSzqPyOE4pXkwC2/WEdxG
         FQgOlPX5bDam5hxAbOmcQQBgoHz86QCJth7LPW0c4yUlACK8Ak50q4Hh4x9kznI3YePt
         V9yg==
MIME-Version: 1.0
X-Received: by 10.152.120.164 with SMTP id ld4mr5277111lab.84.1442092080649;
 Sat, 12 Sep 2015 14:08:00 -0700 (PDT)
In-Reply-To: <9C33EEB9-0F4C-426E-86D6-AB42B1FB2842@noqsi.com>
References: <20150912002643 DOT d476ca384a4a11ddda3b3a52 AT gmail DOT com>
	<CAM2RGhQ0QT7JWHu4FY0+uTBdkDBKyK5fHprUO17NNao_BP4E7Q AT mail DOT gmail DOT com>
	<20150912190130 DOT 8e2dbad9f49bd700b19ef422 AT gmail DOT com>
	<CAM2RGhQbW5+EkKDGhBdH6Xv1p7sFC9YgHzdO8niLHnJacSv7bg AT mail DOT gmail DOT com>
	<9C33EEB9-0F4C-426E-86D6-AB42B1FB2842 AT noqsi DOT com>
Date: Sat, 12 Sep 2015 21:08:00 +0000
Message-ID: <CAM2RGhSZa=NjXcQG-N+Kj-rm_jc4SoYVQGCjOVTk4CG_v9g+1A@mail.gmail.com>
Subject: Re: [geda-user] Netnames on all connected segments
From: "Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie 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 t8CL86nQ015971
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, Sep 12, 2015 at 8:27 PM, John Doty <jpd AT noqsi DOT com> wrote:
>
> On Sep 12, 2015, at 2:07 PM, Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
>
>> On Sat, Sep 12, 2015 at 5:01 PM, Nicklas Karlsson
>> (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]
>> <geda-user AT delorie DOT com> wrote:
>>>>> Would it be hard ta add the netname all connected segments then it is added or changed?
>>>>
>>>> I would have issues with this. One of the features I wanted to add to
>>>> gnetlist was the ability to output specific properties for parts of
>>>> nets.
>>>> (ex. trace width for PCB.)
>>>
>>> I also want. As is now connections are stored as lines and an attribute could be added to one of the lines, I guess it would be possible to achieve this with current file format although there may be a need split lines in two sometimes to form segments.
>>>
>>> What would be needed in gschem would a function to select all line segments belonging to a net and a function selecting all lines belonging to a segment which possibly also sometimes have to split a line in the middle to form a segment. Then an attribute is added or changed it will be attached to only one off the lines and then I guess it will work with gnetlist.
>>
>> Igor2 and I have been fixated on the idea of placing additional
>> attributes on parts of nets so that you can have things like trace
>> width passed to PCB. I am looking at having gnetlist understand when
>> someone wants a star ground by looking at how nets are angled when
>> they meet.
>>
>> There is the question of how much of gnetlist should be moved into
>> libgeda
>
> None. Scheme scripting is flexible, libgeda is rigid. Moving things into libgeda is the wrong direction.

1. People fought me when I wanted a second plugin interface in
parallel to scheme.
2. People want back annotation and that requires gschem being able to
import some net related info. How would you do it? If gschem not going
to import back annotation info in the form of a netlist what is the
logical input for it?
3. I have been a lot more open to your ideas than a *lot* of other
people on this list. Simply stamping "wrong direction" on someone
elses idea is pretty closed minded. You give no technical reasons and
no alternative solution.

>> since I don't want to do this in scheme.
>
> Then do it in xorn-netlist. Options are a wonderful thing to have. I’d be happy to help you with doing it in Scheme, but the gnetlist API cannot access connection details at segment level.

Yes and I can add to the gnetlist API with out breaking things.

> 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/