X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com 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; bh=Al/7SeIJhvwyebCQSgAguiNJUlfREJegKIelMf9RgNM=; b=C6kX8Mjl4R/bzpz27aI4FoO/ynL9oDCk6Z5ErJc60uv8LIg9xYNZVPNOLJvNfxFIh1 EPGCfkSjRrk0igq2TcbN5HnEoKvqxMEgpn17Xig9BFr+QoMN32DLgNjzL1p2g4BtwaJq k4LA5ekQ5IGQVStXCmRPOxng1zQWHNx3LrQEHBfoFMD9vEeCIsYohyzuBRygTlusnc0i aIdTUn1BfPlmrDgfH5xM7qopvgNvOs+03muuU3xs5RNfdcYfC/Ts6wjoUQhX9FytITCa R6MImh4w+P4hBSg1cVR6f2Z+YPIIniDIYdX0Nh7MK4A/UaCTCiSIso3+UpS5twX5a2pr G8CQ== MIME-Version: 1.0 In-Reply-To: <22F588A0-0729-4600-9B8C-34F213CCA92B@noqsi.com> References: <4F9D5D77 DOT 4080308 AT ecosensory DOT com> <15A5FC7D-2FDA-4EBD-A4C5-AA8C908B41E9 AT noqsi DOT com> <4F9D8849 DOT 4020508 AT ecosensory DOT com> <22F588A0-0729-4600-9B8C-34F213CCA92B AT noqsi DOT com> Date: Mon, 30 Apr 2012 07:26:25 -0700 Message-ID: Subject: Re: [geda-user] Down schematic hierarchy question From: Ouabache Designworks To: geda-user AT delorie DOT com Content-Type: multipart/alternative; boundary=bcaec5299a7540f6b804bee63de6 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 --bcaec5299a7540f6b804bee63de6 Content-Type: text/plain; charset=ISO-8859-1 On Sun, Apr 29, 2012 at 4:13 PM, John Doty wrote: > > On Apr 29, 2012, at 12:28 PM, John Griessen wrote: > > > On 04/29/2012 12:06 PM, John Doty wrote: > >> Gschem is fully hierarchical > > > > > > How do you define that? > > > > It edits schematics in explicitly hierarchical form. When you edit a > subschematic, you are editing the common subschematic behind all instances, > not an instance from a flattened set of schematics. That is sane behavior > for a hierarchical schematic editor. > > John Doty Noqsi Aerospace, Ltd. > http://www.noqsi.com/ > jpd AT noqsi DOT com > > > That is one sane behavior but not the only one. There are times when your entire design is configured by attributes passed down from 5 levels above that all you want to do is push down a level and see exactly what all that setup has done to the lowest values. It appears that gschem was never meant to elaborate a design and can only operate on the pre-uniqified sources. I am using gEDA to create design documentation from ip-xact files and it looks like I will need to perform the elaboration and convert that output into schematic form. Thanks all, John Eaton --bcaec5299a7540f6b804bee63de6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Sun, Apr 29, 2012 at 4:13 PM, John Do= ty <jpd AT noqsi DOT com> wrote:

On Apr 29, 2012, at 12:28 PM, John Griessen wrote:

> On 04/29/2012 12:06 PM, John Doty wrote:
>> Gschem is fully hierarchical
>
>
> How do you define that?
>

It edits schematics in explicitly hierarchical form. When you e= dit a subschematic, you are editing the common subschematic behind all inst= ances, not an instance from a flattened set of schematics. That is sane beh= avior for a hierarchical schematic editor.

John Doty =A0 =A0 =A0 =A0 =A0 =A0 =A0Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com



That is one sane behavior but not the on= ly one. There are times when your entire design is configured by attributes= passed down from 5 levels above that all you want to do is push down a lev= el and see exactly what all that setup has done to the lowest values.

It appears that gschem was never meant to elaborate a design and can on= ly operate on the pre-uniqified sources.=A0 I am using gEDA to create desig= n documentation from=A0 ip-xact files and it looks like I will need to perf= orm the elaboration and convert that output into schematic form.


Thanks all,


John Eaton


--bcaec5299a7540f6b804bee63de6--