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=6LTwdzlAklJ8CuIe3KD4XCeMCDrTvwNe3BGg0gzE3T8=;
	b=aVXkF2LakBSNsbhJeya64/w/TpVT8xxlRhZLK3xv/ONGDq55Hjj5itbTMGzFv2WdFw
	6AUb/ZnJPkWqOu/JWRZ+kZCcEocNCpYBltQHYyNpqTxUC5aRhhE13YzVLMETn5fDM28w
	9v+tSXh2kjVhPJdeDqP9ehnR1oEY7a0vPo/vG37osB0oH7N2Ugs8UwZvTx6MoPtGpZ2A
	MommOap5Py61uzxVtuM6TJeWdaN1hu3UyoS9cOsZ8sf4f0KA6gP08UYqRnivurNydWXW
	82gCtkZP2E6Oo7GaQK3pJXSXjsw0rcQDm8MZjsI9M5rXeVfzpoVb3+sANbniseOMrTx1
	K2PA==
MIME-Version:	1.0
X-Received:	by 10.112.198.198 with SMTP id je6mr6035193lbc.31.1442102691170;
	Sat, 12 Sep 2015 17:04:51 -0700 (PDT)
In-Reply-To:	<6BCF1504-7F5A-48FF-9C2B-C67645C93609@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>
	<CAM2RGhSZa=NjXcQG-N+Kj-rm_jc4SoYVQGCjOVTk4CG_v9g+1A AT mail DOT gmail DOT com>
	<6BCF1504-7F5A-48FF-9C2B-C67645C93609 AT noqsi DOT com>
Date:	Sun, 13 Sep 2015 00:04:51 +0000
Message-ID:	<CAM2RGhRgHvtRSdZf8gcB677vRcEgxR4nACxQdfFwO+f1_ydc9g@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
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id t8D04uQ5005174
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 Sat, Sep 12, 2015 at 9:33 PM, John Doty <jpd AT noqsi DOT com> wrote:
>
> On Sep 12, 2015, at 3:08 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 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.
>
> Not me. But I don’t think you realize how hard it is.

Oh I do and I even started it. Then it came up in conversation on the
list and I got push back from people who have commit privileges to the
mainline and I gave up.

>> 2. People want back annotation and that requires gschem being able to
>> import some net related info.
>
> Nope. It requires a tool that can annotate a schematic. Gschem, as an interactive editor, is not that tool. https://github.com/xcthulhu/lambda-geda is such a tool, and I have used it, but scripting in Haskell is probably not to your liking.

You are right about Haskell.

>> 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?
>
> *Back* annotation is to me a bad idea in general. Annotation is good. If you want back annotation, simply copy the result of annotation to your source schematics.

Please hold your opinions until you see how it works.

>> 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.
>
> If you want to do that, I’ll support it as a Scheme programmer, as I supported the refactoring that enabled the attribute censorship bug fix. But I thought you didn’t want a Scheme solution. Xorn might very well be what you want.

If you are willing to do the scheme coding then I will do it that way.
I would almost always compromise and work with people than go it
alone. Igor2 has already expressed interest in doing the pcb side (in
his fork) which someone else can carry over to the mainline.

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

- Raw text -