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

List:       kde-devel
Subject:    Re: Filter html before Konqi renders it
From:       "Mark A. Taff" <marktaff () comcast ! net>
Date:       2006-05-24 19:54:06
Message-ID: 200605241254.06410.marktaff () comcast ! net
[Download RAW message or body]

On Wednesday 24 May 2006 03:53, Andras Mantia wrote:
> This seems to be OT. Use proxy filtering and it will work for every
> browser. Privoxy is an example for such filter.

I apologize if it is off-topic.  It seemed to me that developing filtering 
capabilities for the KDE web browser would be on-topic?  As it stands, it 
seems google can't find any real documentation on how to extend Konqi for 
such purposes.

As for the filtering proxies, yes, they would work, but they also require 
downloading, installing, and configuring an external server.  Your same 
argument about proxies could be said for the features provided by adblock, or 
the javascript pop-up blocker, yet those were included in Konqi.

Ironically, it is because adblock was included in Konqi that filtering should 
also be included, at least as an extension.  Now that Konqi has adblock, 
using an external filtering proxy is like using a 10 pound sledgehammer to 
drive a finishing nail (unless you also want to cache data, or spy on people, 
which I don't).

Most of the code for this is already written within Konqi, between adblock and 
the javascript per-domain actions, it just needs to be adapted.

I filed a wishlist bug for more info on what I'm after: 
http://bugs.kde.org/show_bug.cgi?id=127915

Perhaps someone here can explain the merits of Konqi's plugins vs extentions 
vs tools vs status bar?  Or perhaps point me towards a tutorial?  This really 
shouldn't be that tough to implement, I think.

Regards,

Mark
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]