<div class="gmail_quote">On Thu, Jul 15, 2010 at 11:50 PM, Daniel Drake <span dir="ltr"><<a href="mailto:dsd@laptop.org">dsd@laptop.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi,<br>
<br>
On the XO HS (highschool edition, the one with a more "normal"<br>
keyboard) we're facing some questions about how the F keys should<br>
function, under sugar and GNOME.<br>
<br>
The technicalities are in <a href="http://dev.laptop.org/ticket/10213" target="_blank">http://dev.laptop.org/ticket/10213</a> and here<br>
is a picture of the keyboard:<br>
<a href="http://wiki.laptop.org/go/OLPC_Spanish_Non-membrane_Keyboard" target="_blank">http://wiki.laptop.org/go/OLPC_Spanish_Non-membrane_Keyboard</a><br>
<br></blockquote><div><br></div><div>What's up with the layout? The lowercase letters are gone and that was a fine addition.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Under non-sugar environments (e.g. GNOME), myself and Paul are in<br>
agreement that in order to change brightness and volume, you should<br>
press e.g. Fn+F9 (to decrease brightness).<br>
<br>
This matches behaviour of "normal" laptops, including the Dell that<br>
I'm writing on. Linux already has mechanisms (once through hal, now<br>
through udev) so that when I press Fn+F8 on my Dell, X receives the<br>
"volume down" key press (instead of the Fn+F8 key press), matching<br>
what is printed on the keyboard.<br>
<br>
<br>
We want all of the unmodified F-keys to send the normal F-key events<br>
(we don't want to map them especially). This is for maximum<br>
compatibility with non-sugar environments.<br>
<br>
<br>
For Sugar we have an open question.<br>
The F1-F4 keys have the zoom levels printed on them, and pressing the<br>
keys unmodified will cause the zoom levels to change (because this is<br>
how Sugar is already coded, it responds to the literal F1 keypress).<br>
<br>
The other keys are:<br>
- F5: search/journal<br>
- F6: frame<br>
- F9: brightness down<br>
- F10: brightness up<br>
- F11: volume down<br>
- F12: volume up<br>
<br>
For these other keys, when using Sugar, should the user have to press<br>
the Fn modifier while pressing the key in order to reach the named<br>
function?<br>
<br>
The advantage of not having to press Fn (i.e. the keys would work<br>
unmodified) is that sugar works the way it always has on XO (we retain<br>
consistency with XO-1).<br>
As for the other option, the advantage of requiring Fn is that we gain<br>
consistency between Sugar and GNOME, and between the XO HS and<br>
"normal" laptops (where Fn *is* necessary to reach those alternate<br>
functions). (but we do end up with some confusion with the zoom level<br>
keys,which will continue to work unmodified)<br>
<br></blockquote><div><br></div><div>Since on the XO-1 & 1.5 the keys don't have the F numbering print, it seems to me a good idea to have <i>all</i> OLPCs running the modified keys by default, even in GNOME, and having Fn change it to F keys. This bring some advantages:</div>
<div><ul><li>XO 1.5 currently has no way of accessing F keys that are mapped for functions(at least that I know of), which is a problem.</li><li>XO 1 would now be able to run other desktop environments and have the F keys available</li>
<li>Consistent "by design" - although it has become the norm for the Fn key to modify to non F keys, it makes more sense to have to press the Fn key to get an F key output, just like we press shift to get the alternate keycode.</li>
<li>Consistent with Apple and newer laptops</li></ul></div><div>Although this may break usability at first, new users may quickly realize that while the zoom keys don't do anything, the volume and brightness ones do and that may suggest them to press Fn to check the F key functions on the zoom keys when the F1 keycode will expose the GNOME help, suggesting a normal behavior.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
If we decide to make the keys available unmodified in Sugar we would<br>
have to change sugar (worldwide, not interested in downstream forked<br>
patches) so that F5 on any system opens the journal, F6 on any system<br>
opens the frame, etc. How would people feel about that?<br></blockquote><div><br></div><div>Ideally if you could check the keyboard at boot and make the changes, it would be better. Can you?</div><div><br></div><div>Best regards,</div>
<div>Tiago</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
cheers,<br>
<font color="#888888">Daniel<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
Devel mailing list<br>
<a href="mailto:Devel@lists.laptop.org">Devel@lists.laptop.org</a><br>
<a href="http://lists.laptop.org/listinfo/devel" target="_blank">http://lists.laptop.org/listinfo/devel</a><br>
</div></div></blockquote></div><br>