X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.98.4 at av01.lsn.net
Message-ID: <54DD6DD0.4000201@ecosensory.com>
Date: Thu, 12 Feb 2015 21:21:52 -0600
From: John Griessen <john AT ecosensory DOT com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.4.0
MIME-Version: 1.0
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] gschem refactoring ideas -- overall architecture
 document.
References: <54DBDFF1 DOT 1010409 AT ecosensory DOT com> <20150212234011 DOT 224e2d30 AT jive> <CAM2RGhS48RcUjZN8XB_fn5sMdkqu7Ha_mmf_zF30N3bvEy9ysg AT mail DOT gmail DOT com> <51B5EF74-76A1-4F0C-A0FA-332F7B945A08 AT noqsi DOT com>
In-Reply-To: <51B5EF74-76A1-4F0C-A0FA-332F7B945A08@noqsi.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: geda-user AT delorie DOT com

On 02/12/2015 07:54 PM, John Doty wrote:
> Needs groups. The Clock Drivers are each a set of subsymbols. Needs better layering to get the stacking and connections right. Needs busses with actual semantics.
>
> I think the file format as it is today is almost capable of describing this. The barrier I see is the clumsiness of having libgeda in C support scripting in Guile.

Those stacked clock drivers are instances and you merge their busses.  That's the essential info I was saying we need
for what I'd call "decent hierarchy".  We agree at a high enough abstraction level.

John Griessen