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

List:       kde-core-devel
Subject:    Re: KDE browser work team
From:       Adam Treat <manyoso () yahoo ! com>
Date:       2009-07-02 21:03:14
Message-ID: 702794.69244.qm () web34205 ! mail ! mud ! yahoo ! com
[Download RAW message or body]


Yes, I said KHTMLPart API, not KHTML API. The latter was someone else&#39;s \
paraphrase :)

I don&#39;t anticipate working on konq/webkitpart anytime soon and think it would not \
be the fastest avenue to a solution. Others are, of course, welcome to prove me \
wrong, but konq browser view is very tied to khtml. It is not just the settings \
either. I&#39;m traveling at the moment, but when I get back I&#39;d be happy to sit \
down and write a short list of the places I found.

Cheers,
Adam

David Faure wrote: 
> On Wednesday 01 July 2009, Adam Treat wrote:
> > On Wednesday 01 July 2009 05:23:47 pm Stefan Majewsky wrote:
> > > By now, I only have two reliable expert opinions: (links at the end)
> > > 
> > > [1] Adam Treat has worked on the Webkit KPart, and complains that Konqueror
> > > is much too much tied to the API of KHTML, and proposes to push KDE
> > > integration of Arora as this browser is modeled around Webkit. (My fear
> > > continues that we lose a unique selling point if our swiss knife Konqueror
> > > is not anymore the default web browser. It was the reason why many of us
> > > started to use KDE at the turn of the millenium. But that's a whole other
> > > story, and I might be misguided by my emotions in this regard.)
> > 
> > Uhm, to be clear, for those folks who desire a WebKit based KDE browser 
> > option, I think quickening KDE integration in Arora is the easiest, fastest 
> > and best path to take.  I am not pushing or advocating anything.  Just giving 
> > my opinion as to the best solution to a problem I have some experience with.
> And I am happy to work with you or other webkit kpart developers in the direction \
> of making the interfaces used by konqueror (e.g. kparts and extensions) more \
> generic. The goal was for them to be generic, if something is not generic enough \
> then let's talk about it, rather than moving to yet-another-browser.
> More details needed for sure (I really assume you meant KParts extensions
> and not "the API of KHTML" above, since konqueror does not call the API of
> KHTML _anywhere_).
> -- 
> David Faure, faure@kde.org, sponsored by Qt Software @ Nokia to work on KDE,
> Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).


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