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] The new to do From: John Doty In-Reply-To: <201507160024.t6G0OZrG013557@envy.delorie.com> Date: Wed, 15 Jul 2015 19:31:44 -0600 Message-Id: References: <55A2A0A2 DOT 4080403 AT ecosensory DOT com> <7AE39440-DA68-4491-A965-C1B97D1D86C1 AT sbcglobal DOT net> <20150712213152 DOT 7968b74c AT jive DOT levalinux DOT org> <304D9D86-3CF6-4D61-A5CA-6CE414EA0661 AT sbcglobal DOT net> <20150712224637 DOT 2d4cc2de AT wind DOT levalinux DOT org> <55A2E9B7 DOT 9040502 AT neurotica DOT com> <20150713131707 DOT GA782 AT recycle DOT lbl DOT gov> <55A4042E DOT 5060402 AT neurotica DOT com> <55A41B30 DOT 50602 AT neurotica DOT com> <254F9AFE-1A3E-4D88-BABF-E6E0F87A56B1 AT icloud DOT com> <1436960577 DOT 1072 DOT 6 DOT camel AT ssalewski DOT de> <201507151820 DOT t6FIKYME001704 AT envy DOT delorie DOT com> <201507152007 DOT t6FK7lv8005229 AT envy DOT del! orie.com> <24AD56C6-B7C2-4D7E-B69A-F68DBACCBFDC AT noqsi DOT com> <201507152051 DOT t6FKp8ip006830 AT envy DOT delorie DOT com> <201507160024 DOT t6G0OZrG013557 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 t6G1Vsc3017261 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 15, 2015, at 6:24 PM, DJ Delorie wrote: > >> I don't want to enter a world where the workflow is a direct flow >> from gschem to pcb. That would be very inflexible. I also don't see >> how it would really be saving anytime in coding. > > That is not the case, has never been the case, and nobody is > suggesting that it be the case. PCB goes through the netlister like > everyone else, and none of the options we've discussed prevent you > from doing things a different way if you want. > > If it *really* bothers you, it's all open source - make a copy for > yourself and don't update, and you don't have to worry about anything > changing any more. How can you do collaborative work that way? I reject the idea that gEDA is only for hermits. > > What we *would* like to do is expand the tools to allow a wider range > of things to be possible, without stopping the old things from working How do you keep the documentation and menus simple? Every unnecessary feature makes it harder for the user to discover and employ the necessary ones (been there with Viewlogic). How do you avoid interaction between features? Integration is the enemy here, but the toolkit approach is a great way to encourage factoring. > or being needlessly complex. The opposition to *any* change has made > this more difficult than it should be. No, it *should* be difficult. Geda-gaf is a mature, stable, useful toolkit. Ill-considered change is bad. Adding features to software is like adding mass to aircraft: not always bad, but there’d better be very strong justification. > > PCB's importer is an example of that. We improved the existing tools > to implement a significant convenience feature, and made it easy for > the user to use. This doesn't prevent you from using the old gsc2pcb > if you want. > But that itself reflects pcb’s inflexibility. If you could import netlists from 20 other tools, you’d want those interfaces factored out, I think. I certainly would. John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ jpd AT noqsi DOT com