X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-TCPREMOTEIP: 64.88.227.134
X-Authenticated-UID: jpd AT noqsi DOT com
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: [geda-user] Hierarchy
From: John Doty <jpd AT noqsi DOT com>
In-Reply-To: <54DA3AA5.9060902@ecosensory.com>
Date: Tue, 10 Feb 2015 13:23:39 -0700
Message-Id: <20629907-423A-47EE-8229-37DAFD780875@noqsi.com>
References: <CAOFvGD7pJTo8A=MXVbuuXO=++0vGukUyqVfckVtnCi99ziqWJQ AT mail DOT gmail DOT com>	<3709636 DOT NVszrDDjOR AT jasum>	<20150208135925 DOT 6f6ddab6 AT Parasomnia DOT thuis DOT lan>	<1897145 DOT BbSdS1MRWc AT jasum>	<EE929E31-B2C7-48BF-BA49-B2E728DB99C3 AT noqsi DOT com>	<66DD3BF9-092C-4EFF-B12D-6214141C152D AT icloud DOT com>	<52E0C8E3-2FD3-4D79-A01D-962E7EFA6D4F AT noqsi DOT com>	<C26D592D-04B1-4AB0-9F32-6D5A537EBAF4 AT icloud DOT com>	<638942CE-E278-40ED-8C36-6A89C33FD158 AT noqsi DOT com> <CAGde_xM8Gfs-xAQad33h2d9aTTWV7e4Cyegw6A-Wbs+phP5scQ AT mail DOT gmail DOT com> <54D7CC55 DOT 1090602 AT ecosensory DOT com> <F442D696-BDB0-453E-8162-2034B37C3391 AT noqsi DOT com> <54D8D57C DOT 6010901 AT ecosensory DOT com> <9F1DFB84-F10E-4834-A68C-44529867358B AT noqsi DOT com> <54DA3AA5 DOT 9060902 AT ecosensory DOT com>
To: geda-user AT delorie DOT com
X-Mailer: Apple Mail (2.1878.6)
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t1AKNvBl009258
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 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