Mail Archives: geda-user/2015/09/17/16:00:23
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:-)
- Raw text -