KDE browser work team
manyoso at yahoo.com
Thu Jul 2 22:14:30 BST 2009
Re: writing to khtmlrc... The fact that the entire browser config dialog is tied to khtml is not something to gloss over. That is a big part of the browser. Moreover, modifying konq source to use an entirely different config dialog if kpart != khtml strikes me as very bad idea. I can only imagine the confusion and chaos that would generate.
Regardless, a lot of work is involved going down that path. I guess you'd have to start with cataloguing the subset of functionality between khtml and webkit to share same config.
David Faure wrote:
> On Thursday 02 July 2009, Lubos Lunak wrote:
>> Moreover, I don't know Konqueror very well, but could somebody point out how
>> Konqueror is tied to KHTML? I thought Konqueror was mostly a shell that
>> didn't care that much about what the part does.
> Correct. The integration with KHTML is done in generic ways, which allows to
> write other browser kparts - like kwebkitpart.
>> Grepping the sources for KHTML doesn't show anything interesting.
> Correct, konqueror doesn't even link to KHTML.
> Indeed the settings modules write to khtmlrc. It's not that hard to come up
> with a more standardized config file (simply writing to konquerorrc might
> even work, iirc KHTML reads from both khtmlrc and KGlobal::config()),
> or (if other parts have too different settings) to come up with a way to only
> show the config modules that relate to the user-chosen html-part.
> David Faure, faure at kde.org, sponsored by Qt Software @ Nokia to work on KDE,
> Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).
More information about the kde-core-devel