Mail Archives: geda-user/2015/02/08/08:40:07
On Sunday 08 February 2015 13.59:25 you wrote:
> > My dream
> > would be a console in gschem (or standalone) for executing our own
> > scriptlets directly on the life data.
>
>
> When using gschem try hitting the ':'-key, voila a console! Now you
> need to brush up on your Guile coding skills...
Like that? http://www.gnu.org/software/guile/manual/guile.html#Running-Guile-Interactively
Yeah, very straighforward. Call me ignorant, but we all know C on some level,
and learning yet another language with a completely different syntax sounds not
like efficiently spent time to me. Simple scriptlets should be a mater of a couple
of lines, not a jungle of brackets. Especialy as we wan't to attract new
developers, we should lower the hurdles, not make them higher.
I once wanted to change a netlister backend to my needs, but I gave up and
used grep/awk/cut because of the (IMHO) obscure syntax of scheme. Simple
tasks like outputing the filenames of all the referenced symbols should be
possible with the netlister, not by pouring over the schematic files. Now I use
a Makefile rule to generate a dependency file for each schematic page and
import it. It works like a charm, but it took me some time (which rather spend
in doing schematics) to see my error in searching in the wrong places.
> > I'm no fanboy of lua, but with an standartised, scriptable data
> > format, adding a custom netlister or other small housekeeping jobs
> > like autonumbering, autoslotting should be straightforward.
>
> For autonumbering use the script named "auto-uref.scm", to activate
> it use a hook. For an example see your gschemrc file, find "hooks" or
> "add-hook!".
I normally use 'tu' in gschem, works also.
> When writing those custom netlisters or other scripts you need some
> Guile knowledge. My guess is that I need to find a Python tutorial, it
> is much quicker to teach myself Python than teaching others Guile.
+1
--
mit freundlichem Gruss
Christian Riggenbach
- Raw text -