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=sokRFyZdfp0n0o5Zj1XIJxlUNf368BHORhu276Udbvc=; b=qgO/FFHb3uqOWCnqSbhqCbE6yC9DORzAw/l5MmzdxxkpnQ9b9gKhjQzgzSSD1k3E3a RVDkWQ5ikDZPSeTTaNY49FwBFH5HHtjI0fJag95wCP9f7NHAP263wr+wjWvQgErnBLro N2LycriWkvtX0MW7LZXZKIDbYYgm8AIvqhBaZuYwJU21GpPnB52qSIracGiqCF3y3v94 Wb8d/ONIM7j5ONJZmGPDJoKh3Y7XD1MN3/Y+dMoUBfBG0AiiKG9kiKtTWaba13IuZxIr 3i56kDVF104jtkSoWSENeX0uPhE9cl7oRguBb6/NL6D9esQNmsqvu7vX6OrQtNW/cjJW +p8w== MIME-Version: 1.0 X-Received: by 10.180.82.199 with SMTP id k7mr63690496wiy.54.1436461231612; Thu, 09 Jul 2015 10:00:31 -0700 (PDT) In-Reply-To: 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> Date: Thu, 9 Jul 2015 09:00:31 -0800 Message-ID: Subject: Re: [geda-user] Back annotation From: "Britton Kerin (britton DOT kerin 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 t69H0dn1005361 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 7:26 AM, Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com] wrote: > On Thu, Jul 9, 2015 at 10:47 AM, Dave McGuire (mcguire AT neurotica DOT com) > [via geda-user AT delorie DOT com] wrote: >> On 07/09/2015 10:25 AM, John Doty 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 PCB nowadays does this in one step via Import Schematics. It can be set up to run your old gsh2pcb Make code automagically if you want. And there is absolutely no contest between this and the old "run gsh2pcb, restart PCB, re-import the netlist, and re-run the command file" approach that was enough to make you hate changes as simple as one refdes or pad shape. > the reverse should be something like > pcb -> pcb file -> pcb2netlist -> netlist file -> netlist2gsch -> sch > file -> gschem > pcb -> pcb file -> pcb2sch -> sch file -> gschem So the reverse should, one way or another, be similarly easy from gschem. Britton