Message-ID: <b3d7aec4-6bad-0938-0f44-a68130f66e45@mcmahill.net>
Date: Tue, 24 May 2022 00:58:28 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
 Thunderbird/91.9.0
Subject: Re: [geda-user] Re: gschem/lepton: gafrc security issue
Content-Language: en-US
To: geda-user AT delorie DOT com
References: <alpine DOT DEB DOT 2 DOT 20 DOT 2204280758280 DOT 25839 AT igor2priv>
 <fbaecf7b-1c84-fe7-5f30-35722fb35f13 AT grinsen-ohne-katze DOT de>
 <20220429135341 DOT 4559b215 AT yo>
 <71564b8-b39-ca3b-b01c-78fbc7e4fe AT grinsen-ohne-katze DOT de>
From: "Dan McMahill (dan AT mcmahill DOT net) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
In-Reply-To: <71564b8-b39-ca3b-b01c-78fbc7e4fe@grinsen-ohne-katze.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
Precedence: bulk

On 4/29/2022 2:58 PM, Roland Lutz wrote:
> On Fri, 29 Apr 2022, dmn (graahnul DOT grom AT gmail DOT com) [via 
> geda-user AT delorie DOT com] wrote:
>> Currently, gafrc and gschemerc files are still used
>> to define the following remaining settings [3]:
>> - gafrc:
>>  - component and source libraries
>>  - print color scheme
>> - gschemrc:
>>  - keyboard shortcuts
>>  - color scheme
> 
> Yeah, that's about how far I am, as well.
> 
> Color scheme is a surprisingly hard problem.
> 
> "Keyboard shortcuts" doesn't capture the complexity of the problem. 
> gEDA/gaf has a completely configurable menu (and since 1.10.0, toolbar) 
> system, and some users employ this to add complex additional 
> functionality to gschem.  This is also why GTK migration is a problem; 
> this kind of setup requires tear-off menus to be used efficiently which 
> are no more supported in GTK 3/4.
> 
> Libraries are just the tip of the "project awareness" iceberg.
> 
> Replacing one kind of configuration format with another is the easy 
> part. Just offering it as an alternative isn't enough: in order to close 
> the security barn-door, the old executable configuration format would 
> have to be removed, or at least discouraged by the GUI.  I don't want to 
> take the ability to a hack a custom solution away from users without 
> figuring out these cases and offering a proper alternative.  This is the 
> hard part.
> 
> Roland
> 

Regarding configurable menus and other extensions, a vision I had and 
started on some of the infrastructure for ages ago was to be able to 
support "modes" in gschem sort of like how emacs has major modes for 
editing different sorts of files (C, python, LaTeX, Makefile, etc). 
Maybe you're using gschem to drive a spice simulation, so enter spice 
simulation mode and get menus that are appropriate for the simulator you 
have.  Maybe it is for driving a pcb layout and you get those sorts of 
menus.  Unfortunately other commitments in life took over and I never 
really got it to the point I wanted.  I'm guessing some of that code is 
still in place though.

-Dan