[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: KDE browser work team
From:       "Aaron J. Seigo" <aseigo () kde ! org>
Date:       2009-07-02 21:52:14
Message-ID: 200907021552.14888.aseigo () kde ! org
[Download RAW message or body]


On Thursday 02 July 2009, David Faure wrote:
> 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.

the implementation in playground/libs/webkitkde/kdewebkit/settings/ already 
pulls from khtmlrc.

however, it probably makes sense that different engines will indeed offer 
different options and capabilities and so should be able to define which kcm's 
to load for them.

kdewebkit and khtml could continue to share options as is currently 
implemented, and kdewebkit could either implement it's own config dialogs from 
scratch, use some of the khtml specific ones or some reorg of the current ones 
could be done to separate out generic features from engine-specific ones. the 
latter will probably create a confusing spreading out of options for users, 
though. and config dialogs aren't that hard to make :)

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Qt Software

["signature.asc" (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]