Keyboard mapping capability

madecoste / music-beta-controller

Automatically exported from code.google.com/p/music-beta-controller

0 stars 0 forks source link

Keyboard mapping capability #3

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago

It would be great to have keyboard mappings for the Controller... 
Unfortunately, the Chrome Extensions framework doesn't have any support for 
keyboard mapping (yet?).

There would be a possible workaround by inserting a content script in every 
single page that would have keyboard event listeners, but those would only work 
when the content area has focus and we would need to find keys that don't 
conflict with web content interaction... Not trivial...

Allowing to map to the play/pause and next/prev buttons already present on many 
keyboards would also be excellent (e.g., Macbook Pro keyboard). But it's not 
clear how this can be done in a platform independent way.

Still, it's worth investigating possibilities when someone has time to look 
into it... Patches are welcome! :-)

Original issue reported on code.google.com by mad@chromium.org on 13 May 2011 at 2:10

GoogleCodeExporter commented 9 years ago

Original comment by mad@chromium.org on 30 May 2011 at 3:09

Added labels: Priority-Low
Removed labels: Priority-Medium

GoogleCodeExporter commented 9 years ago

I ported a project that does what you describe (inserts a content script in to 
every page) from amazon cloud to google music, you can see the code at:

https://github.com/bradlambeth/keyGMusic

If you're interested, I could try to create a patch for your project as well.

Original comment by bradlambeth on 1 Jun 2011 at 2:17

GoogleCodeExporter commented 9 years ago

Ho, please do... I would appreciate it!

Original comment by mad@chromium.org on 1 Jun 2011 at 3:58

GoogleCodeExporter commented 9 years ago

Originally I planned to add the shortcuts to each of your controllers, but 
really these shortcuts should be in a common extension to reduce code overlap.  
The shortcuts aren't limited by the browser action icon like your controllers, 
so I ended up simply adding a new extension directory for the shortcuts:

http://code.google.com/r/bradlambeth-music-beta-controller/source/list

Unfortunately, this is essentially an un-stylized version of keyGMusic, so it 
doesn't really add much.  The generic code is there now though if you want to 
add it to your extension(s).

Original comment by bradlambeth on 3 Jun 2011 at 2:21

GoogleCodeExporter commented 9 years ago

Thanks, I'll see if I can do something with it...

I would worry about the skip extension, it's just a separate addition for those 
who prefer to use two buttons, all the functionality should eventually be 
available in the other one anyway...

Original comment by m...@google.com on 7 Jun 2011 at 8:28