Mail Archives: geda-user/2015/02/10/15:25:48
On Feb 10, 2015, at 10:06 AM, John Griessen <john AT ecosensory DOT com> wrote:
> On 02/09/2015 11:35 AM, John Doty wrote:
>>> If we had a document for what the
>>> >overall structure of gschem was,
>> Hierarchy in gschem is documented. Seehttp://wiki.geda-project.org/geda:gschem_ug:hierarchy.
>>
>>> >and how the desired new features of hierarchy where we can have schematics in schematics,
>> None required in gschem.
>
> But then you go on describing all kinds of changes you'd like…
Not in gschem, at least for my purposes. However, I am sympathetic to the idea that a next generation gschem/gnetlist should use a more mainstream, familiar scripting language. Not Scheme, and not Lua either. Python, a language I rarely use (but *can* use), seems the best choice to me.
Not in the .sch file format, which seems sufficiently flexible, and is easy to parse in most languages without having to go through an FFI to a complex parser.
Gnetlist is very good, too, but occasionally I want more views into the collected data from the Scheme level. In the case of hierarchy, gnetlist is good for a single module at a time, but figuring out which modules go into a design and assembling them into a hierarchical netlist requires external input and scripting. It’s a bit inconvenient and error prone.
I don’t ask for any changes to pcb, either. I think it both unusable and unrepairable. But others like it.
John Doty Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com
- Raw text -