[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:37:17
Message-ID: 200907021537.17508.aseigo () kde ! org
[Download RAW message or body]


On Wednesday 01 July 2009, Harri Porten wrote:
> Why suppress the freedom of the people writing the code for the Remember
> The Milk plamoid then?

i reject the formation of your question in terms of freedom suppression. let's 
keep this discussion about the facts, and here are the facts regarding that 
email you linked to:

* the context of that email is the Plasma desktop shell
* use of  KHTML currently results in instability there due to crashes in KHTML 
when used there
* using KHTML means loading two whole web rendering stacks (the other being 
WebKit) into memory; that's a little sub-optimal, wouldn't you say?

now, RTM needs to use KHTML right now because:

* QtWebKit does not yet offer DOM API and there is no WebKit <-> KIO 
integration (e.g. via the cookiejar) that it needs for its html authentication 
(which just displays part of a web page directly)

until QtWebKit gets DOM API and we have KDE integration for it, RTM will 
almost certainly continue to use KHTML. no freedom  suppression there, it's 
the pragmatic but in some ways suboptimal solution for this particular context 
(Plasma).

-- 
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]