On Fri, Apr 9, 2010 at 2:47 AM, Xan Lopez <x...@gnome.org> wrote: > I suppose I could wait until you land the patches and see by myself, but: > > - In the wiki you mention that one goal of the new framework is to > provide a stable C-based API. Is this meant as a public API for > WebKit, the same in all platforms (like JSC), or a stable internal API > for embedders to use in order to implement their native APIs on top? > From some lines in the wiki (like WKView wrapping native objects) it > seems like you want to do the former, but that seems like quite a > massive effort and the loss of an important selling port of the > various WebKit ports. > > - Does your new framework require any significant changes in WebCore? > Could you briefly summarize them? > > - Do you see valid usecases in the long term for the "traditional" > ports or are your plans to quickly transition all code to the new > system as soon as it's ready? >
Another issue seems to be that parts of the public C API expose CoreFoundation, which definitely would be an issue for the other ports. I'm told on the side that this was just done as a quick solution to have something running and that if there's interest by other ports in using this we'd solve it with the good-old "let's add another abstraction layer" method, right? Xan _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
