Re: [webkit-dev] Updating HTML Gamepad support

2014-06-19 Thread KwangHyuk Kim
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.So, I hope that you can

Re: [webkit-dev] Drop EFL WK1 port

2014-06-19 Thread Benjamin Poulain
On 6/19/14, 3:51 AM, Gyuyoung Kim wrote: As discussed on webkit-efl mailing list, we decided to stop EFL WK1 port since we don't use EFL WK1 port anywhere now and future. We will focus on EFL WK2 port. We're going to remove EFL WK1 source code as well as EWS and buildbot for EFL WK1. EFL mailing

[webkit-dev] Updating HTML Gamepad support

2014-06-19 Thread Brady Eidson
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

[webkit-dev] Using W3C test suite as LayoutTests

2014-06-19 Thread youenn fablet
Hi all, I drafted in https://github.com/canonresearchfrance/webkit/wiki/Running-W3C-Tests some thoughts about how to run W3C tests within WebKit, the goal being to improve regression checks and monitor overall W3C conformance.. It contains how to run the W3C tests using the WPT test server throug

Re: [webkit-dev] Drop EFL WK1 port

2014-06-19 Thread Maciej Stachowiak
> On Jun 19, 2014, at 7:07 AM, Darin Adler wrote: > > On Jun 19, 2014, at 5:27 AM, pulkomandy wrote: > >> Should existing WebKit ports that are WK1 based consider switching to WK2? > > Yes. > > WK1 will be around for the foreseeable future because, on both Mac and iOS, > it’s part of the pu

Re: [webkit-dev] Drop EFL WK1 port

2014-06-19 Thread Darin Adler
On Jun 19, 2014, at 5:27 AM, pulkomandy wrote: > Should existing WebKit ports that are WK1 based consider switching to WK2? Yes. WK1 will be around for the foreseeable future because, on both Mac and iOS, it’s part of the public API that developers can use for apps on those platforms. But on

Re: [webkit-dev] Drop EFL WK1 port

2014-06-19 Thread Gyuyoung Kim
Hi, > Who is still supporting it then ? As far as I know, iOS, Mac and Wince(?) ports are still supporting their WK1 port. > Should existing WebKit ports that are WK1 based consider switching to WK2? In my opinion, each port community can decide to support WK1 port continually. Gyuyoung. On

Re: [webkit-dev] Drop EFL WK1 port

2014-06-19 Thread pulkomandy
On Thu, Jun 19, 2014 at 07:51:40PM +0900, Gyuyoung Kim wrote: > Hello WebKittens, > > As discussed on webkit-efl mailing list, we decided to stop EFL WK1 port > since we don't use EFL WK1 port anywhere now and future. We will focus on > EFL WK2 port. We're going to remove EFL WK1 source code as we

[webkit-dev] Drop EFL WK1 port

2014-06-19 Thread Gyuyoung Kim
Hello WebKittens, As discussed on webkit-efl mailing list, we decided to stop EFL WK1 port since we don't use EFL WK1 port anywhere now and future. We will focus on EFL WK2 port. We're going to remove EFL WK1 source code as well as EWS and buildbot for EFL WK1. EFL mailing thread regarding EFL WK