X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.98.4 at av01.lsn.net
Message-ID: <55FB1BC6.7010503@ecosensory.com>
Date: Thu, 17 Sep 2015 15:00:06 -0500
From: John Griessen <john AT ecosensory DOT com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.7.0
MIME-Version: 1.0
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] key bindings
References: <alpine DOT DEB DOT 2 DOT 00 DOT 1509131209260 DOT 6924 AT igor2priv>	<55F5EFB6 DOT 6050809 AT ecosensory DOT com>	<alpine DOT DEB DOT 2 DOT 00 DOT 1509140349440 DOT 6924 AT igor2priv>	<20150914100244 DOT 4c371d64616a1ca14f7e3912 AT gmail DOT com>	<alpine DOT DEB DOT 2 DOT 00 DOT 1509161940580 DOT 3528 AT lichen>	<201509161753 DOT t8GHr83L007994 AT envy DOT delorie DOT com>	<CAM2RGhQVThXyZDX7vfBNY3-8SgA0gH78bc30swP-EWzTEVr5WA AT mail DOT gmail DOT com>	<201509161846 DOT t8GIk6Dm010388 AT envy DOT delorie DOT com>	<CAM2RGhSj4z8HTSCnA8FpG962aEJJsSmnh=TS__R_qkdW2=Jb9Q AT mail DOT gmail DOT com>	<201509161905 DOT t8GJ5MVY011855 AT envy DOT delorie DOT com>	<CAM2RGhQYtTKyBHVG+9tpCvYiVixgG_gtTbxX+Z+QvRZYp91tEg AT mail DOT gmail DOT com>	<mtd2db$kk2$1 AT ger DOT gmane DOT org>	<201509170049 DOT t8H0nEAZ031617 AT envy DOT delorie DOT com> <20150917202651 DOT 4694fbad57dd80862d7c67d8 AT gmail DOT com>
In-Reply-To: <20150917202651.4694fbad57dd80862d7c67d8@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: geda-user AT delorie DOT com

On 09/17/2015 01:26 PM, Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com] wrote:
>> Our current scheme is to define the hotkeys in the resource files by
>> >binding them to actions.  To bind them on a context basis, I think
>> >would require something more complex in our action scripts.  Perhaps
>> >Igor2's scripting work will give us a way to apply more complex
>> >bindings.
>> >
>>> > >BTW, starcraft also provides a good GUI way to facilitate learning
>>> > >the keys on the fly. On the lower right there is an area with icons
>>> > >of the currently available actions. These icons are decorated with
>>> > >the letter of the respective accel key.
>> >
>> >I think gtk offers a way to do this, if you use compatible APIs.
> I would consider the following good:
>    1. ctrl + "*" for compatibility with others.
>    2. Left hand one stroke for the most common actions.
>    3. Context based bindings (otherwise not enough keys).
>    4. Two stroke combinations for less common (increase number of fast actions).
> Decorated letters or similar methods to learn about them.

I've done some of this same kind of setup, and used it to mimic the
productive methods I used with Cadence SW for chip layout and
design rules.

In compiling and packaging releases, what would it be like to use directives
as we've discussed recently for setup stuff like that, even though it doesn't need
compiling?  Features like --disable-python leave out libs that get compiled.
How would one create switches like that for versions of config files?  I'm thinking
of those with names like gschem2pcb-newbie, gschem2pcb-big-EDA, gschem2pcb-from-Kicad,
gschem2pcb-from-orcad gschem2pcb-from-eagle, etc.  Then if we automated a build with scripts,
it could churn our 10 flavors of gschem and pcb installations with setup just matching
a description of what each is good for, and maybe even a targeted tutorial.
I might need to sign on as a junior developer though:-)