Mail Archives: geda-user/2015/08/02/21:30:19
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
- Raw text -