Use this tool to learn about websites, specifically the one you just entered.
If you find some aspect of it inappropriate it is not our fault.
If you are the owner of this website: yes we are a real search engine, we do have a real web crawler called FyberSpider and you can block it if you feel the urge.
Is It Cataloged?
We are in the process of updating this tool. Until we are done just use our search results to check the inclusion status of your site.
Find out if your site has been cataloged by top search engines for only $8.99.
Below you will see site info taken directly from the URL you entered in real time. This is also known as our URL Breakdown tool and can be used independently of our site info tool.
Page Title
manyoso's blog kdedevelopers.org
Stripped Text Content
This is just a sample of the content found on this website. Please visit the website to read the entire page.
"Skip navigation .
KDE Developer's Journals
Home ยป Blogs manyoso's blog
A QtWebKit KPart is no answer for a KDE browser
Submitted by manyoso on Wed, 07/01/2009 - 20:13
KDE General
KParts
Disclaimer: I have no desire to re-ignite KHTML vs WebKit arguments. Rather, the purpose of this blog post is to hopefully enlighten a technical question.
Over the last few months I've heard many KDE developers in various forums bemoan the lack of a working and stable WebKit KPart. The motivation behind this complaint seems to be that KDE folk want a WebKit browser option for KDE. Thus the naive solution is to just get the WebKit KDE KPart in shape. Given this motivation... the solution is wrong IMO.
I can speak from some experience here. I've been working on QtWebKit for quite awhile and have also worked - in the past - on the WebKit KPart plus Konqueror integration that Simon started. For a time, it was building and running just fine. You could install it and change a configuration file and Konqueror would render using QtWebKit. However, the integration was *far* from complete. Plumbing the sources of Konqueror I learned a nasty secret: Konqueror is highly KHTML API specific. Konqueror has deep integration with KHTML that goes far above and beyond the KPart API. Creating a QtWebKit KPart is woefully insufficient for the purpose of providing anything more than a basic HTML viewer.
A simple HTML viewer is no where close to a fully modern desktop browser.
This all makes sense if you stop to think about the history of Konqueror. Konqueror is a generic desktop shell. It is designed to allow basic viewing of various documents in various formats. Of cour"
....
read entire page
