On May 14, 2011, at 12:55 PM, ext Oliver Hunt wrote: A common problem the we're hitting when working on JSC is that the Qt bridge bindings are implemented in terms of JSC internals. This keeps causing us problems as no one working on JSC really knows anything about Qt or the API the bridge objects are intended to provide, and yet we are required to keep them running when making significant changes.
Given there seems to be little focus on these bindings from Nokia it seems that the best path forward is to have them rewritten in terms of the JSC API rather than the JSC internals. This will insulate the bindings from future changes and make life a little easier for everyone. I've filed https://bugs.webkit.org/show_bug.cgi?id=60842 to track this change. If during the conversion people find any short comings in the JSC API that's useful too, as it's likely that those problems would impact other users of the JSC API and we would welcome bugs being filed on those them (CC'ing me :) ). Hi folks. I have a couple of long flights this week so I'll pick up the challenge of trying to convert the Qt bridge code to use JSC/API (which is a good flight activity :)) So far from an initial glance the main issue is with exposing internal data-types like ByteArray and HTMLElement; but I'm sure that can be resolved by minor additions to the API. At the very least, I'm confident that we can remove a big chunk of the internal-JSC dependency and leave some at the fringe for until we approve the additions to the API. btw if you open https://trac.webkit.org/wiki/WebKit%20Team, you'll see that the Qt bridge links to my name quite directly. However, this is the first time I've heard about this being a problem for the evolution of JSC, which is of course something we want to resolve. Cheers, No'am
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
