incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jesse MacFadyen <purplecabb...@gmail.com>
Subject Re: Keypress Refactoring
Date Tue, 14 Aug 2012 18:09:11 GMT
WP only has a back button that is overridable.

Cheers,
  Jesse


On 2012-08-14, at 10:56 AM, Brian LeRoux <b@brian.io> wrote:

> I like the idea of a lower level API for meeting the use case and
> providing the opportunity for a higher level polyfill.
>
> Seems like a mapping file would be unwieldy and should be in the
> user-space plugin land. The issue here, of course, is that we'll need
> to document these edges and I think that might be just as messy.
>
> Curious what the other platforms are experiencing with this. Windows
> Phone certainly has some weird buttons. BlackBerry too.
>
>
> On Tue, Aug 14, 2012 at 10:35 AM, Joe Bowser <bowserj@gmail.com> wrote:
>> Hey
>>
>> So, after going through the 2.1 keypress issue, it's clear that
>> there's certain buttons that just don't map to Javascript Events.  In
>> addition, the Android KeyCode mapping is totally different than the
>> WebKit KeyCode mapping, which leaves me with the following options:
>>
>> 1. Carry around a giant mapping file and arbitrarily map certain keys
>> (Gamepad on Xperia Play, Play/Pause/FastFwd) to existing keys
>> 2. Fire a custom key event for the Android Platform and let the user
>> figure out the key events
>>
>> I'm thinking the latter, since I don't think that having a giant JSON
>> mapping file is maintainable, nor is something that we want to do.
>> There may be other platforms (i.e. Windows 8) that also have these
>> issues, and there may be APIs in the future to help with this (GamePad
>> API), but right now it'd be good to give people some way of handling
>> these key events in Javascript.
>>
>> Thoughts??
>>
>> Joe

Mime
View raw message