X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-TCPREMOTEIP: 63.119.35.194
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] Improved Find
From: John Doty <jpd AT noqsi DOT com>
In-Reply-To: <55BEBC22.1030004@ecosensory.com>
Date: Sun, 2 Aug 2015 21:29:44 -0400
Message-Id: <B224D264-8CD5-473C-B7EF-383A40017E53@noqsi.com>
References: <FF2A0FBC-75B1-4A3E-9588-CD3DB7CC448A AT sbcglobal DOT net> <5329D15C-0713-4919-8205-AC474BAC5652 AT noqsi DOT com> <CAC4O8c_bRzahs66fCYsuNggvuwy0-JxGbTu8EJsGwaeSVB8G-Q AT mail DOT gmail DOT com> <FFA87469-7432-49C7-8AF5-153C41DFE78F AT sbcglobal DOT net> <CAC4O8c9241Z8A6-kKTQM6f=CTxtTU_-Dmj9uMOqqmp68_OuZxg AT mail DOT gmail DOT com> <BC57B367-8548-4947-B29C-A69378423BA8 AT noqsi DOT com> <631C0577-E61D-40BC-B200-96BA897092E6 AT sbcglobal DOT net> <DAC3E2ED-AB1E-42C7-AA0B-78853F31A95A AT noqsi DOT com> <55BEBC22 DOT 1030004 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 t731Ts2n016095
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 Aug 2, 2015, at 8:56 PM, John Griessen <john AT ecosensory DOT com> wrote:
> 
> On 08/02/2015 01:52 PM, John Doty wrote:> Two source attribs in the symbol. Like slotdef, you can have as many source attribs as you need in a symbol. This could be considered a design defect: how do you promote and override this sort of attrib? Maybe these should be multi-line instead.
> 
> This kind of thing really strongly impacts/possibly-destroys hierarchic schematic usefulness.

I don’t see why. What if you need eight pages to express what a subschematic does?

> 
> I don't have any mathematical proofs, but my gut says, "keep a module definition same-as-chip-design-methods,
> as a single ins/outs list associated with a graphic symbol or code chunk, and with a mechanism to convert between
> 'code chunk for the module container' and graphic-symbol at will by an easy to launch program.”
> 

An example from my chip designs is an amplifier that comes in two forms: a fixed-gain form and a form with digital gain adjustment. These have different symbols, but share a common page, the core amplifier circuit. Gain adjustment works by strategically switching capacitors in parallel with capacitors in the core, so I judged that making the core its own module would require wrapping a rather difficult to comprehend symbol around it. In any case, reviewers have  been able to figure out what’s going on without difficulty, and they are, of course the primary audience for the schematics.

John Doty              Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com