dependencies on KJS/KHTML in kdelibs and kdebase-runtime

Alexander Neundorf neundorf at
Wed Sep 22 20:21:10 BST 2010

On Wednesday 22 September 2010, Aaron J. Seigo wrote:
> let me state what should be the obvious: i think it is terrific that people
> continue to work on KJS/KHTML and enjoy improving them, release after
> release. i think it is terrific that people continue to use KJS/KHTML with,
> e.g., konqueror.
> now for the perhaps less obvious: that does not mean that the rest of
> kdelibs (or the SC modules, even) need to therefore use KJS and KHTML as
> their defaults. for the world of devices, it just doesn't make sense to do
> so. for the desktop, particularly apps showing app generated HTML content,
> it's probably less of an issue.
> so now the proposal:
> i'd like to propose that we deprecate the usage of KJS / KHTML in kdelibs
> and kdebase/runtime/ with the intention of moving what code does use it to
> QtScript or QtWebKit. both are mature enough to take on this weight, and
> are what we are having to use on devices anyways.

Although I'm not directly involved in the development of either: I think this 
completely makes sense.


More information about the kde-core-devel mailing list