MIME-Version: 1.0
In-Reply-To: <CAGRhJMbBg-ios4YJnVEbaTSNJNKmN1RuQZnfywhxt_2r8jPygw@mail.gmail.com>
References: <CAGRhJMbBg-ios4YJnVEbaTSNJNKmN1RuQZnfywhxt_2r8jPygw AT mail DOT gmail DOT com>
Date: Mon, 8 Jul 2013 09:12:24 -0800
Message-ID: <CAC4O8c9MimeU28JdZvTZ5VTmJ4FCJSJChrKf3k77OY8Rk4CS=w@mail.gmail.com>
Subject: Re: [geda-user] gschem script button
From: Britton Kerin <britton DOT kerin AT gmail DOT com>
To: geda-user AT delorie DOT com
Content-Type: text/plain; charset=ISO-8859-1
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
Precedence: bulk

Good idea, I might even use it despite being fine with command line,
since its a bit clunky to switch-run-script-reload.  pcb offers to
reload when it detects the file has changed, but sometimes crashes
when you say yes
(on my version anyway).

Britton

On Mon, Jul 8, 2013 at 6:29 AM, Joshua Lansford
<joshua DOT lansford AT laserlinc DOT com> wrote:
> Hey guys,
>   An idea for gschem and possibly pcb:
>   From my understanding, a lot of the power of gschem comes from the
> simplistic file format which allows external scripts to extract and change
> information.  I have utilized this myself as well as several other folks.
> For a command line kind of person like myself this isn't a problem.
>   For a gui type of person, jumping in and out of the program though the
> design iteration to execute external scripts seems like a design flaw.  (I
> don't think it is... just saying...) so I thought of the following idea for
> incorporating external scripts into gschem without script specifically
> having been design for inclusion.
>   Create a directive to include in the gafrc file which specifies
>   -a script filename with arguments and a $@
>  -an image icon,
>    -and a tool tip.
> This button then shows in gschem on the tool bar.  When this button is
> clicked, the in memory pages are saved to a temporary folder, the script is
> called with these pages and the temporary files are then loaded back into
> gschem without editing the original files.  The textual information of the
> script is shown in a popup.  The user can then immediately view the changes
> the script made, if any and if he/she likes them can then save them, or hit
> undo to revert.
>   This work flow process should handle bom generation, export to pcb,
> refdes_renum as well as innumerable other scripts which work directly on the
> file format itself.
>   Powerful scripts then become available as button clicks to those who try
> to stay clear of the ominous command line.  Just an idea.
> ~Joshua