Re: khtml

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: khtml
by MamiyaOtaru on Friday 18/Apr/2008, @13:42

Thank you for this post. I am so tired of hearing that webkit is a panacea. It's controlled by an outside entity, and to get to KDE has to go through another outside entity. There will be lead time for each new version.

There will be issues integrating it into KDE. Anyone who thinks webkit can just be dropped into Qt, much less KDE should read this: http://zecke.blogspot.com/2008/01/joys-of-debugging-webkit.html

I don't link to that to somehow try to prove that webkit in KDE won't work, it's just to show that there are issues getting webkit to work on any platform where it isn't native (pretty much anything but OSX). It's a lot of work getting it working in Qt, never mind KDE.

And yeah, in so many cases it seems like people want the browser string. Thing is, those people don't need a new rendering engine to get the browser string they want. I wish they'd just change it in their copy of Konqueror and stop agitating for webkit. If webkit proves to be superior (including how easy it is to get working and current in KDE) then it will happen, with or without boosterism on the dot.

Related Links

·   Articles on Developer
·   Also by MamiyaOtaru
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )


		"Ahhh, the whole screen feels bigger now." -- Waldo Bastian
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.