unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: joakim@verona.se
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org, raman <raman@google.com>
Subject: Re: Using xwidget to play youtube videos
Date: Wed, 10 Feb 2016 09:03:59 +0100	[thread overview]
Message-ID: <m3pow5f0uo.fsf@exodia.verona.se> (raw)
In-Reply-To: <87fux18p7d.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 10 Feb 2016 09:59:50 +1100")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> raman <raman@google.com> writes:
>
>> Nice! Once the Youtube video starts playing, are you able to send it kbd
>> events from Emacs to cause rewind/forward etc to happen?
>
> I'm not sure.  Joakim?

It's not currently possible to send keyboard events as such at the gtk
level. Although that seemed easy enough to implement, I couldn't make it work
at the time. 

It is posible, though, to use javascript snippets to control the
widget. This is the method that is used to fill textarea components in
the webkit widget with text from Emacs.

This method might also be used to simulate keyboard events in the
widget, here is a link I found:

http://stackoverflow.com/questions/596481/simulate-javascript-key-events



-- 
Joakim Verona



  reply	other threads:[~2016-02-10  8:03 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-09  5:58 Using xwidget to play youtube videos Lars Ingebrigtsen
2016-02-09  9:38 ` joakim
2016-02-09 22:55   ` Lars Ingebrigtsen
2016-02-10 14:14     ` Richard Stallman
2016-02-10 14:41       ` Andreas Schwab
2016-02-11  5:18         ` Marcin Borkowski
2016-02-11  9:51           ` Andreas Schwab
2016-02-11 18:21           ` Richard Stallman
2016-02-21 17:17             ` Nix
2016-02-22  3:56               ` Lars Ingebrigtsen
2016-02-22  9:27                 ` joakim
2016-02-22 16:26                   ` Eli Zaretskii
2016-02-23  1:24                   ` Lars Ingebrigtsen
2016-02-22 16:09                 ` Eli Zaretskii
2016-02-22 18:59                   ` joakim
2016-02-22 18:59                   ` John Wiegley
2016-02-12  3:43           ` Matthew Carter
2016-02-12 13:05             ` Marcin Borkowski
2016-02-13 15:33               ` Richard Stallman
2016-02-14 12:21                 ` Elias Mårtenson
2016-02-14 12:33                   ` Dmitry Gutov
2016-02-14 15:32                     ` Elias Mårtenson
2016-02-15 10:26                   ` Richard Stallman
2016-02-15 10:42                     ` Marcin Borkowski
2016-02-11  3:48       ` Lars Ingebrigtsen
2016-02-11 18:21         ` Richard Stallman
2016-02-11 18:46           ` joakim
2016-02-12 12:34             ` Richard Stallman
2016-02-09 16:31 ` raman
2016-02-09 22:59   ` Lars Ingebrigtsen
2016-02-10  8:03     ` joakim [this message]
2016-02-09 16:51 ` Eli Zaretskii
2016-02-09 23:00   ` Lars Ingebrigtsen

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=m3pow5f0uo.fsf@exodia.verona.se \
    --to=joakim@verona.se \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.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).