Mail Archives: geda-user/2015/06/29/21:37:57
On Jun 29, 2015, at 7:05 PM, Evan Foss (evanfoss AT gmail DOT com) <geda-user AT delorie DOT com> wrote:
> Yes but that is not the format PCB accepts.
I’m unclear on what you want. PCB has its input format, which is not TSV. TSV is good for other uses, since a very wide variety of tools can read it.
>
> On Tue, Jun 30, 2015 at 12:52 AM, John Doty <jpd AT noqsi DOT com> wrote:
>>
>> On Jun 29, 2015, at 6:36 PM, Evan Foss (evanfoss AT gmail DOT com) <geda-user AT delorie DOT com> wrote:
>>
>>> I was thinking TSV for the other information (refdes to footprint or
>>> trace properties) but that is cool.
>>
>> The standard “bom" gnetlist back end can make a TSV with symbol attributes like footprint, value, etc. The gnetlist API does not have a way to access net attributes.
>>
>>>
>>> On Tue, Jun 30, 2015 at 12:28 AM, John Doty <jpd AT noqsi DOT com> wrote:
>>>>
>>>> On Jun 29, 2015, at 5:59 PM, Evan Foss (evanfoss AT gmail DOT com) <geda-user AT delorie DOT com> wrote:
>>>>
>>>>> It would be nice to change the way PCB takes data in. I like the
>>>>> netlist handling but something more CSV or tab delineated would be
>>>>> nice for the rest of the stuff.
>>>>>
>>>>
>>>> Nothing whatever to do with PCB, but I do sometimes find a TSV netlist useful. Here’s a gnetlist back end that makes a TSV:
>>>>
>>>>
>>>>
>>>>
>>>> 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/
>>>
>>>
>>
>> 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/
>
>
John Doty Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com
- Raw text -