X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type:content-transfer-encoding;
	bh=XSTc93IpBzBlRSQXdh3D0yyNOrjzj1cLonYndc1vtLg=;
	b=xEb42Vzk0971iPsqAdMdn5JvTyTd2pS7Z0vIh+RKNwQM15RK2smD6IJrLXpsUGIydu
	eBdk470AOngS0SEeN+J0UdRcDR4FsYuD8RPZYsPIStCPS69zhyMRJVp6fdOSedqtG0zc
	5nO+izDH3LXaJ8t163flcIKJcWC8QApHijb7XtwDpMwHhXhM/BWkNx6LNYNDMUdv03In
	86MusPvjeoAXFzMxSSvuu0qcMvQ41C4NUtH/oDayd5Z/P1TLB8ZVOo4pRg0Ync55I/qk
	8TNik9iPAOLpLxG8oH1MnqYrqkj+FMUb4M/Kd6Seu8x6czykTN0PO1SXWaiVlYyXczZu
	3pCA==
MIME-Version:	1.0
In-Reply-To:	<665E18E2-E9F9-40E4-9DE1-CC8FDBBDCB00@noqsi.com>
References:	<CANqhZFxYH+Y5U1ai7ey-s+4nz6eYDM2vx3aMDb7WuigNXmi4AQ AT mail DOT gmail DOT com>
	<2CB304B5-9587-4734-84E4-49F464744D11 AT noqsi DOT com>
	<CANqhZFwPNG4R1dR2X0HB+tP1JzNXUAVg55gy54Lry5E49aAQ6Q AT mail DOT gmail DOT com>
	<E9D200C7-475C-4CC7-A592-5A6C14B3EA25 AT noqsi DOT com>
	<6BF2E986-51EB-41E9-A4AD-8071CD00B1A1 AT jump-ing DOT de>
	<834283D4-0891-486E-A981-2FF20B32C615 AT noqsi DOT com>
	<C3C35AF4-24D1-4977-9134-2C0B13473D01 AT jump-ing DOT de>
	<54CAA7EE-7638-4B89-8197-111D0493F859 AT noqsi DOT com>
	<D59D8F6D-0436-4A8D-AFC0-5124BD3031D6 AT jump-ing DOT de>
	<508CE947 DOT 4050408 AT xs4all DOT nl>
	<665E18E2-E9F9-40E4-9DE1-CC8FDBBDCB00 AT noqsi DOT com>
Date:	Mon, 29 Oct 2012 11:17:42 -0800
Message-ID:	<CAC4O8c8Q_MSCg6af5Ro13KefdTkMFeEWXyQLrMWZsTw+yJLA6g@mail.gmail.com>
Subject:	Re: [geda-user] The state of gEDA/gaf (Was gEDA/PCBs diversity, Was:
	Pin hole size)
From:	Britton Kerin <britton DOT kerin AT gmail DOT com>
To:	geda-user AT delorie DOT com
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id q9TJHlj5011876
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 Sun, Oct 28, 2012 at 3:53 AM, John Doty <jpd AT noqsi DOT com> wrote:
>
> On Oct 28, 2012, at 2:13 AM, Bert Timmerman wrote:
>
>> You hit this nail spot on the head: it's all about momentum and how the software is perceived at first glance ... "you never get a second chance for a first impression".
>>
>> Fritzing does that with integration of a schematic capture + breadboard + PCB layout UI,
>>
>> KiCad does that with integration of schematic capture + PCB layout + 3D views and models,
>>
>> Eagle does integration of schematic capture and PCB layout UI,
>>
>> gEDA-tools do that with ... letting the user find his way in a maze of dispersed tools.
>
> gEDA enables the skilled user to do things far beyond the capabilities of the tools you mention. Symbolic circuit analysis, (with the help of Mathematica), VLSI design (with the help of other tools), or feed ~20 different PCB layout programs. Instead of wasting time with GUI, the gEDA user can automate document and data product generation by employing other tools like make and LaTeX.

John, I like gEDA for the same reasons as you, but everyone else is still
right.  It will die if the new user experience doesn't get better.

>> And a for user convienence www.symbols.org, only usable by fighting and conquering CVS (the SCM tool you will learn to hate).
>
> It's browsable by web, so consumers don't need CVS. And CVS isn't that hard.

cvs is a pain in the ass that no one wants to invest in learning anymore (I'm
delighted to have forgotten it) and this is a major barrier to contributions
to geda-symbols.  And geda-symbols is not complete enough as it stands to
be very useful (see http://www.gedasymbols.org/footprints/newlib.cgi?headers
for example).

>> So the gEDA-tools need to look "sexy" and needs more "eye-candy" to get this "sexy" tool-set to flirt with new (candidate) users.
>
> Nah, let 'em come when they figure out that the other tools can't get the job done. Then they'll actually appreciate gEDA.

The other tools will be able to soon enough.

>> 0.
>> Get the GUIs consistent with each other.
>>
>> 1.
>> Pull in xgsch2pcb as a first point of entry, squash any bugs left and implement outstanding feature request.
>> First step into integration, still keeping a use case for every single tool ;-)
>
> Shudder. If gEDA was focused on serving pcb, I wouldn't be here. What's the point of that? The tools above are likely to remain superior to the gEDA->pcb flow. gEDA's strength is all the *other* stuff it can do. Please do not let the weaknesses of pcb be the driving motivation for changes to the gEDA toolkit.

Its what probably 90+% of users use.  So if it loses bad enough and they go
away (or aren't replaced with new users) the software dies.

>> Start up/migrate www.gedasymbols.org to git and get "social integration" (like in Github) on those symbols, footprints, gnucap models, scripts and other related stuff
>> Give users a chance to improve on other users stuff with "pull requests" and "issues".
>> Give new users a chance to start with a fork of known good stuff that really works.
>> Maybe even move over to Github with the gedasymbols.org repo and let this organization handle the maintenance load.
>
> Git's a massive kit of power tools. I'm puzzled that you think that those users who reject the toolkit approach for EDA will be able to embrace Git.

I agree with you here.  It would be some decent way for people to share symbols
via the web or something.  Also it would be nice if gEDA traditional fear
of heavy (symbol+footprint) symbols would go away.  With a sparse library of
symbols the major value of the library will be as a set of prototype objects
for people to tweak, and having to merge the symbol and footprint halves is
IMO one of the things that makes gEDA so daunting for new users.

Britton

- Raw text -