Saber
Advanced Member
- Joined
- Jan 23, 2012
- Messages
- 1,303
Reply to post from Saber in The official news thead.
I don't want to turn that thread into another keyboard discussion, so I'm importing it here. I'll cross-link with a reply there to this post.
The problem with your layout is not that people haven't heard your rationale, they just don't agree with it. Repeating it over and over again is not going to fix that, it will only annoy people.No, it has functionality issues to it. I've posted some needed changes here but I'll reiterate them anyways for the readers.
You have a couple of points, so I'll address them here.
Junk? That's a selfish thing to say. Depends on usage patterns. I don't care about ° § but I do like the availability of €.Junk symbols ° § € at significantly reachable positions while these ] } \ | are pushed away to and past the middle. No need to clone everything from a full-size German PC keyboard.
I agree with this one. They are out of order and neither of them is in a harder to reach position so frequency of use does not really play a role here._ - = + are weirdly placed. If you, and it seems so, are imitating strictly U.S. symbol pairups then they shouldn't be arranged reversed like that.
Don't worry, looping is easily software controlled. Is brightness changing something you do so frequently that the combination of it should be super easy? For me it is fairly boolean (indoor minimum brightness, outdoor maximum brightness). I think that moving it just makes more important buttons harder to reach.Brightness controls for screen and key backlighting, on one button, on the same side as the keyboard modifiers to use them. Please no looping.
Software controllable. I would recommend the keyboard shift to be sticky by default.Is the keyboard Shift going to be a sticky key? It should be since ( and ) are unwieldy to reach without the L1 shoulder.
One of the aspects that people liked according to the polls was that shifted values were one row above the non shifted values on the Fn layer (i.e. DOSbox "cheat-sheet").All these are much more reachable: { } [ ] \ | _ - + =.
You break this principle with / and ? and you reverse the direction for -_ and =+.
While I agree with the principle, I rather have them paired then not having a Print screen button.Removed Print Screen on Escape, which shouldn't like Enter have any modifier value.
I think sacrificing a comfortable shift+usr and Fn+shift+usr is worse than sacrificing a comfortable shift+brightness and shift+fn+brightness (see above).All brightness controls still reluctantly on one key but now easily accessible with the keyboard Fn. It's no longer clumsy to change brightness, which people tend to like to do sometimes.
While this improves things, I've also further pushed in the private layout discussion most of you are unaware of to move all brightness controls to keyboard-only Fn + Dpad, with Fn + Up or Down for display, and Fn + Left or Right for key backlighting.
Fn + dpad combinations is a bad choice because it is very likely to accidentally press that while gaming. You could utilize a keyboard-fn combination only, but that is rather confusing. In general it is not obvious without very ugly labeling around the dpad to easily communicate brightness changes on the DPAD.
Personally, I wouldn't mind the brightness key to be another modifier (e.g. HW modifier). That way the brightness key + dpad would change brightness and perhaps other hardware combinations such as "brightness" + W for WiFi, "brightness" + B for Bluetooth, etc.. Obviously it shouldn't be called brightness then. Previously I suggested these to be on the super layer.
Personally, I wouldn't mind the brightness key to be another modifier (e.g. HW modifier). That way the brightness key + dpad would change brightness and perhaps other hardware combinations such as "brightness" + W for WiFi, "brightness" + B for Bluetooth, etc.. Obviously it shouldn't be called brightness then. Previously I suggested these to be on the super layer.
I thought if we are going to do the whole French "thang", we might as well do it all. For myself, I'd remove all of those vowels and use dead diacritics, which is what ED originally intended to do before the poll.
Print Screen or whatever can be remapped to the User key. Escape is just one of those keys you don't want to annoy.
How the brightness controls and backlight will be handled on the Pyra now is awful. No way to backtrack with display brightness, which will probably have more than two settings, is like going back in time in interface years. That you can't even use the Shift with it to reverse the display's illumination is just imbecile. People suggested this same thing before and it got shot down to swiss cheese, but now it's suddenly brilliant and new-age.
I don't care if we have ë and ï but I put them there for completism. Same for ñ, although several members here asked for it.They are out of order for a reason though: it makes + and - closer to one another (on Fn+S and Fn+X).I agree with this one. They are out of order and neither of them is in a harder to reach position so frequency of use does not really play a role here._ - = + are weirdly placed. If you, and it seems so, are imitating strictly U.S. symbol pairups then they shouldn't be arranged reversed like that.
If you would put them in the "correct" order while respecting the shift-pair convention, you would end up with + and - on Fn+D and Fn+Z, which means the distance between + and - would be larger.
In Saber's proposal, + and - are also close, but his proposal does not respect the shift-pair convention. If you're not going to have a shift-pair convention, then you can just as well put + as a neighbor of - on the same row, e.g. on Fn+A and Fn+S.
Other comments on Saber's proposal:
- ë and ï are overkill, these letters are rare in any language and no standard keyboard has them, so having ¨ on Shift+^ (like on a French keyboard) is good enough
- If you really want to cover French: you're still missing ù and œ
- ñ for Spanish is nice, but according to this source, ñ only has a frequency of 0.311% in Spanish, while ã has a frequency of 0.733% in Portuguese. So I'm not sure if we really need ñ; the Portuguese keyboard has ~ as a dead diacritic and that's it.
- The caron on Shift+^ looks nice and symmetric, but it makes limited sense from the point of view of languages. For example, why have a caron (only used in Czech, Slovak, Slovenian, Letvian and Serbo-Croatian), but not an ogonek (used in Polish) ?
- Why F11/F12 to the left of User? Is there any reason not to put F11/F12 as far to the right as possible, to get it as close as possible to its expected position?
- Why are é and è reversed? There is no reason to do that: on a standard AZERTY keyboard the order is é è, and also é is more frequent
- While § is probably indeed not very useful, a lot of people like to have €, and I think ° is quite useful: it's used for all kinds of degrees (temperatures, arcs, coordinates on earth, alcohol content etc), and also (though the symbol is actually slightly different) as an ordinal indicator, e.g. 1°, 2°, 3° as abbreviations for primo, secundo, tertio.
- I don't understand the Shifted Shift symbol
- PrintScreen is nice to have.
You said something different before to ED about degree which was "what do we need it for, temperatures?". Compose +oo creates it and Compose +so or os gives us Section Sign.
You are correct about the order of é è.
Shifted Shift symbol wasn't meant for the official label. Figured it was understood as Sticky Shift. We don't need the Shift echo on the label of course.
You can't accept the standard as gospel then reject it when the gloves don't fit. These _ - + = are disoriented and non-standard, and thus break the supreme pattern the authors tried to go for, and use as points against other's layouts which deviate from this rule too for the same reason: the layout doesn't work if we follow conventions.Some valid points there. That is actually a usability reason instead of just an aesthetic one. Convincing enough for me to deviate from "the standard".I want to say that while they appear in strange positions, they will actually be very natural for thumb movement. + and - being in a natural thumb arc from each other, rather than being next to each other horizontally, will be a little bit easier for the thumb to alternate between. It will keep roughly the same "radius" but just adjust the "angle" in °s.
(And they make for some pretty easy code combos in this position, including but not limited to: <= >= += -= /=. You can't beat that with another ordering.)
It is surprisingly hard to poke big holes into the layout. I love it Great work everyone.
It's easy to poke holes in the official layout, if you examine it. The one Shift keyboard key isn't so nice but livable with a sticky Shift. Having ( and ) only available to the shoulder Shift isn't so nice too. The tedious brightness toggles not so either. The tragically wasted positions reserved for those symbols for the smallest occasions, like the three "junk" ones I mentioned, while the coder's tools are put in the middle or closer still to the keyboard Meta which forms them.
These are only some of what I brought up, but, behold the community layout is here now, and I won't "save" you guys from it anymore, so enjoy ED's layout for what actually does work well on it.
Last edited by a moderator: