Linked by Thom Holwerda on Thu 2nd Jul 2009 12:19 UTC
Whenever I use KDE, the part I dislike the most is the rendering engine used by Konqueror, called KHTML. KHTML just doesn't render pages as smooth and as well as Gecko and the KHTML fork WebKit, up to a point where I find Konqueror unusable as a web browser. However, work is underway to replace KHTML in Konqueror with WebKit, but according to KDE developer Adam Treat, this is a futile effort: Konqueror is too KHTML API specific.
Thread beginning with comment 371334
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Sounds like it's time for a new one
by tyrione on Thu 2nd Jul 2009 20:06
in reply to "RE: Sounds like it's time for a new one"
Member since:2005-11-21
Konqueror is much much more than a webbrowser, for better or worse, its more a shell for document viewers. It uses KIO to fetch documents and then KParts to show them in various ways. Meaning I can view a pdf in konqueror as if it were a slimmed down version of okular, the kde document viewer (pdf, dvi, etc). When you click a link to a txt file it opens the text editor/viewer part, same as an image, video, etc etc. While nice in some aspects its really an app that tries to do too much and does none of them especially well.
The best route KDE can go is to go the dolphin route, make an application, that while still highly integrated, is much more web browser centric and tries to be less of a jack of all trades like konqueror.
The best route KDE can go is to go the dolphin route, make an application, that while still highly integrated, is much more web browser centric and tries to be less of a jack of all trades like konqueror.
Safari renders PDF via Preview.app as a Service in OS X. The same goes for images, etc.
There is no reason Qt 4.5/4.6 can't help in the Services department and allow that interaction being lightweight for a non-Konqueror/WebKit compliant browser.
AS you noted, Dolphin is the File Manager. Slow as hell, but the file manager nonetheless.
RE[3]: Sounds like it's time for a new one
by fukudasan on Mon 6th Jul 2009 04:43
in reply to "RE[2]: Sounds like it's time for a new one"
Member since:2006-06-04
Glad I'm not the only one who's noticed the "slowness" of Dolphin - I prefer Konqueror for file browsing any time.
Having said that . . . actions initiated in Dolphin like moving files and stuff execute fast enough, it's just that the UI is so slow, like right-click menus and previews.
Could anyone explain to Mr. Sixpack here in Korea why this is so?
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2006-01-01
Konqueror is much much more than a webbrowser, for better or worse, its more a shell for document viewers. It uses KIO to fetch documents and then KParts to show them in various ways. Meaning I can view a pdf in konqueror as if it were a slimmed down version of okular, the kde document viewer (pdf, dvi, etc). When you click a link to a txt file it opens the text editor/viewer part, same as an image, video, etc etc. While nice in some aspects its really an app that tries to do too much and does none of them especially well.
The best route KDE can go is to go the dolphin route, make an application, that while still highly integrated, is much more web browser centric and tries to be less of a jack of all trades like konqueror.