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=20161025;
        h=mime-version:references:in-reply-to:from:date:message-id:subject:to
         :content-transfer-encoding;
        bh=XuZV3JvbaiKRuvM+sooJIKzGqkIkTUyKRkuXsmQsTIo=;
        b=NLTfYhgoam+uzmJ4sh6wa7ESJKgEATl1uSU7QfiP8xsrdKcLnZETrIBLc1G+VDFQPC
         KpaEWMr2NbQ1yR9Y8NIX87Oy0RaaCy+cRG2G/hGny1rFQ8T0UonEVGaMMRd2/vBlEDNI
         a9g6vy6X9XNaIA548Kg/05xvDDUdNxn8XO3WknkbB1IsktbyfKpu68jRsqu6faCueghg
         lGzhe8vhrqprIFC+AXRXENWlAmJRcMETrHL98FOI6a8JviFsnFgdOhDL185hCcukC7XO
         wRF5mIItZ9nPnz3XxocHTR9+5TdhfpOcoVkUofghDeMxQ5cO6wAx2Savt4s0JoK0fzPy
         qBDg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:references:in-reply-to:from:date
         :message-id:subject:to:content-transfer-encoding;
        bh=XuZV3JvbaiKRuvM+sooJIKzGqkIkTUyKRkuXsmQsTIo=;
        b=SmAaHWXWq2Fy+ZU3f2Mk9rqep3pchNRWKKoeHR3jDyOFjxfRu46zU6F9Vf5UL3O5m4
         i1TprDJohpGp7z6VcFkR+XcXiJ3ASMhUTu/c8+CaRl/muEadA7ARw6AukfGpAKvQbwXY
         BDIZlkvO8+RR1U4MPOYOJBUxTPvcF2yZf7Przf9nBqjkRtKXwjx3JNizsv/mrRlzzDf7
         QusN1EagjPgSlqOzP9JmAzNQKwr+UeptYAvv/8dy221bz+0hW2Kidm+iThCsEAizdH++
         U/OzjRTXMkh5eGLgnL9UK7dZTVVZUUj2QeQ65GcZdrDkg+xCO3RTjVX1fMhBciPRClWb
         rt6g==
X-Gm-Message-State: APjAAAWO7Bxdx74NBe/ljmvmIluscmBJhrwgXu6+vM67zQVNRgXwhgI9
	wDNGCu7W/OnW1PH/nunnbPuACQlBAGidRHkkTU9kpCB1
X-Google-Smtp-Source: APXvYqz0/8UKgOGdn3tlbRO8TY8AP34oIuGG+hgFSMk7/48TXMWE/vNRVBfaYmJbIEj+JjZsma6I4Fc0HLclA+3RoqE=
X-Received: by 2002:a9f:2213:: with SMTP id 19mr2208201uad.25.1567437117052;
 Mon, 02 Sep 2019 08:11:57 -0700 (PDT)
MIME-Version: 1.0
References: <CAPp8_DqaZpOpdKFrUF7HC9sbCG2ag0a2iuWQrSkOY76U1kRQ6g AT mail DOT gmail DOT com>
In-Reply-To: <CAPp8_DqaZpOpdKFrUF7HC9sbCG2ag0a2iuWQrSkOY76U1kRQ6g@mail.gmail.com>
From: "Shashank Chintalagiri (shashank DOT chintalagiri AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Date: Mon, 2 Sep 2019 20:41:45 +0530
Message-ID: <CALT8Ef5UGWs0oFLx-EraLACB4H0D_KRaxb9io2uRZjbg3soPvQ@mail.gmail.com>
Subject: Re: [geda-user] gschem interaction from external processes
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 x82FCYHF014194
Reply-To: geda-user AT delorie DOT com

I've gone down a similar road before. Though what I was doing
explicitly tried to not touch the internal workflow of gEDA and gschem
as far as possible. From a practical perspective, I found it more
viable and stable to be able to parse the files generated by software
such as gEDA and act on those actions using automated versions of the
natural interaction method for the software.

In the case of gEDA/pcb, I found that executing the programs with the
correct flags acting on .proj files was usually good enough to get
what I needed.

Of course, I'm not saying it isn't possible, just that it might turn
out to be a whole lot of high maintenance code that will be needed
long term.

If you wish, you can let me know and I can try to summarize what I do.


On Mon, Sep 2, 2019 at 4:56 PM Majenko Technologies
(matt AT majenko DOT co DOT uk) [via geda-user AT delorie DOT com]
<geda-user AT delorie DOT com> wrote:
>
> I am attempting to build an integrated project management system based around gschem and PCB and associated tools. Something which integrates the tools together into a single workflow.
>
> As part of this is an automated (by automated I mean you click one button in the interface) "Save open schematics and PCBs, Run gsch2pcb, Reload open schematics and PCBs from disk, Load new netlist and layout to buffer" operation.
>
> Of course, part of that is getting gschem and PCB to save their files and "revert" from disk after files have been changed externally.  For PCB that's not a problem - I just launch it with --listen and I can interact to my heart's content.  gschem is a little harder though.
>
> I have modified the code so that it responds to two signals, USR1 (save all pages) and USR2 (close and re-open all pages), and it (kind of) works (at the moment it's dumping random "untitled_1.sch" files around the place, but I can fix that...). I can't help feeling that it's a little clunky though, and am wondering if there is a better way of implementing it.
>
> What would be ideal would be a "--listen" system like PCB has that would allow you to send SCM scripts directly to the running process. I don't know how any of that is implemented though, so have no clue if that would be practical or not.
>
> So really I'm looking for ideas from people that are more familiar with the internals of gschem than I am...
>
> --
> Matt Jenkins
> Majenko Technologies
>


--

Chintalagiri Shashank
Indian Institute of Technology, Kanpur

http://blog.chintal.in