[prev in list] [next in list] [prev in thread] [next in thread]
List: webkit-dev
Subject: Re: [webkit-dev] Changes in QtWebKit development
From: Arunprasad Rajkumar <ararunprasad () gmail ! com>
Date: 2013-09-30 14:27:42
Message-ID: CACDxuFzXbGNvWrmiqq7ZZautnAXb6mZuisjn0KSR+07nf=F8DA () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
"New XML parser" was removed from the tree [1].
[1] https://lists.webkit.org/pipermail/webkit-dev/2012-August/022103.html
http://trac.webkit.org/changeset/140399
On 30 September 2013 19:18, Konstantin Tokarev <annulen@yandex.ru> wrote:
>
>
> 30.09.2013, 17:39, "Dirk Schulze" <krit@webkit.org>:
> > On Sep 30, 2013, at 11:58 AM, Allan Sandfeld Jensen <kde@carewolf.com>
> wrote:
> >
> >> On Thursday 26 September 2013, Andreas Kling wrote:
> >>> On Sep 25, 2013, at 12:40 PM, Allan Sandfeld Jensen <kde@carewolf.com
> >
> >> wrote:
> >>>> On Saturday 14 September 2013, Andreas Kling wrote:
> >>>>> On Sep 14, 2013, at 11:24 AM, Allan Sandfeld Jensen <
> kde@carewolf.com>
> >>>> wrote:
> >>>>>> That said, in all likelihood the Qt port will not remain part of
> WebKit
> >>>>>> forever, ...
> >>>>> (This being the main reason.)
> >>>>>
> >>>>> Since you already know you’re eventually going to leave, you could
> just
> >>>>> move to a branch sooner rather than later. It’s unreasonable to
> expect
> >>>>> WebKit to accommodate a port that has no forward-looking interest
> in the
> >>>>> project.
> >>>> We do have a branch tagged and being prepared for 5.2. It was taken
> >>>> before the FTL merge and the following switch to require C++11 in
> all of
> >>>> the project. It will be very hard branch again after that point
> since we
> >>>> support 2-3 year old platforms by default, and the Webkit project
> want
> >>>> to move to using the latest and greatest compilers.
> >>> So you are saying that you'll never branch QtWebKit from WebKit trunk
> >>> again?
> >> I would love to, but I do not think it is going to happen. Quite
> honestly I
> >> wasn't sure I would be able to pull a new branch for 5.2 off, since
> older
> >> Linux (gcc 4.4), all windows builds and especially old OS X (10.6)
> were not
> >> building WebKit2 when I started. I got it working, but it the work to
> unroll
> >> unnecessary compiler features and library dependencies is just going
> to get
> >> harder from now on (if anyone want a patch to remove the C++11
> requirement
> >> from WebKit2 late July, I have one). If a new branch is made from
> WebKit
> >> trunk in the future would likely only be limited to specific
> platforms, and
> >> therefore not suited as a module shipped with Qt, but as an optional
> upgrade.
> >>> It’s commendable that you want to land your platform-agnostic patches
> >>> before withdrawing from the project, but assuming your last branch
> point
> >>> is already set, I don’t see why this necessitates keeping the Qt
> platform
> >>> code around.
> >> We all know what happens when a webkit port works on a branch. In
> theory it
> >> shouldn't be a problem, but as you know it didn't work for the N9
> browser
> >> branch in Nokia, it didn't even work for the iOS branch at Apple!
> >>
> >> So based on observations, I believe to be part of the project and able
> to
> >> commit upstream you must live upstream.
> >
> > I would not necessarily disagree with the problem of upstreaming work.
> But you said that most likely you wouldn't be able to branch WebKit anymore
> because of the compiler requirement. At least for Qt. Do you have other
> interests in QtWebKit beside the integral part of Qt so that it makes sense
> for you to maintain the port further?
> >
> > Another question that is just partly related to WebKit but more
> curiosity. Qt is deep integration into WebKit. We have (had?) a lot of Qt
> specific code in core WebCore to support QtXML and other things. Blink
> already stated that they would not accept such deep interventions in their
> platform. Is all that not important for you anymore? Can you operate with
> libxml2 and other libraries from now on? If that is the case, can't we
> limit the Qt specific code to just /platform/qt and remove all other Qt
> specific dependencies from WebCore?
>
> For embedded targets libxml2 would be an additional dependency to build,
> and it would take additional space in device firmware. New XML parser from
> [1] would be better alternative if it was finished (and had decent
> performance).
>
> [1] https://bugs.webkit.org/show_bug.cgi?id=64396
>
> --
> Regards,
> Konstantin
> _______________________________________________
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-dev
>
--
*Arunprasad Rajkumar*
http://in.linkedin.com/in/ararunprasad
[Attachment #5 (text/html)]
<div dir="ltr">"New XML parser" was removed from the tree \
[1].<div><br></div><div>[1] <a \
href="https://lists.webkit.org/pipermail/webkit-dev/2012-August/022103.html">https://lists.webkit.org/pipermail/webkit-dev/2012-August/022103.html</a><br>
</div><div><br></div><div><a \
href="http://trac.webkit.org/changeset/140399">http://trac.webkit.org/changeset/140399</a><br></div></div><div \
class="gmail_extra"><br><br><div class="gmail_quote">On 30 September 2013 19:18, \
Konstantin Tokarev <span dir="ltr"><<a href="mailto:annulen@yandex.ru" \
target="_blank">annulen@yandex.ru</a>></span> wrote:<br> <blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><br> <br>
30.09.2013, 17:39, "Dirk Schulze" <<a \
href="mailto:krit@webkit.org">krit@webkit.org</a>>:<br> <div><div class="h5">> \
On Sep 30, 2013, at 11:58 AM, Allan Sandfeld Jensen <<a \
href="mailto:kde@carewolf.com">kde@carewolf.com</a>> wrote:<br> ><br>
>> On Thursday 26 September 2013, Andreas Kling wrote:<br>
>>> On Sep 25, 2013, at 12:40 PM, Allan Sandfeld Jensen <<a \
href="mailto:kde@carewolf.com">kde@carewolf.com</a>><br> >> wrote:<br>
>>>> On Saturday 14 September 2013, Andreas Kling wrote:<br>
>>>>> On Sep 14, 2013, at 11:24 AM, Allan Sandfeld Jensen <<a \
href="mailto:kde@carewolf.com">kde@carewolf.com</a>><br> >>>> \
wrote:<br> >>>>>> That said, in all likelihood the Qt port will \
not remain part of WebKit<br> >>>>>> forever, ...<br>
>>>>> (This being the main reason.)<br>
>>>>><br>
>>>>> Since you already know you’re eventually going to leave, you \
could just<br> >>>>> move to a branch sooner rather than later. It’s \
unreasonable to expect<br> >>>>> WebKit to accommodate a port that \
has no forward-looking interest in the<br> >>>>> project.<br>
>>>> We do have a branch tagged and being prepared for 5.2. It was \
taken<br> >>>> before the FTL merge and the following switch to require \
C++11 in all of<br> >>>> the project. It will be very hard branch again \
after that point since we<br> >>>> support 2-3 year old platforms by \
default, and the Webkit project want<br> >>>> to move to using the \
latest and greatest compilers.<br> >>> So you are saying that you'll \
never branch QtWebKit from WebKit trunk<br> >>> again?<br>
>> I would love to, but I do not think it is going to happen. Quite honestly \
I<br> >> wasn't sure I would be able to pull a new branch for 5.2 off, \
since older<br> >> Linux (gcc 4.4), all windows builds and especially old OS X \
(10.6) were not<br> >> building WebKit2 when I started. I got it working, but \
it the work to unroll<br> >> unnecessary compiler features and library \
dependencies is just going to get<br> >> harder from now on (if anyone want a \
patch to remove the C++11 requirement<br> >> from WebKit2 late July, I have \
one). If a new branch is made from WebKit<br> >> trunk in the future would \
likely only be limited to specific platforms, and<br> >> therefore not suited \
as a module shipped with Qt, but as an optional upgrade.<br> >>> It’s \
commendable that you want to land your platform-agnostic patches<br> >>> \
before withdrawing from the project, but assuming your last branch point<br> \
>>> is already set, I don’t see why this necessitates keeping the Qt \
platform<br> >>> code around.<br>
>> We all know what happens when a webkit port works on a branch. In theory \
it<br> >> shouldn't be a problem, but as you know it didn't work for \
the N9 browser<br> >> branch in Nokia, it didn't even work for the iOS \
branch at Apple!<br> >><br>
>> So based on observations, I believe to be part of the project and able \
to<br> >> commit upstream you must live upstream.<br>
><br>
> I would not necessarily disagree with the problem of upstreaming work. But you \
said that most likely you wouldn't be able to branch WebKit anymore because of \
the compiler requirement. At least for Qt. Do you have other interests in QtWebKit \
beside the integral part of Qt so that it makes sense for you to maintain the port \
further?<br>
><br>
> Another question that is just partly related to WebKit but more curiosity. Qt \
is deep integration into WebKit. We have (had?) a lot of Qt specific code in core \
WebCore to support QtXML and other things. Blink already stated that they would not \
accept such deep interventions in their platform. Is all that not important for you \
anymore? Can you operate with libxml2 and other libraries from now on? If that is the \
case, can't we limit the Qt specific code to just /platform/qt and remove all \
other Qt specific dependencies from WebCore?<br>
<br>
</div></div>For embedded targets libxml2 would be an additional dependency to build, \
and it would take additional space in device firmware. New XML parser from [1] would \
be better alternative if it was finished (and had decent performance).<br>
<br>
[1] <a href="https://bugs.webkit.org/show_bug.cgi?id=64396" \
target="_blank">https://bugs.webkit.org/show_bug.cgi?id=64396</a><br> <span \
class="HOEnZb"><font color="#888888"><br>
--<br>
Regards,<br>
Konstantin<br>
</font></span><div class="HOEnZb"><div \
class="h5">_______________________________________________<br> webkit-dev mailing \
list<br> <a href="mailto:webkit-dev@lists.webkit.org">webkit-dev@lists.webkit.org</a><br>
<a href="https://lists.webkit.org/mailman/listinfo/webkit-dev" \
target="_blank">https://lists.webkit.org/mailman/listinfo/webkit-dev</a><br> \
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- \
<br><div><b><font size="4" face="arial, helvetica, sans-serif">Arunprasad \
Rajkumar</font></b></div><div><span \
style="color:rgb(51,51,51);font-family:Arial,Helvetica,'Nimbus Sans \
L',sans-serif;font-size:13px;line-height:15px;background-color:rgb(255,255,255)"><a \
href="http://in.linkedin.com/in/ararunprasad" title="View public profile" \
name="SafeHtmlFilter_SafeHtmlFilter_webProfileURL" \
style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;padding-top:0 \
px;padding-right:0px;padding-bottom:0px;padding-left:0px;border-top-width:0px;border-r \
ight-width:0px;border-bottom-width:0px;border-left-width:0px;border-style:initial;bord \
er-color:initial;outline-width:initial;outline-style:none;outline-color:initial;font-s \
tyle:inherit;font-size:13px;font-family:inherit;vertical-align:baseline;text-decoration:none;color:rgb(0,102,153)" \
target="_blank">http://in.linkedin.com/in/ararunprasad</a></span></div>
</div>
_______________________________________________
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic