X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=mail.ud03.udmedia.de; h=
	subject:to:references:from:message-id:date:mime-version
	:in-reply-to:content-type:content-transfer-encoding; s=beta; bh=
	bsxp49moMxKOPA2qdZ7FcWw1nsVBZGv0K9umu+UuNDg=; b=bnNVuMUjqjs3c0Fn
	imnJcBH+zzsi2yTNIFHi2mL/xjNaExeECnbiuPL70NyGOTXwpWMw/TSWXF4MgO1H
	0qU/qaTdOnNoa7jx/TczWaTE45Zds7k7ZzGj1bpNlVPQRQNzNF9RJ1+nxKwCoYkt
	O0TFC2kxsfKfakKd0yhtH9/ruBk=
Subject: Re: [geda-user] New experimental netlist features
To: geda-user AT delorie DOT com
References: <alpine DOT DEB DOT 2 DOT 11 DOT 1509031356150 DOT 13201 AT nimbus>
 <55E8773B DOT 9000902 AT jump-ing DOT de> <alpine DOT DEB DOT 2 DOT 11 DOT 1509031846370 DOT 7163 AT nimbus>
 <55E8831A DOT 8050307 AT jump-ing DOT de> <alpine DOT DEB DOT 2 DOT 11 DOT 1509032004020 DOT 10628 AT nimbus>
 <55E891FA DOT 2010509 AT jump-ing DOT de> <alpine DOT DEB DOT 2 DOT 11 DOT 1509032039300 DOT 14871 AT nimbus>
 <BC7E3E69-4914-4654-B020-1338C71E0CDB AT noqsi DOT com>
 <201509032030 DOT t83KU1Yq017045 AT envy DOT delorie DOT com>
From: "Markus Hitter (mah AT jump-ing DOT de) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Message-ID: <55E97A3E.2070402@jump-ing.de>
Date: Fri, 4 Sep 2015 13:02:22 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <201509032030.t83KU1Yq017045@envy.delorie.com>
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: 7bit
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
Precedence: bulk

Am 03.09.2015 um 22:30 schrieb DJ Delorie:
> Do we want to retain backwards compatibility?  Yes.  Do we want to do
> so at the expense of new development?  No.  How do we reconcile these
> two goals?  I don't know, and nobody has offered a workable solution.
...
> So how do we proceed?  I think each side needs to consider the needs
> of the other side, and try to come up with a solution that leads to a
> seamless transition from the old way to the new way.  We can't afford
> to either choose "don't change anything" or "replace the old with the
> new".
> 
> We need a third option that involves some compromise from each side.
> 
...
> Don't forget the ton of documentation and random web pages that refer
> to "gnetlist" that will no longer be the "preferred way".

I think the secret is to make the GUI-only workflow for the usual
schematics -> pcb -> Gerbers task complete. With orange and/or xgsch2pcb
we're almost there, so let's do the final touches. Tutorials should be
replaced with ones using GUI tools only. 90% of potential newbies don't
even try when they see a tutorial which asks to type commands. Having
the GUI workflow, the name of the underlying tool matters a lot less.

The birth of a new tool also brings in marketing opportunities. "gEDA
now with Xorn, the new powerful netlister. Now you can 1) ... 2) ... 3)
..." and so on. People put a lot more attention to something entirely
new than to refinements over the years.


Markus

-- 
- - - - - - - - - - - - - - - - - - -
Dipl. Ing. (FH) Markus Hitter
http://www.jump-ing.de/