Gecko/Webkit KDE browser
Registered Member 
|
From what I see in the khtml commits, there is a trend to merge webkit (webcore) back to khtml. First SVG, then CSS3, then web fonts, then Acid 3 code and there is Google summer project to support WYSIWYG editors in khtml. Moreover, there is basic support for video and audio HTML5 tags. All these technology are coming from webkit. It is matter of time before all good features in webkit be in the KHTML.
|
|
Registered Member
|
So what exactly is the point of having KHTML again? Aside from KDE integration, which is apparently fixable. |
|
Registered Member
|
The answer is: 1-There is no developer interests to fix webkitpart and bring to work without major problem. Everyone interests in webkit reinvent the wheel and create new browser from scratch. 2- We can not remove KHTML from kdelibs in KDE 4 series due BIC. KHTML was ready for KDE 4.0 while Qtwebkit was not. 3- html engine is not sexy as plasma things and firefox is there, so why do kde developers bother themselves in that **** thing ? Moreover, we have some monkeys there working in html engine, so we can sleep peacefully. In short answer, khtml will be there till someone stand up and provide a good replacement of it. |
Registered Member
|
i have noticed that disabling javascript speeds up konqueror browsing a great deal. then what really needs to be improved is kjs, right? because with javascript disabled for me konqueror renders websites faster than any other browser.
|
Moderator
|
I don't know about KJS, but for me nsplugin is the "devil"  .If you go to a flash heavy site your CPU goes sky-high, at least for me. I would really like to see a better solution for Flash. In this department WebKit is better.
Primoz, proud to be a member of KDE forums since 2008-Nov.
|
Registered Member
|
I agree that KHTML has still few error and issue of sites not working but the main problem of KDE's default browser lies in it user interface things such as tabs, menus, address bar and other UI things...
Ujjwol, proud user of KDE 4 and member of KDE forums since 2008-Oct.
|
Registered Member
|
The Konqueror UI is great! Much better than FF imho. I really don't know what you are complaining about.
Last edited by blueget on Sun May 31, 2009 4:51 pm, edited 1 time in total.
sidux
|
Registered Member
|
wow! i ve just disabled javascript and konqueror is the faster browser i ve ever seen
Last edited by Dimitrios on Wed Jun 10, 2009 8:08 am, edited 1 time in total.
|
Registered Member
|
All the other major browsers seem to have completely re-written their JS engines. Maybe it's time for KJS to get more then just a facelift...?
Though, then you'd also have to find developers willing to work on it, or for current developers to spend a lot of time on it (because, again, they are few and far between). Still, I find Konqueror to be a very good browser even now: it's already faster then the latest Firefox and seems to get improved every update. In fact, stable Konqueror does better in acid3 then stable Firefox (which just **** me off, when companies like Google make websites that only work in Firefox properly...)
Last edited by Madman on Wed Jun 10, 2009 6:22 pm, edited 1 time in total.
Madman, proud to be a member of KDE forums since 2008-Oct.
|
|
Registered Member
|
Konqueror is actually faster then firefox. Even Youtube loads in a second or so, and the videos work every time now.
Madman, proud to be a member of KDE forums since 2008-Oct.
|
|
Registered Member
|
ELinks is also faster than Firefox. Firefox is still, somehow more usable. |
|
Registered Member
|
Maybe we can also consider coming up with a kick-ass Chromium-based KDE browser? It's a shame Chrome uses GTK.
|
|
KDE Developer
|
Why should the KDE-browser be a clone of another browser with Qt instead of Gtk+? It shouldn't.
Konqueror has great concepts and a good infrastructure. Those features make it better in some aspects. So we should work on the other aspects and not write a new browser without the good ideas of Konqueror. A KDE-Firefox would have slightly better theming, a better file-choose-dialog and better notifications. That's it. When you think about usability you can also use the Gtk+-version. When you want to have a better browser which is also integrated into KDE, use Konqueror. |
|
Registered Member
|
The above is under the assumption, that today's web moves at such a high pace, that it costs an enormous amount of manpower and resources to keep up with it. Mozilla can handle as they have steady income from redirecting searches to google etc. Webkit can handle because they are being backed by Apple and Google. Can KHTML keep it up? I'm not so sure.
That said, I'm not only taking about a QT clone of a GTK app (whereas Chromium is not a GTK app per se, but rather a custom core with GTK widgets for configuration and such). Rather I think that we should incorporate as much as we can from the well supported Chromium project and try to embed it as well as possible into KDE. Clearly, smooth KDE Integration is a superset of using QT. I can only speak for myself, but I wouldn't regard it as a major loss, if the future konqi was a "just" plain web-browser, considering we now have Dolphin for the other tasks. |
|
KDE Developer
|
Of course KHTML and KJS has problems.
There could be something like a KHTML-WebKit merge or whatever. But that wouldn't be a Chromium-port. Maybe the Chromium JS could be integrated. But a new browser upon Chromium or from scratch is the wrong way. You have said something about Dolphin: Use Dolphin when you want to. But KParts and KIO are still great concepts. I for myself use Konqueror as file-manager, PDF-viewer, browser, FTP-client and I use the editor inside Konqueror. These features make KDE-browsers unique. Nobody needs a second xy-browser developed by KDE-developers. But Konqueror with some enhancements from other browsers would be great. |
Bookmarks
Who is online
Registered users: Bing [Bot], gfielding, Google [Bot], Sogou [Bot]
