X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=D6SxUX0GYFMCqvn12IiK4qQaKoqvlANHHPQEgbyHPdw=; b=Fpg3MNdlpvV5mhOsTV/ljYIFpq+ZrhYMm4aGcqLLiMsJsGNqG9Rhbkwq8ZbXPDeNAE ujwFslEWx1UdFeeEykylEbEElZkvQaoB2tw2Czd0Kvug5vH1vc0bzLUVJTg+iN+sAp8M qiVr1Oz4wGEaVXHoWMfGAQTxPMO2Q7l3292smrpwgyD4DzD9k8O/6lZjH+e1hI2n/zoc ohZx0kIbnNzFzhqwA5x4+rMkXFu/GXwNzPvUCE29bFfKSStlNmCmRN4YHPa7shRmBFs/ c4UPQHrfcOzOTd3UVupFSxrVoZ3eGhp0aCeEyIA4/fn7OmbOy6CwGdb50jE2ZvfIrgfj BMmQ== MIME-Version: 1.0 X-Received: by 10.152.203.162 with SMTP id kr2mr15617878lac.57.1436457628362; Thu, 09 Jul 2015 09:00:28 -0700 (PDT) In-Reply-To: <559E9616.1020706@neurotica.com> References: <44FED82A-8277-427B-87A8-FBC5E9A3D0E5 AT noqsi DOT com> <11988591-8CA7-4132-B14A-21A53895E63E AT noqsi DOT com> <559E8975 DOT 9050805 AT neurotica DOT com> <559E9616 DOT 1020706 AT neurotica DOT com> Date: Thu, 9 Jul 2015 12:00:28 -0400 Message-ID: Subject: Re: [geda-user] Back annotation From: "Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t69G0W7L032239 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 Thu, Jul 9, 2015 at 11:41 AM, Dave McGuire (mcguire AT neurotica DOT com) [via geda-user AT delorie DOT com] wrote: > On 07/09/2015 11:26 AM, Evan Foss (evanfoss AT gmail DOT com) [via > geda-user AT delorie DOT com] wrote: >>>>>> If you’re just making changes until a diff shows nothing, it doesn’t matter whether you make them upstream or downstream. Just quit when you have a match! >>>>> >>>>> This sounds reasonable to me. So the common denominator is to load a "target netlist" into gschem and show the differences between the current state and the target state, either by highlighting them in the schematic or by showing a diff? This shouldn't be too difficult to implement. >>>> >>>> Not into gschem. Keep gschem clean, please. I just displayed a diff in a terminal window. >>> >>> Why are you assuming that adding this (or anything else!) will >>> automatically make gschem "dirty"? >> >> It would be dirty. It breaks the unix mentality by integrating too >> much stuff into one program and violates the otherwise clean symmetry >> we are going for in workflow. >> >> Forward the flow is >> gschem -> sch file -> gnetlist -> netlist file -> pcb >> gschem -> sch file -> gsch2pcb -> pcb file -> pcb >> >> the reverse should be something like >> pcb -> pcb file -> pcb2netlist -> netlist file -> netlist2gsch -> sch >> file -> gschem >> pcb -> pcb file -> pcb2sch -> sch file -> gschem >> >> See how each tool only does on step. That is one of the principles >> that make gEDA great. Integrating more stuff into one program is more >> like what kicad would do. > > Yes I'm quite familiar with (and applaud) the UNIX many-small-tools > philosophy. Making these sorts of connections between these "small" > (using the world loosely) programs in real time, at runtime, rather than > connected by files and doing them separately, does not violate this > philosophy. If it did, UNIX would not have pipes. Well the bit I was omitting is it takes shared libraries and makefiles. > -Dave > > -- > Dave McGuire, AK4HZ > New Kensington, PA > -- Home http://evanfoss.googlepages.com/ Work http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/