DreymaR said:I'd have more than 0 on the home row keys, although that may just result in a total penalty shift in the model? Also, the pinkies and ring fingers are about the same I feel. Maybe add 0.25 to all eight home position keys except pinkies? Also, the BK keys aren't really easier than FU I believe, so maybe 1.0 on those too? Also, I don't see why Q: should be that much harder than GJ – when trying them out they feel about the same to me.
The values are relative. I'm not sure adding a base difficulty makes a difference on reading the chart. But if I were to write a program to analyze layouts, then I would start to calculate more exact values based on various criteria, such as can be found at http://andong.azurewebsites.net/dvorak/ … iency.aspx . Another factor to take into consideration is inter-key combinations and penalties (but probably too complicated to fit on a single chart).
The pinkies are easy to tire out and cumbersome during rolls. OTOH, the ring fingers are stronger and closer to the middle of the hand, thus have better support and quicker during rolls. But since the home keys don't require reaching, the difference isn't that noticeable for single presses. Moreover in practice, there are other more important factors concerning these two keys (such same key presses with top and bottom rows).
I'm confused about the BK vs FU comment. Maybe you misread the chart? The BK keys in the middle columns require stretching the index fingers, thus the higher effort score.
Stretching the pinkies is very different than stretching the index finger. For one, the index finger is longer and stronger. Also the arms simply go in and out to reach the keys, whereas the pinkies requires more twisting of the wrist. However, these motions may be different depending on the keyboard you use. I based the chart on mainly the Kinesis where keys are aligned in columns and the hands are spread far apart from each other. On a standard keyboard, the hands are together and the arms bend towards each other. So the pinkies have easier access to the top row. Nevertheless, many Dvorak typists have complained about the placement of the L in such an awkward position at the top pinky.
lalop said:Amuseum's model might deserve a new thread of its own. As for the chart itself, I can't say I completely agree with it. For me, at least, the middle and ring fingers already hover between the middle and top row, making those positions relatively easy to press; IMO, even easier than QWERTY V.
In one of my Widely Alternating experiments, I did try putting D on the QWERTY V position in accordance to Workman-like models. I ended up swtiching it back to QWERTY G, however, feeling like it was causing too much... I'm not sure, twisting?
Obviously when your hand is moved farther away from the bottom row, the bottom keys become harder to reach. The standard keyboard design does encourage hovering between the home and top rows. However, I don't think that is the most natural or comfortable pose for the arms and fingers. On the Kinesis, my fingers and arms are extremely relaxed; I never swing or twist my arms too much or use much effort to reach with my fingers. I don't have to hover towards top or bottom row; both rows are equally accessible and neither are preferred over another except by the fingers' natural inclination.
Each finger has different lengths and curvature. Just hang your fingers in the air in front of you. You can tell that the middle and ring fingers lean away from you, whereas the index fingers and pinkies lean closer to you. Now if you compare my chart, you will see a similar pattern where the middle and ring fingers favor the top row, while the index and pinkies favor the bottom rows.
As for punctuations, using the knowledge I have now, I would place them at the corners or middle columns, accessed by the pinkies and index fingers. On my chart, they would be placed on the keys with highest difficulties (2.5 and 3.0, the reddish cells.) Period and comma would go on the top pinky keys (QP on Qwerty, Q; on Colemak, 'L on Dvorak) close to the number keys to facilitate typing arithmetic and monetary values and IP addresses. Then apostrophe and double quotes on separate keys, both unshifted. With these four unwanted corner keys taken care of, proceed with optimizing the other 26 keys for the 26 letters.
DreymaR said:I think that Arensito is a right mess when applied to a standard keyboard! Why that and Asset are still being discussed is a bit beyond me, but I guess they were early contestants in the field. Arensito was made for a matrix board (Maltron I think) and doesn't look bad on that, though.
Arensito has a nice symmetry and intuitiveness at least on the home row. It goes VCVCC from out to in for both hands. Likewise, my layouts tend to go CVVCC from out to in. This symmetry and balance is aesthetically pleasing.
DreymaR said:As for the layout itself, I strongly recommend giving a mild penalty to moving keys from their QWERTY positions if you're making the layout for anyone else than yourself at least – and even for your own good. Punctuation flying all over the layout looks butt ugly, is harder to implement and probably just not worth it.
I don't see why QWERTY has to be favored, especially when you're trying to wean away from it. Another popular camp is Dvorak style: all vowels on one hand, punctuations moved to the top. It really depends on your usage. On your own computer at home or work, you can set up your favorite layout without having to resort back to QWERTY. If you say it makes it easier and faster to transition out of, then again it really depends on how much you still use QWERTY for fast typing. I'm an IT guy who helps others with their computer troubles. Of course they still use QWERTY, but I don't need to type fast when I'm at their computers. I can still look down at the keyboard to remind me where the keys are.
These alternative layouts are for the most part purely theory-crafting on the interaction between humans and keyboards. There would be little progress if we keep trying to tweak QWERTY, instead of starting from scratch and working towards a goal. Dvorak's goal is hand alternation and inward rolls, and the result looks nothing like QWERTY. Colemak's goal is to be like QWERTY but improve on home row, among other things. Workman improves on that using a strain/difficulty model. Some programmers also like to optimize their keyboards for their profession. Yet others try to find the layout that scores the highest based on some contrived, nonstandardized metrics. And other designers may have other goals, such as best layout from genetic algorithms, new physical design like Maltron, air typing or touchpad or smartphone (which BTW I have also worked on http://shenafu.com/smf/index.php?topic=88.0) etc. My own goals include not just metrics, speed, and comfort, but also balance, intuitiveness, and aesthetics.
So if your goal is maximum comfort and least effort, then it makes sense to move every key to their optimal position regardless of how other layouts have done before. Since that's what you're going to use the majority of the time you're at your own keyboard, you should use the layout that feels best for you. Nevertheless, if someone wanted me to recommend them an alternative layout, I'd just show them Dvorak because it's a standard layout that can be configured almost as readily as QWERTY on many devices. Custom layouts that people make are really for the hardcore enthusiasts who are dedicated and have the time and patience to learn a new layout anyway. Of course it would be nice if others picked up your layout, like Colemak. Even though it's touted as being not much different than QWERTY and performs very well on most metrics, however, that's still not enough appeal for the masses and corporations to change from the industry standard. So in that regard, I don't see much value in retaining QWERTY like features. It's an option that looks good on paper, but in itself is not a deal breaker for people looking for the most comfortable layout. (And if you're thinking about functions like copy and paste, etc. then I highly recommend assigning mouse buttons for these functions in this era of GUIs. You could also reassign unused keys like Insert, Delete, etc. so that you rely less on agility while reducing strain due to reaching and holding down Control. Not to mention that one-press copy or paste is so much better and faster.)