Keysyms: HomePage vs WWW
Hi folks Today I looked at the usage of I32 in symbols/inet and found interesting thing. There are 31 cases where it is used as XF86WWW and 17 cases where it is used as XF86HomePage. Could anyone explain the substantial difference between these 2 keysyms (in the context of desktop)? May be, we could just declare WWW as "deprecated" and switch entirely to HomePage? Or - the other way around? There are more exotic cases for that key, like Search, Finance etc - I guess I'll just leave them as they are. For a moment, at least;) Maniac of unification AKA Sergey ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Keysyms: HomePage vs WWW
Both keys have linux input definitions: ,< excerpt from linux-2.6/include/linux/input.h > | #define KEY_WWW 150 /* AL Internet Browser */ | #define KEY_HOMEPAGE 172 /* AC Home */ ` where AL means Application Launch Button and AC means Application Control. In USB HID, the AL and AC keys are part of the Consumer Page (0xC0). Aplication Launch button Internet Browser is UsageID 196 in that page, Generic GUI Application Control button AC Home is 223. The description for the AL section says: ,< excerpt from Hut1_12.pdf §15.15 > | These controls launch the application that most closely relates in | function to the Usage Name. ` The AC keys section says: ,< excerpt from Hut1_12.pdf §15.16 > | These controls provide shortcuts to software application functions or | provide physical controls that mimic the controls found in a typical GUI | application. Most controls in a GUI are buttons, but others such as | scroll bars or zoom controls might be physically implemented as sliders | or wheels. ` , | AC Home Sel - Load the designated root of a hierarchical set of objects. ` So, if one wants to follow the USB recomendation, XF86WWW should launch one's browser and XF86HomePage should load one's preferred home page if one's browser has focus, should go to the top dir if an info viewer has focus, etc. So, Application Launch keys should point at XF86WWW and GUI-control keys at XF86HomePage. I don't know which is used for. -JimC -- James Cloos <[EMAIL PROTECTED]> OpenPGP: 1024D/ED7DAEA6 ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Keysyms: HomePage vs WWW
James, Thanks for the insightful information - really interesting. Unfortunately, as we all know, XKB is not that smart - it cannot distinguish application launch context from application control context. So a keysym has to be mapped to the keycode unconditionally. My question was: what would be the best XKB mapping for the keycode I32 (the keycode itself does not matter, it is just happen to be used frequently for THAT key). As an option, we could declare 2 shift levels - one for App Launch context (WWW), second for App Control context (HomePage). I just want some consistent approach, you know... Sergey ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Keysyms: HomePage vs WWW
> "Sergey" == Sergey Udaltsov <[EMAIL PROTECTED]> writes: Sergey> Unfortunately, as we all know, XKB ... cannot distinguish Sergey> application launch context from application control context. Apologies for ambiguity. These are two completely different keys at the USB level; it is really the keyboard manufacturer who decides which the key is. If keyboards which use with the kbd driver generate in evdev I'd make be WWW and if they generate when using evdev then HomePage. (I presume the mapping between keycodes/xfree86's when using kbd and keycodes/evdev's or when using evdev is consistant across all keyboards.) Sergey> I just want some consistent approach, you know... I agree with that! -JimC -- James Cloos <[EMAIL PROTECTED]> OpenPGP: 1024D/ED7DAEA6 ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Keysyms: HomePage vs WWW
> If keyboards which use with the kbd driver generate in > evdev I'd make be WWW and if they generate when using evdev > then HomePage. Ghm. How could I find this out without having that particular keyboard in front of me?;) Sergey ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Keysyms: HomePage vs WWW
> "Sergey" == Sergey Udaltsov <[EMAIL PROTECTED]> writes: >> If keyboards which use with the kbd driver generate in >> evdev I'd make be WWW and if they generate when using evdev >> then HomePage. Sergey> Ghm. How could I find this out without having that particular keyboard Sergey> in front of me?;) I suspect WWW is more likely than HomePage. But I see that some of the keyboards have both, often with as HomePage and something else as WWW. And a look through the two drivers and Linux's usb and at kbd drivers didn't make obvious the relationship between evdev codes and what kbd gets from the kernel Maybe the bsd src for converting from usb to their kbd driver might make it easier to predict what code kbd would see from a given usb hid code? -JimC -- James Cloos <[EMAIL PROTECTED]> OpenPGP: 1024D/ED7DAEA6 ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Keysyms: HomePage vs WWW
> I suspect WWW is more likely than HomePage. Yes, I suspect the same thing. That's why I asked. > But I see that some of the keyboards have both, often with as > HomePage and something else as WWW. Yes, for those cases we have to distinguish... > Maybe the bsd src for converting from usb to their kbd driver might make > it easier to predict what code kbd would see from a given usb hid code? Well, I'll try to look at it... Thanks for the idea. Sergey ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Keysyms: HomePage vs WWW
Here I published the keycodes used for WWW and HomePage (and VendorHome, just in case): http://spreadsheets.google.com/ccc?key=pCdLapzoHyYYFYQ5pKV3-QA Another suspect keycode: . May be, we just should state that I32 would be for HomePage, I02 would be for WWW?... Of course, this is only for kbd driver (which is nearly deprecated these days, isn't it?;) Sergey On Mon, Dec 1, 2008 at 9:28 AM, James Cloos <[EMAIL PROTECTED]> wrote: >> "Sergey" == Sergey Udaltsov <[EMAIL PROTECTED]> writes: > >>> If keyboards which use with the kbd driver generate in >>> evdev I'd make be WWW and if they generate when using evdev >>> then HomePage. > > Sergey> Ghm. How could I find this out without having that particular keyboard > Sergey> in front of me?;) > > I suspect WWW is more likely than HomePage. > > But I see that some of the keyboards have both, often with as > HomePage and something else as WWW. > > And a look through the two drivers and Linux's usb and at kbd drivers > didn't make obvious the relationship between evdev codes and what kbd > gets from the kernel > > Maybe the bsd src for converting from usb to their kbd driver might make > it easier to predict what code kbd would see from a given usb hid code? > > -JimC > -- > James Cloos <[EMAIL PROTECTED]> OpenPGP: 1024D/ED7DAEA6 > > > > > ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Keysyms: HomePage vs WWW
Sergey Udaltsov wrote: > Of course, this is only for kbd driver (which is nearly deprecated > these days, isn't it?;) Except on non-Linux systems, where kbd is still used since evdev can't be. -- -Alan Coopersmith- [EMAIL PROTECTED] Sun Microsystems, Inc. - X Window System Engineering ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
