X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Wed, 30 Dec 2015 07:30:19 +0100 (CET)
X-X-Sender: igor2 AT igor2priv
To: "Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
X-Debug: to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu"
From: gedau AT igor2 DOT repo DOT hu
Subject: Re: gEDA and it's future with Scheme & Guile was Re: [geda-user]
 Project leadership
In-Reply-To: <CAM2RGhR+zp5LAXPC1hVbFDfTsbtWg9cLA38G00EZSAq23UzkvQ@mail.gmail.com>
Message-ID: <alpine.DEB.2.00.1512300729130.9035@igor2priv>
References: <CAM2RGhS4L-ch6FEcLtdSt0vA0BdQZvq+AuFDP+9ea7Ftd=AALg AT mail DOT gmail DOT com> <8444F816-17CE-4A56-A982-4A60DEDA72B8 AT noqsi DOT com> <alpine DOT DEB DOT 2 DOT 00 DOT 1512300544550 DOT 9035 AT igor2priv> <87FC7D4C-157A-499E-8B93-97653D6A7C68 AT noqsi DOT com> <alpine DOT DEB DOT 2 DOT 00 DOT 1512300641030 DOT 9035 AT igor2priv>
 <CAM2RGhR+zp5LAXPC1hVbFDfTsbtWg9cLA38G00EZSAq23UzkvQ AT mail DOT gmail DOT com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
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



On Wed, 30 Dec 2015, Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com] wrote:

> On Wed, Dec 30, 2015 at 5:46 AM,  <gedau AT igor2 DOT repo DOT hu> wrote:
>>
>>
>> On Tue, 29 Dec 2015, John Doty wrote:
>>
>>>
>>> On Dec 29, 2015, at 9:54 PM, gedau AT igor2 DOT repo DOT hu wrote:
>>>
>>>> - gschem doesn't have cosistent concept of its goals. It pretends it
>>>> doesn't need to know about nets because it's a dump editor, but it does know
>>>> about slotting and has lists of hardwired attribute names in code
>>>
>>>
>>> And some of us think that those are design errors. There are several
>>> alternate notions of how slotting should work. If you want slotting in
>>> gschem, you should load a suitable script.
>>
>>
>> You are trying to avoid answering the real problematic part, picking on the
>> small things.
>>
>> Any EE I've ever met or worked with talked the same language. The most
>> important bricks of the language were compoment and network names. Does
>> gschem speak this language?
>>
>> Compontent names: refdes; it's hardwired all around to make gschem more or
>> less understand the language. Still it is not strong enough so that we can
>> really idetify (search, find, list) a component by name and make sure we get
>> what we need to get.
>>
>> Network names: gschem has absolutely no idea about networks. Gschem fails to
>> model this aspect of the world.
>>
>> I am all for plugins and scripts (but against restricting the user to one
>> specific scripting language). However, there must be a core of the tool,
>> which is not a plugin, not an user provided addon. This core should try to
>> speak the same language to at least a minimal extent, that the userbase
>> does. To me it seems gschem fails on this. It probably could be worked
>> around with endless streams of scheme scripts, but it'd be easier to admit
>> it and come up with a proper fix in the core.
>>
>
> +1 Every EE I know can do some C. Only a small number from MIT know
> scheme and in the words of one professor there "We stopped using it
> when we realized there was more value in educating the students than
> torturing them."
>

I didn't mean that. I meant language as "network names" and "component 
names". I.e. the EE wants to find network "adc_5" and "pin 1 of U5". This 
is the "query language". It's not about programming languages, it's an UI 
question.