X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-TCPREMOTEIP:	207.224.51.38
X-Authenticated-UID:	jpd AT noqsi DOT com
Mime-Version:	1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject:	Re: [geda-user] New experimental netlist features
From:	John Doty <jpd AT noqsi DOT com>
In-Reply-To:	<55E8773B.9000902@jump-ing.de>
Date:	Thu, 3 Sep 2015 13:01:53 -0600
Message-Id:	<B2444E14-A162-4118-B75E-57F319498B43@noqsi.com>
References:	<alpine DOT DEB DOT 2 DOT 11 DOT 1509031356150 DOT 13201 AT nimbus> <55E8773B DOT 9000902 AT jump-ing DOT de>
To:	geda-user AT delorie DOT com
X-Mailer:	Apple Mail (2.1878.6)
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id t83J2E44027091
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 Sep 3, 2015, at 10:37 AM, Markus Hitter (mah AT jump-ing DOT de) [via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:

> Am 03.09.2015 um 15:32 schrieb Roland Lutz:
>> You can clone the repository from
>> 
>>    git://github.com/rlutz/xorn.git  (branch "experimental")
> 
> The question of all questions is, when can Xorn enter gEDA and replace gnetlist, isn't it?

Gnetlist should stay for the foreseeable future. I’m not the only user with custom scripts for particular purposes.

> The netlister is one of the parts which should "just work", behind the user visible scenes, so I don't think it's neccessary it comes with every single feature the precedessor has.

I disagree completely. Gnetlist is the core of gEDA’s power. The ability to customize the extraction of various data products is what makes gEDA special. The point of having a toolkit is that the tools are user-visible, giving power to the user.

> In fact it may be a good opportunity to get rid of some old cruft.

Well, of course, the nice thing about a toolkit is the choice of tools. Xorn looks impressive, but I haven’t had time to study scripting it. I think Xorn makes sense as the future-looking tool, but I can’t see it replacing customized gnetlist-based flows in existing projects. I’m still coding Scheme. I agree that full backward-compatibility (whatever that might mean) is not a sensible goal for Xorn. And what constitutes “old cruft”? Maybe last year I would have classified the PADS back end as “old cruft”, but now it's important for one of my projects.

John Doty              Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com

- Raw text -