X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] Possible paths of gnetlist development
To:	geda-user AT delorie DOT com
References:	<alpine DOT DEB DOT 2 DOT 11 DOT 1609221743230 DOT 2817 AT nimbus>
From:	"John Griessen (john AT ecosensory DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Message-ID:	<85005a41-cd1d-de70-971c-743bae8046b2@ecosensory.com>
Date:	Thu, 22 Sep 2016 16:06:41 -0500
User-Agent:	Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
	Icedove/45.2.0
MIME-Version:	1.0
In-Reply-To:	<alpine.DEB.2.11.1609221743230.2817@nimbus>
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

On 09/22/2016 10:59 AM, Roland Lutz wrote:
> 3.) Proper parameter substitution
>
> The currently available patches for parameter substitution in subschematics are relatively simple: they can only influence
> attributes which are output by the backend, not anything which is used by the netlister itself.  In order to be able to use
> parameters in refdes=, slot=, or net= attributes, a more sophisticated approach would be necessary which allows for multiple
> versions of a schematic to co-exist.
>
>
> 4.) A netlister GUI
>
> At the moment, gnetlist is typically invoked in the background (e.g. by the PCB "Import Schematic" feature).  Now that more useful
> error and warning messages are available, it may be desireable to have more direct control over the netlisting process via a GUI,
> in particular to be able to select messages and jump to the corresponding object in the schematic file.

These seem high value to me.  They would eventually allow capacitance extraction for one...

- Raw text -