<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.2.5">
</HEAD>
<BODY>
Well, I try to make keytouch as desktop independent as possible. For example it uses konqueror under KDE and nautilus under GNOME as the filemanager. I didn't know there was an infrastructure for starting the preferred browser, but I would really like to use it (where can I find information about it).<BR>
Maybe you are about point 2, but would it not be great if the desktop environments share the configuration?<BR>
<BR>
- Marvin Raaijmakers<BR>
<BR>
On Tue, 2006-01-31 at 02:17 +0000, Matthew Garrett wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">On Fri, Jan 27, 2006 at 12:21:21PM +0100, Marvin Raaijmakers wrote:</FONT>
<FONT COLOR="#000000">> Please read: <A HREF="http://keytouch.sourceforge.net/desktopenv_cooperate.html">http://keytouch.sourceforge.net/desktopenv_cooperate.html</A></FONT>
<FONT COLOR="#000000">> More information about keytouch can be found at: <A HREF="http://keytouch.sf.net">http://keytouch.sf.net</A></FONT>
<FONT COLOR="#000000">You seem to be trying to solve two problems in one piece of code:</FONT>
<FONT COLOR="#000000">1) Mapping physical scancodes to Linux keycodes</FONT>
<FONT COLOR="#000000">2) Mapping Linux keycodes to session events</FONT>
<FONT COLOR="#000000">The first of these is certainly a cross-desktop issue, and I think the </FONT>
<FONT COLOR="#000000">only sensible solution is to ensure that X keysyms are consistent </FONT>
<FONT COLOR="#000000">everywhere. In the Linux case, the easiest way to ensure that is to </FONT>
<FONT COLOR="#000000">make sure that, wherever possible, the physical scancodes are mapped to </FONT>
<FONT COLOR="#000000">the logical keycodes as described in include/linux/input.h.</FONT>
<FONT COLOR="#000000">However, (2) would appear to be heavily desktop dependent. For instance, </FONT>
<FONT COLOR="#000000">Gnome already has infrastructure to handle the volume being changed. </FONT>
<FONT COLOR="#000000">Keytouch appears to tie it to aumix. There's infrastructure for starting </FONT>
<FONT COLOR="#000000">the preferred web browser. Keytouch doesn't seem to use that.</FONT>
<FONT COLOR="#000000">I think Keytouch would be far better off sticking to (1), and leaving </FONT>
<FONT COLOR="#000000">(2) up to the desktops. As long as they work at the X keysym level, no </FONT>
<FONT COLOR="#000000">configuration is required.</FONT>
<FONT COLOR="#000000">As a suggestion - for laptops, you can use the DMI information to </FONT>
<FONT COLOR="#000000">automatically detect which keymap you need. Check the hotkey-setup </FONT>
<FONT COLOR="#000000">package in Debian or Ubuntu.</FONT>
</PRE>
</BLOCKQUOTE>
</BODY>
</HTML>