X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-TCPREMOTEIP: 207.224.51.38 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] gEDA/gschem still alive? From: John Doty In-Reply-To: <201507140314.t6E3EWAM031358@envy.delorie.com> Date: Mon, 13 Jul 2015 21:54:07 -0600 Message-Id: <57DE6891-3080-4C78-86A5-C3524164398D@noqsi.com> 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> <201507131725 DOT t6DHPU2V010794 AT envy DOT delorie DOT com> <201507140209 DOT t6E29V39029166 AT envy DOT delorie DOT com> <6C481B59-D7CC-43E5-B761-AD4C5A29F4A8 AT noqsi DOT com> <201507140314 DOT t6E3EWAM031358 AT envy DOT delorie 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 t6E3sFhb026314 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 Jul 13, 2015, at 9:14 PM, DJ Delorie wrote: > >> If the wad of lines is too dense to follow without confusion, what >> good is it? > > If the wad of lines is too dense to follow, you've failed as a > designer. Yes. But how do you avoid that when you have 16 channels of data converging on a connector? > I've seen the dense wad of lines. I've seen engineers dump > a design and start from scratch because it was "just a wad of dense > lines" and come up with something much more understandable but just as > complex. > >>> Because not everyone wants to do things your way. >> >> You're pushing graphics, but then you want tables in gschem, a >> graphics tool. Make up your mind. > > You're playing with semantics to argue your point. I've made up my > mind - I want small tables of related information on the same page as > the symbolic information, just like others might want text blocks, > images, simulation outputs, test data, pin numbers, or other relevant > information. You want an integrated tool, not a toolkit. You’ve come to the wrong place. There are 100 tools that you can use to make tables. Gschem is not one if them. This is a very good thing. > > It's not about graphics vs text. It's about putting related useful > information in a form that conveys design intent. > There are tools that are good at this, e.g. LaTeX. Use them. I have lately had a number of people reviewing my schematic designs. I also have several testing them. The latest review committee praised my LaTeX documentation. Nobody has complained about the tables. The common complaint is that hierarchical schematics are hard to understand. But when I ask them if 80 pages of flat schematics for one board would be better, the answer is always “no”. John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ jpd AT noqsi DOT com