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=relaxed/relaxed;
	d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type;
	bh=DvxN47hoYftlFJh9CxmVT235WeO/VW5HyFzdi5vWHng=;
	b=M2MO9qqYuo4ngOpeI7rxmRaUqtHacBGD9mUr3Iu+vitSix1f64+4JQtIQAGZiZkAUf
	vN/pFWpVcbx5Wq+/eBz5PTRRUWWfY/TJzQ7PHdk+fAiyZ4J/jg6TgNQ5K52dKvBRGJ8D
	ZYNsT/uVqyXoIF5AsSnhP6ySugua0hUGM2cgfzg6e0puNPCNHFygbjaCVvfQi6shVm04
	CLPsR0y10fJelRaiI9g83cbxSiv2RQTIODZIyPKhcFfMzcLF0wdXwvuyGCTnUZxlxWM3
	iBWR6DGPn37e7KTpvfMTSp7Tl3hDaS9ceM3KvSVi63W3FKIguMpXHLsOBWFBuM5iTIN0
	el3w==
MIME-Version:	1.0
X-Received:	by 10.112.120.134 with SMTP id lc6mr7234194lbb.86.1436816462708;
	Mon, 13 Jul 2015 12:41:02 -0700 (PDT)
In-Reply-To:	<55A4042E.5060402@neurotica.com>
References:	<CAM2RGhQ70Pex5aNeQ86vKHc7sKf_Vpws69__CPb2QKg6fJTeHg AT mail DOT gmail DOT com>
	<55A2A0A2 DOT 4080403 AT ecosensory DOT com>
	<7AE39440-DA68-4491-A965-C1B97D1D86C1 AT sbcglobal DOT net>
	<20150712213152 DOT 7968b74c AT jive DOT levalinux DOT org>
	<304D9D86-3CF6-4D61-A5CA-6CE414EA0661 AT sbcglobal DOT net>
	<20150712224637 DOT 2d4cc2de AT wind DOT levalinux DOT org>
	<55A2E9B7 DOT 9040502 AT neurotica DOT com>
	<CAM2RGhSmFhz9=oRaaj2EDL79c5XVmeuwmX_RdLqMv0evEHCyTw AT mail DOT gmail DOT com>
	<CACwWb3DbmOZbtb9Hrp2JvvG7-toryXuequQA=YV7X6ss762zsw AT mail DOT gmail DOT com>
	<20150713131707 DOT GA782 AT recycle DOT lbl DOT gov>
	<CAM2RGhTT__nWCkA4y36rb24yT8xP=o1nR04H=DNqTJiu=naSGA AT mail DOT gmail DOT com>
	<55A4042E DOT 5060402 AT neurotica DOT com>
Date:	Mon, 13 Jul 2015 15:41:02 -0400
Message-ID:	<CAM2RGhS=5xq0_oN4e0M55Kor4bcnXNn3NfLvRZoi7Vw9Aq1ZXg@mail.gmail.com>
Subject:	Re: [geda-user] The new to do
From:	"Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
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 Mon, Jul 13, 2015 at 2:32 PM, Dave McGuire (mcguire AT neurotica DOT com)
[via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
> On 07/13/2015 11:36 AM, Evan Foss (evanfoss AT gmail DOT com) [via
> geda-user AT delorie DOT com] wrote:
>>>> I see this FLTK thing, and it looks good, but this is not mature.
>>>
>>> FLTK had its initial release in 1998.  I personally have used it, and
>>> can attest to its working well (by its own standard) since about 2006.
>>> I don't know how that can be considered not mature.
>>>
>>> Sorry to add one more bit of non-geda noise.
>>
>> Noise is better than silence and there is content in your words and
>> other peoples. The hard part is figuring out how to integrate
>> everything into a plan.
>
>   Then the next hard part is people finding time to do the actual work.
>  Every time all of us have a big conversation about the next big step
> for gschem or PCB, it ends with nothing (or nearly nothing) actually
> getting done.  It happens every couple of years.

Yes well. I have a good feeling about this time. Although that might
be a side effect of my own intentions.

>   I think what we need to motivate actual development, rather than
> conversation, is cold hard CASH.  I'll kick in a few bucks for the next
> round of development, whatever it may be, for gschem and PCB.

It got a long way with out paid developers. I think kicad got
basically just as far before CERN got involved and it remains to be
scene how much farther it will go. At the start CERN just wanted an
open source project equivalent to Eagle, after they get that who knows
if they will continue. There are underlying issues remaining with
kicad's code. eeschema as I understand it suffers the same fundamental
issues as our PCB.

http://ci.kicad-pcb.org/job/kicad-doxygen/ws/Documentation/doxygen/html/md_Documentation_development_road-map.html#eeschema

* Coherent SCHEMATIC Object "Clean up the code related to the
schematic object(s) into a coherent object for managing and
manipulating the schematic."
<- to me this reads exactly like our current problem with PCB
* Hierarchical Sheet Design "Create a more robust sheet instance
design rather than recreating them on the fly every time sheet
information is required."
 <- we have this now
* Schematic and Component Library Plugin "Create a plugin manager for
loading and saving schematics and component libraries similar to the
board plugin manager."
<- we are bating how to architect this
* Keepout Zones. "Add support for keepout zones on boards and footprints."
<- This is a wanted feature for us too

>   Anyone else?
>
>                  -Dave
>
> --
> Dave McGuire, AK4HZ
> New Kensington, PA



-- 
Home
http://evanfoss.googlepages.com/
Work
http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/

- Raw text -