X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Date:	Sun, 8 Feb 2015 22:55:04 +0100
From:	Bas Gieltjes <bas AT gieltjes DOT dds DOT nl>
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] Using Lua to safely read configuration and layout
	files (program attached)
Message-ID:	<20150208225504.38118306@Parasomnia.thuis.lan>
In-Reply-To:	<1897145.BbSdS1MRWc@jasum>
References:	<CAOFvGD7pJTo8A=MXVbuuXO=++0vGukUyqVfckVtnCi99ziqWJQ AT mail DOT gmail DOT com>
	<3709636 DOT NVszrDDjOR AT jasum>
	<20150208135925 DOT 6f6ddab6 AT Parasomnia DOT thuis DOT lan>
	<1897145 DOT BbSdS1MRWc AT jasum>
X-Mailer:	Claws Mail 3.11.1 (GTK+ 2.24.25; x86_64-pc-linux-gnu)
MIME-Version:	1.0
X-OriginalArrivalTime:	08 Feb 2015 21:55:04.0738 (UTC) FILETIME=[E54F8820:01D043E9]
X-RcptDomain:	delorie.com
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id t18Lt9ZU012484
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

> Especialy as we wan't to attract new developers, we should
> lower the hurdles, not make them higher.

Maybe it comes down to attracting more users of the geda suite of tools?
After a while those users could become (badly needed) new developers.

Most(?) new users expect an integrated suite of programs that you can
control using the mouse and to get thing going really don't want to use
any scripting language.

Maybe after a while that users starts to dig into the scripting part of
geda, becomes a "power" users and starts to script the environment and
leaves (once in a while) that comfortable gui.

Creating a seamless integrated suite of tools to attract users is
another rabbit hole. When you dive into that hole don't forget that
there are users that script their environment.

> 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. 

To my knowledge gnetlist is unable to output filenames of the used
symbols, don't blame Guile but extend the current interface. Does Lua or
Python solve that problem? For all those scripting languages you need
to code that functionality. What about adding that functionality to
gnetlist? Or create gnetlist-lua and replace gnetlist/src/g_netlist.c's
Guile code by a Lua implementation to create an alternate netlister
using Lua scripting (the configuration is still done by Guile).

 Bas
-- 

- Raw text -