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
> 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
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
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
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
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
6 matches
Mail list logo
