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:content-transfer-encoding;
	bh=cjrf7tqD7gcaVwtU+NqMf005iBVwutDpIb57fCeKvjk=;
	b=hbPvUCx7tYV0AijQPZjkiXBTPukLYAdBXVCS4U9NhjjYuT56hyka2vpLaPwRgTu0Kn
	xmHiFkUtBCH5oNib2o3S/XaGM+szQ2abeVT1IqlNzr68pJyVEZByGW+fHfIOfmHdduNy
	hrPSm7OA99Kw0j6uN6IMP7CbUhWe7x7/uMtiTaHrZA9JgleYJKw6bTJyej0N9x7LEdvA
	fW6wmkdAUX/u6em+zq/TgaRok/WBsyPXuUXRurpRRDlIK9Mqo6EFzyhqhY+J7SjWY+P0
	PdfzFCVeOjWAMy9KuztgMjRNxcWj/gCn/SkTsBAIuZuKofjRDuBEVb8hBBPXL3A7HHNH
	jxYQ==
MIME-Version:	1.0
X-Received:	by 10.25.40.130 with SMTP id o124mr189002lfo.41.1444791246249;
	Tue, 13 Oct 2015 19:54:06 -0700 (PDT)
In-Reply-To:	<C8AC7729-F0BC-4CFA-95DA-65CCEF10EC4E@noqsi.com>
References:	<1042003D-82E2-40F0-AB60-8186580C46AD AT noqsi DOT com>
	<201510121905 DOT t9CJ5T9W026297 AT envy DOT delorie DOT com>
	<CAM2RGhTMnybSnYgnNhVZGA6PTvyJu+=Kzd5LX2HMqxT1F4LoRg AT mail DOT gmail DOT com>
	<88EA58F5-2B23-498A-9E5B-84054976DBED AT noqsi DOT com>
	<CAM2RGhTPPtqmWVa3=Kf-PeN+WS5Tn4J+D0Ri6R_4OrQOk+LFKQ AT mail DOT gmail DOT com>
	<4D3CD563-D8EE-4B2A-975A-AC2B573960FF AT noqsi DOT com>
	<CAM2RGhT8WzhwvzFx3Rfv8vN-f=i1=uWuLF+48VygSRtfdzdo-A AT mail DOT gmail DOT com>
	<34B17816-9EA5-45FD-BFB4-9D623A8D3D87 AT noqsi DOT com>
	<CAM2RGhR+K+dvDdXsbk0Y6LN=-7RhhG5wvtG4i0k4+uMgzd=H0w AT mail DOT gmail DOT com>
	<39FF6208-7D45-4DE8-9AEE-1ED1B512705B AT noqsi DOT com>
	<CAM2RGhROpz_3y2JB=xEkEQ3CMHqHJ_WZxqVrbQhP4q2mg40h8g AT mail DOT gmail DOT com>
	<C8AC7729-F0BC-4CFA-95DA-65CCEF10EC4E AT noqsi DOT com>
Date:	Wed, 14 Oct 2015 02:54:05 +0000
Message-ID:	<CAM2RGhTSPvQguBwNQRXEnkk5snEWxi0kTe-NXv3x42Xs6Q426Q@mail.gmail.com>
Subject:	Re: [geda-user] A lesson from gnet-makefile
From:	"Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	gEDA users mailing list <geda-user AT delorie DOT com>
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id t9E2sC5o025916
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 Wed, Oct 14, 2015 at 2:25 AM, John Doty <jpd AT noqsi DOT com> wrote:
>
> On Oct 13, 2015, at 8:01 PM, Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
>>
>> You assume I am going to be like a bull in a china cabinet.
>
> No, I assume that you don’t know what might break the tools.

Condescending.

> I am confident in this, because I don’t know of anybody who uses the full breadth of geda-gaf. So nobody really knows what might break them.

We need a design document to break down what is and is not going to
break tools. This is a recurring sour point and there has to be a set
in stone guide or it will just inhibit all development for ever.

I can not help but notice you skipped over a few of my other points
including the ones about back notation and convolution.

>> I
>> deliberately declined to have direct commit privileges. If my code is
>> going to the mainline it will I expect have to get a review. Given how
>> open we are to other peoples ideas here getting past that will ensure
>> a level of quality no lower than any previous work.
>>
>> For my contributions I will be glad to write tests of them. We should
>> have a larger regression testing framework though.
>>
>>> Despite Peter Brett’s great work, we simply don’t have the tests necessary to insure that changes to the core don’t affect somebody’s flow.
>>
>> It depends on how people choose to use what I want to add. It simply
>> being there is not going to break flows.
>
> In the core, it might. Features interact. But a plug-in that isn’t plugged in is perfectly safe.

Yes and this is a something that multiple plugins and programs across
geda should use defines what core functionality is in my mind.

>> Everywhere the original flat model exists people should have the
>> option of the new one. The key word being *option*. I am not about to
>> try to remove the old s_conn stuff just build something else next to
>> it.
>
> Why can’t you do this in Scheme? Or in Python with Xorn?

We already talked about scheme. As I recall you and I were in
agreement that scheme needed to be de-emphasized.

I want to build out all the functionality we are going to need to make
a lot of long standing functionality possible using the current
architecture. After that is done I want to write another plugin
interface that works in parallel to scheme.

I want to try to advance gEDA. Xorn is a part of gEDA now but it is
kind of off to the side as an alternative to gnetlist. I put a lot of
effort into learning the ways of libgeda and I am not about to abandon
all of that.

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



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

- Raw text -