X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f Date: Mon, 13 Jul 2015 13:25:30 -0400 Message-Id: <201507131725.t6DHPU2V010794@envy.delorie.com> From: DJ Delorie To: geda-user AT delorie DOT com In-reply-to: (message from John Doty on Mon, 13 Jul 2015 08:50:10 -0600) Subject: Re: [geda-user] gEDA/gschem still alive? References: <20150707060409 DOT GB14357 AT localhost DOT localdomain> <1436287952 DOT 678 DOT 26 DOT camel AT ssalewski DOT de> <559C0F7E DOT 7010009 AT neurotica DOT com> <1436295556 DOT 678 DOT 91 DOT camel AT ssalewski DOT de> <559C3778 DOT 4000105 AT neurotica DOT com> <20150708072021 DOT GB13243 AT visitor2 DOT iram DOT es> <20150713082342 DOT GB26809 AT visitor2 DOT iram DOT es> 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 > For things with a lot of pins, I usually just draw a box without > pins, run a bus to it, and make the pin connections from a table > with pins2gsch.awk. When I have to debug a faulty pcb, stuff like this would be useless. A schematic should be more than just "capture the netlist" - it should help the viewer understand the design and operation of the device. But I agree that there's a tradeoff that's sometimes best solved with a table instead of a diagram. I've suggested adding a "table" object to gschem, for things like power/gnd pins.