No subject

on iOS.  Perhaps we should focus on merging WebKit2 into trunk and delay
having to worry about running WebCore on multiple interlocking threads.

Adam

--e89a8f2347054984ef04d54e9e08
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Fri, Feb 8, 2013 at 8:19 PM, Maciej Stachowiak <span di=
r=3D"ltr">&lt;<a href=3D"mailto:mjs at apple.com" target=3D"_blank">mjs at apple.=
com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmail=
_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex">

<div style=3D"word-wrap:break-word"><br><div><div class=3D"im"><div>On Feb =
8, 2013, at 2:33 PM, Darin Fisher &lt;<a href=3D"mailto:darin at chromium.org"=
 target=3D"_blank">darin at chromium.org</a>&gt; wrote:</div></div><div class=
=3D"im">

<blockquote type=3D"cite"><div class=3D"gmail_quote"><div>I would recommend=
 minimizing the re-architecture of WebCore as you are in the early stages o=
f upstreaming. =A0It seems like you already have a working port that you co=
uld simply upstream. =A0You could then work with others in the community to=
 introduce new concepts to WebCore with the full disclosure of code as an a=
ide to the process. =A0Another option might be to open source the entire th=
ing as a branch somewhere.<br>

</div></div></blockquote></div><div class=3D"im"><blockquote type=3D"cite">=
<div class=3D"gmail_quote">
<div><br></div><div>After the initial upstreaming or sharing of code is com=
plete, you could then catalog all of the warts. =A0The fact that isMainThre=
ad returns true when called on more than one thread would be one such wart.=
 =A0I can imagine a meta bug tracking all of these warts. =A0This would mak=
e it a lot easier for others to understand the overall change in direction =
needed for WebKit to properly support the iOS port.</div>


</div></blockquote></div></div><div>That&#39;s approximately what we&#39;re=
 planning to do. We are upstreaming incrementally, starting with simple pie=
ces, and documenting issues. The bug that sparked this thread was a relativ=
ely change to isMainThread(), plus a function rename, and we are no longer =
asking for the function rename. It will likely be a dozen line patch touchi=
ng a single mac/ios-specific file.</div>

<div><br></div><div>We&#39;d really like to fully upstream the simpler comp=
onents like WTF (where the changes are all simple and targeted) even if we =
can&#39;t as easily do WebCore (where there may be more complex and controv=
ersial diffs).</div>

</div></blockquote><div><br></div><div style>From what you&#39;ve said, it =
sounds like this issue doesn&#39;t apply to WebKit2 on iOS. =A0Perhaps we s=
hould focus on merging WebKit2 into trunk and delay having to worry about r=
unning WebCore on multiple interlocking threads.</div>

<div style><br></div><div style>Adam</div><div style><br></div></div></div>=
</div>

--e89a8f2347054984ef04d54e9e08--