[Rwp] OSARA keymap

[Jim Snowbarger]

It's important not to get discouraged over the predictable fact that
opinions vary on virtually every aspect of any user interface.
In my opinion, there is absolutely no way to make everybody happy about
this.  There is no key map in the world that somebody won't like for some
reason.
If you told people that control+v would be used to paste, and they had never
used that before, people would argue against it.  But, as it is, it is
common place, and nobody fusses about it.
If I were you, I would just bundle Osara with my own preferred key map.
And, if some common agreement came along later, it could be changed.  But,
more likely, people will just learn to use what is there, with minor
exceptions, and life will be good.

I say, don't let discouragement over the predictable level of disagreement
about such a matter detract from the broader benefit what is being
accomplished more generally, and go from there.   If Osara can be
configurable in that regard, that would be great.  
But, keep the focus on the functionality it provides, and let the ergonomics
come later.




-----Original Message-----
From: RWP [mailto:rwp-bounces at bluegrasspals.com] On Behalf Of James Teh via
RWP
Sent: Sunday, February 22, 2015 9:32 PM
To: Reapers Without Peepers
Subject: Re: [Rwp] OSARA keymap

I can't find any solid info regarding CakeTalking's keymap, but I did find
one post that suggests they use m and s for mute and solo, and I imagine
this extends to arm and input echo as well. That is, if I'm correct, they
*don't* use function keys. We could do the same for OSARA, but that would
mean moving the marker and split keys.

At this point, I'm tempted to just bundle my keymap until we can reach some
sort of better consensus.

Jamie

On 23/02/2015 1:10 PM, John Schucker via RWP wrote:
> I personally don't mind multiple key presses, and I'm pretty sure 
> CakeTalking does this, for example. I also find function keys 
> annoying, e.g. in GoldWave. They're a stretch for me to reach from the 
> home row, so I just have to treat them as a separate row, and I 
> usually end up counting and such. So I'm in favor of Jamie's keymap.
>
> Could we have a keymap import function, or some simple way to replace 
> it? I mean, if we're just overwriting files, I don't see why Jamie 
> can't have whatever keymap makes sense to him as a default. Then 
> somebody else can maintain a map with function keys and such, similar 
> to Reaccess I guess. If you want that, if it's such a problem for you 
> that you can't use function keys, I'm guessing you'll know enough, or 
> easily be able to learn, to overwrite the default Osara keymap. It 
> sounds like all you should need to do is copy and paste a single file 
> anyway, so it really shouldn't be that hard.
>
> But for what it's worth, I'd prefer non-function key mappings. I don't 
> think pressing ctrl-shift-m, for instance, is all that much harder 
> than pressing 'm' by itself, and certainly easier, for me at least, 
> than figuring out what function key I need to try to find. I'd also 
> think if people are that much in need of single keys, again, you could 
> either import a map, remap them yourself, or get a control surface. I 
> realize surfaces aren't cheap, even the Behringer is a couple hundred, 
> but I imagine if you're arguing that you're doing so much serious work 
> that ctrl-shift-m slows you down unnecessarily, you'd probably want 
> some kind of surface anyway.
> _______________________________________________
> RWP mailing list
> RWP at bluegrasspals.com
> http://bluegrasspals.com/mailman/listinfo/rwp

--
James Teh
Email/MSN Messenger/Jabber: jamie at jantrid.net Web site:
http://www.jantrid.net/
Twitter: jcsteh

_______________________________________________
RWP mailing list
RWP at bluegrasspals.com
http://bluegrasspals.com/mailman/listinfo/rwp