Re: [webkit-dev] Announcing new port: Nix

Hi Anders, On Mon, Sep 23, 2013 at 3:10 PM, Anders Carlsson wrote: > > On 13 sep 2013, at 01:58 em, Hugo Lima wrote: > >> On Fri, Sep 13, 2013 at 4:31 PM, Antonio Gomes wrote: >>> So will you advocate your users to use your external GitHub version or >>> the one in >>> WebKit? >>> >>> Please co

Re: [webkit-dev] Announcing new port: Nix

On 13 sep 2013, at 01:58 em, Hugo Lima wrote: > On Fri, Sep 13, 2013 at 4:31 PM, Antonio Gomes wrote: >> So will you advocate your users to use your external GitHub version or >> the one in >> WebKit? >> >> Please consider not being half upstream. > > It wont be half upstream, but the github

Re: [webkit-dev] Announcing new port: Nix

On Sep 12, 2013, at 1:58 PM, Hugo Lima wrote: > On Thu, Sep 12, 2013 at 4:14 PM, Ryosuke Niwa wrote: >> Interesting. That sounds a lot like Chromium's WebKit API layer. If I >> remember correctly, that layer had to be modified constantly as >> WebCore/WebKit code was refactored so I'm a bit wo

Re: [webkit-dev] Announcing new port: Nix

On Fri, Sep 13, 2013 at 4:31 PM, Antonio Gomes wrote: > So will you advocate your users to use your external GitHub version or > the one in > WebKit? > > Please consider not being half upstream. It wont be half upstream, but the github repository will be for example a fallback for a working bleed

Re: [webkit-dev] Announcing new port: Nix

So will you advocate your users to use your external GitHub version or the one in WebKit? Please consider not being half upstream. On Fri, Sep 13, 2013 at 2:37 PM, Hugo Lima wrote: > On Fri, Sep 13, 2013 at 3:00 PM, Anders Carlsson wrote: >> >> On Sep 12, 2013, at 1:58 PM, Hugo Lima wrote: >>

Re: [webkit-dev] Announcing new port: Nix

On Fri, Sep 13, 2013 at 3:00 PM, Anders Carlsson wrote: > > On Sep 12, 2013, at 1:58 PM, Hugo Lima wrote: > >> On Thu, Sep 12, 2013 at 4:14 PM, Ryosuke Niwa wrote: >>> Interesting. That sounds a lot like Chromium's WebKit API layer. If I >>> remember correctly, that layer had to be modified con

Re: [webkit-dev] Announcing new port: Nix

>> Thank you for this list. I started reading through it, but I noticed a high >> percentage of patches that were port-specific build fixes or port-specific >> features like support for legacy ARM chips. For example, “...on ARM >> traditional” (). Those

Re: [webkit-dev] Announcing new port: Nix

Geoffrey Garen wrote: Sure. We at University of Szeged who work on WebKitNix from this year contributed many fixes to various part of WebKit: JavaScriptCore, WebCore, Tools, … Thank you for this list. I started reading through it, but I noticed a high percentage of patches that were port-spe

Re: [webkit-dev] Announcing new port: Nix

On Thu, Sep 12, 2013 at 5:29 PM, Geoffrey Garen wrote: >> Sure. We at University of Szeged who work on WebKitNix from this year >> contributed many fixes to various part of WebKit: JavaScriptCore, >> WebCore, Tools, … > > Thank you for this list. I started reading through it, but I noticed a high

Re: [webkit-dev] Announcing new port: Nix

On 9/12/13 9:34 PM, Brent Fulgham wrote: However, you've already clarified that you're going to improve WebRTC and are, in fact, in the process of doing so. Furthermore, you've clarified that there is a demand for your port and human resources to maintain it. I'm actually curious if anyone's

Re: [webkit-dev] Announcing new port: Nix

> However, you've already clarified that you're going to improve WebRTC and > are, in fact, in the process of doing so. Furthermore, you've clarified that > there is a demand for your port and human resources to maintain it. > > I'm actually curious if anyone's opposed to supporting Nix port a

Re: [webkit-dev] Announcing new port: Nix

On Thu, Sep 12, 2013 at 11:06 AM, Hugo Lima wrote: > On Thu, Sep 12, 2013 at 2:54 PM, Darin Adler wrote: > > On Sep 12, 2013, at 10:36 AM, Hugo Lima wrote: > > > >> the Nix implementation will just delegate the implementation to the > application > > > > I think what this means is that Nix will

Re: [webkit-dev] Announcing new port: Nix

>> As it was pointed in the first email of this thread and by Hugo's >> email, Nix "targets whoever wants to have a hardware accelerated >> WebKit2 port on UNIX-based devices, with a minimum effort". > > Yes. I read that email. Then I asked who "whoever" was, and the answer was > "nobody". > > My

Re: [webkit-dev] Announcing new port: Nix

On Sep 12, 2013, at 6:38 AM, Thomas Fletcher wrote: > TDLR: Crank Software Supports a NIX port This is a question of maintenance burden. As Geoff said every port adds a cost to developing and maintaining webkit. You've said you support a NIX port, but a quick search doesn't show any contribut

Re: [webkit-dev] Announcing new port: Nix

On Thu, Sep 12, 2013 at 2:54 PM, Darin Adler wrote: > On Sep 12, 2013, at 10:36 AM, Hugo Lima wrote: > >> the Nix implementation will just delegate the implementation to the >> application > > I think what this means is that Nix will export interfaces that closely match > WebKit internals as th

Re: [webkit-dev] Announcing new port: Nix

Benjamin Poulain wrote: On 9/12/13 5:21 PM, Thomas Fletcher wrote: Geoffrey Garen wrote: Sure. We at University of Szeged who work on WebKitNix from this year contributed many fixes to various part of WebKit: JavaScriptCore, WebCore, Tools, ... Thank you for this list. I started reading thr

Re: [webkit-dev] Announcing new port: Nix

On Thu, Sep 12, 2013 at 6:05 PM, Thomas Fletcher wrote: > Benjamin Poulain wrote: > > On 9/12/13 5:21 PM, Thomas Fletcher wrote: > > Geoffrey Garen wrote: > > Sure. We at University of Szeged who work on WebKitNix from this year > contributed many fixes to various part of WebKit: JavaScriptCore, >

Re: [webkit-dev] Announcing new port: Nix

Oliver Hunt wrote: On Sep 12, 2013, at 6:38 AM, Thomas Fletcher wrote: TDLR: Crank Software Supports a NIX port This is a question of maintenance burden. As Geoff said every port adds a cost to developing and maintaining webkit. You've said you support a NIX port, but a quick search does

Re: [webkit-dev] Announcing new port: Nix

On 9/12/13 5:21 PM, Thomas Fletcher wrote: Geoffrey Garen wrote: Sure. We at University of Szeged who work on WebKitNix from this year contributed many fixes to various part of WebKit: JavaScriptCore, WebCore, Tools, ... Thank you for this list. I started reading through it, but I noticed a hi

Re: [webkit-dev] Announcing new port: Nix

On Thu, Sep 12, 2013 at 4:14 PM, Ryosuke Niwa wrote: > Interesting. That sounds a lot like Chromium's WebKit API layer. If I > remember correctly, that layer had to be modified constantly as > WebCore/WebKit code was refactored so I'm a bit worried about this. Yes, in fact we got some API from t

Re: [webkit-dev] Announcing new port: Nix

On Sep 12, 2013, at 10:36 AM, Hugo Lima wrote: > the Nix implementation will just delegate the implementation to the > application I think what this means is that Nix will export interfaces that closely match WebKit internals as the Nix API to WebKit. This may well create a long term problem

Re: [webkit-dev] Announcing new port: Nix

On Thu, Sep 12, 2013 at 1:46 PM, Darin Adler wrote: > In my work on clipboard and pasteboard recently, I started with the Mac port. > The Qt and GTK ports have been easy to work with. Contributors to those ports > have helped me get the details right, and the code for those ports is > relativel

Re: [webkit-dev] Announcing new port: Nix

> However, I am quite happy that people have been working on improving the > libcURL support :-) Thank you Brent. Although many people left, we are still here, and continually improving WebKit. We are serious about it. Regards, Zoltan ___ webkit-dev m

Re: [webkit-dev] Announcing new port: Nix

> Sure. We at University of Szeged who work on WebKitNix from this year > contributed many fixes to various part of WebKit: JavaScriptCore, > WebCore, Tools, … Thank you for this list. I started reading through it, but I noticed a high percentage of patches that were port-specific build fixes or

Re: [webkit-dev] Announcing new port: Nix

In my work on clipboard and pasteboard recently, I started with the Mac port. The Qt and GTK ports have been easy to work with. Contributors to those ports have helped me get the details right, and the code for those ports is relatively self explanatory. The Windows port has been pretty easy, to

Re: [webkit-dev] Announcing new port: Nix

Hi, On 09/12/13, Osztrogonác Csaba wrote: > Improving cURL network backend (which used by Apple's WinCairo port too) > > The WinCairo port is not an Apple project, though it is tied very closely to the existing Apple Windows port. However, I am quite happy that people have been working on im

Re: [webkit-dev] Announcing new port: Nix

Geoffrey Garen wrote: The most recent effort from our side is to provide WebRTC support. Great. Features, like performance improvements and bug fixes, are a great way to contribute to WebKit. As it was pointed in the first email of this thread and by Hugo's email, Nix "targets whoever wan

Re: [webkit-dev] Announcing new port: Nix

Hi, Geoffrey Garen írta: If the NIX port is what gets you guys excited about WebKit, and the end result is a great implementation of WebRTC, that's great. But, six months from now, if the NIX port still has no adopters, and the only activity it brings to WebKit is the occasional rude email fr

Re: [webkit-dev] Announcing new port: Nix

Hi, Geoffrey Garen írta: Does your code fix bugs or improve performance in WebCore or JavaScriptCore? As any other WebKit port WebCore bugs are fixed when we found it and need a fix, our current performance focus is on CoordinatedGraphics and there are another team working on get the can

Re: [webkit-dev] Announcing new port: Nix

On Wed, 2013-09-11 at 17:43 -0300, Luciano Wolf wrote: > The most recent effort from our side is to provide WebRTC support. > Thiago Lacerda is talking with Eric Carlson and they are coordinating > the merge of Blink patches as well as planning the development of > missing features. So, I believe

Re: [webkit-dev] Announcing new port: Nix

> The most recent effort from our side is to provide WebRTC support. Great. Features, like performance improvements and bug fixes, are a great way to contribute to WebKit. > As it was pointed in the first email of this thread and by Hugo's > email, Nix "targets whoever wants to have a hardware

Re: [webkit-dev] Announcing new port: Nix

Hi Geoffrey, As it was pointed in the first email of this thread and by Hugo's email, Nix "targets whoever wants to have a hardware accelerated WebKit2 port on UNIX-based devices, with a minimum effort". During the last Contributors Meeting in San Jose, we've had discussions with Romain Pokrzywka,

Re: [webkit-dev] Announcing new port: Nix

This would be pure win if Qt/Gtk/EFL switched to it - but otherwise it seems like it would add a lot of maintenance burden. Do you also provide the appropriate scaffolding for a Gtk, Qt, or EFL user to use Nix in the same way that they would now use those native ports' views? If you did this,

Re: [webkit-dev] Announcing new port: Nix

What value do you think this port will bring to WebKit? For example: Does your code fix bugs or improve performance in WebCore or JavaScriptCore? Does the simplification you mentioned allow us to remove existing port-related code? You mentioned that EFL, GTK, and/or Qt

Re: [webkit-dev] Announcing new port: Nix

>>Does your code fix bugs or improve performance in WebCore or >> JavaScriptCore? > > As any other WebKit port WebCore bugs are fixed when we found it and > need a fix, our current performance focus is on CoordinatedGraphics > and there are another team working on get the canvas faster.

Re: [webkit-dev] Announcing new port: Nix

Hi On Tue, Sep 10, 2013 at 6:48 PM, Geoffrey Garen wrote: > What value do you think this port will bring to WebKit? For example: > > Does your code fix bugs or improve performance in WebCore or > JavaScriptCore? As any other WebKit port WebCore bugs are fixed when we found it and need a

Re: [webkit-dev] Announcing new port: Nix

The GTK, Qt and EFL ports were originally mentioned in this thread as the ports that could share much of the POSIX- or GLib-specific code. That's as close as they come to the new Nix port which would also use this code. The three ports are heavily tied to their respective toolkits. They could stil

Re: [webkit-dev] Announcing new port: Nix

Hi Luciano, This appears to be a big step forward. I am especially interested in the notion of design freedom you speak of. Looking forward to seeing this upstreamed. enjoy, Karen. On Fri, May 17, 2013 at 09:41:27AM -0300, Luciano Wolf wrote: > The openBossa team at INdT Brazil is proud to announc

Re: [webkit-dev] Announcing new port: Nix

@lists.webkit.org Subject: [webkit-dev] Announcing new port: Nix The openBossa team at INdT Brazil is proud to announce “Nix” - a new WebKit2 port based on POSIX and OpenGL. Nix stands for “WebKit for unix-like platforms” and, if you consider the German meaning of the word "nix", it can be taken

Re: [webkit-dev] Announcing new port: Nix

ebkit-dev@lists.webkit.org Subject: [webkit-dev] Announcing new port: Nix The openBossa team at INdT Brazil is proud to announce “Nix” - a new WebKit2 port based on POSIX and OpenGL. Nix stands for “WebKit for unix-like platforms” and, if you consider the German meaning of the word "nix",

Re: [webkit-dev] Announcing new port: Nix

Excellent! I'm looking forward to see WebKitNix in trunk. -kbalazs On 05/17/2013 02:41 PM, Luciano Wolf wrote: The openBossa team at INdT Brazil is proud to announce “Nix” - a new WebKit2 port based on POSIX and OpenGL. Nix stands for “WebKit for unix-like platforms” and, if you consider the Ge

[webkit-dev] Announcing new port: Nix

The openBossa team at INdT Brazil is proud to announce “Nix” - a new WebKit2 port based on POSIX and OpenGL. Nix stands for “WebKit for unix-like platforms” and, if you consider the German meaning of the word "nix", it can be taken as “WebKit plus nothing”. We are looking forward to upstreaming and