faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
|
Well done KHTML developers
by Zayed on Monday 24/Mar/2008, @02:00
|
| It seem we will get fast and rich features web browser in kde 4.1. Does any one have the score of KHTML (development version) in Acid test version 3 ? what about the javascript benchmark in compare with firefox 3 beta 4? |
|
|
The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: Well done KHTML developers
by djvnklhjefjmwfn on Monday 24/Mar/2008, @05:26
|
Well, if the KHTML developers finally got over their giant ego and already ported WebKit into the KHTML framework, then it's 95/100 points: http://webkit.org/blog/167/webkit-gets-an-a-on-acid3/
|
[
Reply To This | View ]
|
Re: Well done KHTML developers
by xian on Monday 24/Mar/2008, @08:21
|
While I too would like to see webkit used by kde and one common web platform, the khtml developers deserve better treatment. They seem to be helping out all over: http://webkit.org/blog/158/the-acid-3-test/
|
[
Reply To This | View ]
|
Re: Well done KHTML developers
by Anon on Monday 24/Mar/2008, @09:00
|
Yea, took the WebKit crew quite some time to finally include the CSS3 selectors patches by the KHTML developers (they were available for ages, but only with this ACID3 test there was interest from WebKit side to actually incorporate them).
I'm sure once it's easier to compare output of KHTML and WebKit within KDE the stream of merge patches between the two will increase. I just hope the WebKit side will be more forwardcoming in incorporating KHTML improvements then.
|
[
Reply To This | View ]
|
Re: Well done KHTML developers
by eds on Monday 24/Mar/2008, @10:20
|
Agreed, the KHTML developers really deserve better treatment.
Without them, Konqueror in KDE 4.0.x would be unusable as web browser (KHTML crashed too often and rendered pages like ancient browser before they started fixing bugs for KDE 4, and now it is pretty solid). And I'm also sad that some people never appreciate what the KHTML developers have done, especially those who can only yell: "dump KHTML, use Webkit!"
I hope KHTML can remain alive, so that we have an alternative engine inside our own tree. I would also like WebKit to be used by KDE, but I guess having an engine that we have total control would be advantageous.
|
[
Reply To This | View ]
|
Re: Well done KHTML developers
by rdttgukk,fzjkuggh on Monday 24/Mar/2008, @19:00
|
WebKit is free software and can be forked at any time if WebKit's SVN becomes "hostile" towards KDE. But since some KDE and Trolltech developers got SVN write accress hostility is unlikely.
|
[
Reply To This | View ]
|
Re: Well done KHTML developers
by Anon on Sunday 30/Mar/2008, @03:45
|
A fork is no good if you've lost all of your developers.
|
[
Reply To This | View ]
|
Re: Well done KHTML developers
by eds on Monday 24/Mar/2008, @10:26
|
Well, do you think merging two source code trees that have been diverged for years is that simple? KHTML developers always do merging whatever can be merged from Webkit tree but I guess not all are as straightforward as you think. You can always check the websvn to see what have been merged ;)
|
[
Reply To This | View ]
|
|
Re: Well done KHTML developers
by digital.alterego on Monday 24/Mar/2008, @07:08
|
I got 65/100 points with todays svn version.
|
[
Reply To This | View ]
|
Re: Well done KHTML developers
by fred on Monday 24/Mar/2008, @07:17
|
JavaScript performance also has been improved, I, and will be improved further if kjs-frostbyte branch has been merged to trunk.
Nice, kudos to KHTML team!
|
[
Reply To This | View ]
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
|