[webkit-dev] Updating HTML Gamepad support

[Brady Eidson]

Just had this idea:

I think I’ll start with a patch that renames “GAMEPAD” to “GAMEPAD_DEPRECATED”, along with some file renames.

That way the new implementation can be landed completely independently of the old one, and EFL can choose when to switch over (probably after the new version is done).

From this point on, I’ll lay out plans in the bugzilla https://bugs.webkit.org/show_bug.cgi?id=134076

Thanks,
~Brady


> On Jun 20, 2014, at 9:57 AM, Brady Eidson <beidson at apple.com> wrote:
> 
> 
>> On Jun 19, 2014, at 7:29 PM, KwangHyuk Kim <hyuki.kim at samsung.com> wrote:
>> 
>> Dear Brady Eidson,
>>  
>> > - Only EFL and GTK have Gamepad support code
>> > - The code only supports in-process WebKit1
>> > - GTK has it disabled
>> > - EFL has it enabled, but has also committed to dropping WK1 support
>>  
>> AFAIK, WK2-EFL is also supporting Gamepad api for now.
> 
> Since there was no Gamepad code in the WK2 directory, I assumed this was not the case.
> 
> If EFL’s WK2 strategy is “have every web content process probe the same game pads independent of each other,” then hopefully the upcoming work to set up a proper process model will excite you!
> 
>> However, I would like to say that EFL are now interested in your task too. :)
> 
> Great!
> 
> As far as getting device state from the native gamepad system, I’m sure it will be as easy to adapt to the new model as it was to write GamepadsEfL.cpp.
> 
> The new API does include notifications for connecting and disconnecting gamepads so an EFL maintaining will have to come along and fill in those bits, but it should be pretty straightforward.
> 
> Thanks,
> ~Brady
> 
> 
>> 
> 
>>  
>> BR
>>  - Kwang
>>  
>> ------- Original Message -------
>> Sender : Brady Eidson<beidson at apple.com>
>> Date : 2014-06-20 06:52 (GMT+09:00)
>> Title : [webkit-dev] Updating HTML Gamepad support
>>  
>> Hi all, 
>> 
>> As a pet project I’ve been pecking away at supporting the Gamepad API on Mac.  You can follow along in https://bugs.webkit.org/show_bug.cgi?id=134076.
>> 
>> The first glaring thing I noticed is how out of date the current code is.  The Gamepad code currently in the tree has gone over 3 years without any real development.
>> 
>> In the meantime the working draft for the Gamepad API [1] is much different than what’s in our tree.  Also at least 1 other engine (Mozilla) has shipped support matching the newer API.
>> 
>> I plan to completely break what’s currently in the tree in a non-backwards compatible way.  Grep’ing the tree I conclude that this is okay because:
>> 
>> - Only EFL and GTK have Gamepad support code
>> - The code only supports in-process WebKit1
>> - GTK has it disabled
>> - EFL has it enabled, but has also committed to dropping WK1 support
>> 
>> If I am wrong and somebody has a compelling reason to keep supporting the version of the API that exists in the tree today, please contact me here or in the bugzilla.  *SOON*.
>> 
>> Thanks!
>> ~Brady
>> 
>> [1] - http://www.w3.org/TR/gamepad/
>> 
>>  
>> <201406201129561_XOK0LK7C.gif>
> 
> _______________________________________________
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-dev/attachments/20140620/cd1baad7/attachment.html>