unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Third <alan@idiocy.org>
To: raman <raman@google.com>
Cc: Anders Lindgren <andlind@gmail.com>,
	Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: Touch events
Date: Wed, 28 Jun 2017 21:50:27 +0100	[thread overview]
Message-ID: <20170628205027.GA74167@breton.holly.idiocy.org> (raw)
In-Reply-To: <p91fuekb0va.fsf@raman-glaptop2>

On Wed, Jun 28, 2017 at 08:14:33AM -0700, raman wrote:
> Also it would be nice to think ahead and build something that works on
> tablets and phones, AKA keyboardless devices. 
> 
> Emacs on those devices in turn might well offer an interesting
> experimental platform for testing out different touch input mechanisms
> ---  given Emacs' long history of smart completion across different contexts.

I’ve been looking into the Xorg side of touch events and it doesn’t
have built‐in gesture support, so I think I’ll have to code that
myself. I was thinking it could maybe be worth passing the touch
events up to lisp and doing gesture recognition in it. That would, I
think, also allow us to handle touch screen devices better as we
wouldn’t have to rely on mouse emulation.

The downside is that my lisp skills are woeful and on platforms where
touch gestures ARE available, we might end up with differing behaviour
from native apps.

The best of both worlds would be if we’re able to fire off input
events from within lisp code, which would let us transparently emulate
system touch gestures where they’re not available, while still having
access to all touch events. I don’t know if that’s possible.

The other option, I suppose, is to pass gesture events from C, and
also pass the basic touch events to lisp. That might be easier.

I need to build an Xorg dev system and try digging into this stuff.
-- 
Alan Third



  reply	other threads:[~2017-06-28 20:50 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-24  8:53 Touch events Alan Third
2017-06-24  9:33 ` martin rudalics
2017-06-24  9:58   ` Alan Third
2017-06-24 13:18 ` Clément Pit-Claudel
2017-06-24 17:00   ` Lars Ingebrigtsen
2017-06-24 23:22     ` Alan Third
2017-06-24 23:43       ` Clément Pit-Claudel
2017-06-25  0:04         ` Lars Ingebrigtsen
2017-06-25 10:40           ` Alan Third
2017-06-25 16:56             ` Clément Pit-Claudel
2017-06-25 17:04               ` Noam Postavsky
2017-06-25 17:10               ` martin rudalics
2017-06-25 18:09                 ` Clément Pit-Claudel
2017-06-25 19:22         ` Stefan Monnier
2017-06-26 10:08 ` Anders Lindgren
2017-06-26 18:28   ` Alan Third
2017-06-28  8:25     ` John Wiegley
2017-06-28 15:14       ` raman
2017-06-28 20:50         ` Alan Third [this message]
2017-09-03  9:14           ` Alan Third
2017-06-27 20:08   ` Alan Third
2017-06-28  9:40     ` Anders Lindgren
2017-06-28 17:23       ` James Nguyen
2017-06-28 21:06       ` Alan Third

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170628205027.GA74167@breton.holly.idiocy.org \
    --to=alan@idiocy.org \
    --cc=andlind@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=raman@google.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).