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

List:       kfm-devel
Subject:    KParts vs. Plugins in Konqi
From:       Ryan Breen <ryan () porivo ! com>
Date:       2001-10-21 16:37:55
[Download RAW message or body]


I'm writing an addon for Konqueror, and I'm having trouble determining the 
best approach to take.  My development goal is to create a system management 
program that looks to the end user like a web app (all user interaction is 
driven through KHTML).  I need to be able to intercept user naviagtion, 
translate it into the appropriate work behind the scenes, and then generate 
the next 'page' of output and options.

I've done a good bit of reading and have played around with the alternatives, 
but I'm still not sure which of the possible integration choices makes the 
most sense.  As I see it, my choices are to a) write a Konqueror plugin or b) 
to write a KPart that can provide a browser/view for Konqueror.

I'm wary of choice a) because I'm not sure I can get the level of interaction 
(i.e. intercepting user navigation) with the KHTMLPart that I need.  With 
option b), I can extend BrowserExtension and have a great deal more control.

However, I would like my application to be available on startup of Konqueror 
(like a plugin) rather than simply when someone opens a document of the 
appropriate Mimetype.  Also, since my application is not based on handling 
files, the fact that the KPart will be loaded only when a certain Mimetype is 
requested doesn't seem to fit my goals.

Just hoping someone with more KPart / Plugin experience can steer me in 
the right direction . . .

Thanks,
Ryan

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