From: Peter Hutterer <peter.hutterer@who-t.net>
To: Arjan Opmeer <arjan@opmeer.net>
Cc: Henrik Rydberg <rydberg@euromail.se>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] input: Add a detailed multi-touch finger data report protocol
Date: Tue, 11 Nov 2008 14:13:42 +1000 [thread overview]
Message-ID: <20081111041341.GB6776@dingo.redhat.com> (raw)
In-Reply-To: <20081108112901.GA12987@adopmeer.homeip.net>
On Sat, Nov 08, 2008 at 12:29:02PM +0100, Arjan Opmeer wrote:
> > It is designed to bring advanced gestures to the linux desktop.
>
> Certainly. Have you already thought about the rest of the path from driver
> to application, ie kernel driver -> X.org driver -> X events -> toolkit
> events -> application?
>
> For instance does the X.org driver interpret the data and emit a zoom or
> rotate event based on the finger position and movement? As far as I know
> those event do not exist and would have to be added to X.org as well as the
> toolkits like GTK+ and Qt. It could be a long implementation process... :(
IMHO the server or driver shouldn't do anything with the event but pass it on
to the client. What the events then mean semantically depends on the client
(or the toolkit). This replicates pretty much what we do with mouse events and
although it puts the burden on the client side to do anything useful, it makes
it easier to develop, debug and also to do non-standard interpretation of
gestures.
The X server's job is basically just to pick the right client to send the
events to, and of course augment the events with X specific data (such as the
window).
Cheers,
Peter
next prev parent reply other threads:[~2008-11-11 4:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 11:15 [PATCH] input: Add a detailed multi-touch finger data report protocol Henrik Rydberg
2008-11-07 13:34 ` J.R. Mauro
2008-11-07 14:26 ` Henrik Rydberg
2008-11-07 14:36 ` J.R. Mauro
2008-11-07 14:52 ` Henrik Rydberg
2008-11-07 14:57 ` J.R. Mauro
2008-11-07 15:07 ` Henrik Rydberg
2008-11-11 4:08 ` Peter Hutterer
2008-11-08 0:51 ` Arjan Opmeer
2008-11-08 10:43 ` Henrik Rydberg
2008-11-08 11:29 ` Arjan Opmeer
2008-11-08 12:02 ` Henrik Rydberg
2008-11-11 4:13 ` Peter Hutterer [this message]
2008-11-11 4:20 ` Peter Hutterer
2008-11-11 11:19 ` Henrik Rydberg
2008-11-19 16:37 ` Dmitry Torokhov
2008-11-19 16:54 ` Jim Gettys
2008-11-19 23:34 ` Henrik Rydberg
2008-11-21 14:43 ` Jim Gettys
2008-11-19 23:31 ` Henrik Rydberg
2008-11-21 14:44 ` Henrik Rydberg
2008-11-21 16:04 ` Dmitry Torokhov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081111041341.GB6776@dingo.redhat.com \
--to=peter.hutterer@who-t.net \
--cc=akpm@linux-foundation.org \
--cc=arjan@opmeer.net \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rydberg@euromail.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).