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

List:       kfm-devel
Subject:    Re: KParts vs. Plugins in Konqi
From:       Kurt Granroth <granroth () suse ! com>
Date:       2001-10-22 20:24:23
[Download RAW message or body]

On Sunday 21 October 2001 12:55 pm, Ryan Breen wrote:
> My KPart would never be appropriate for viewing arbitrary web urls -- I
> basically want to write a Red Carpet / Windows Update type installer
> application that uses HTML for all user interaction and embeds in
> Konqueror. The goal is to decrease memory utilization, keep the user in a
> comfortable place, and save me from trying to do widget design.

I'm not getting why you want this in Konqueror.  It sounds like you should
create your own application and just extend KHTMLPart locally.

Why do you want the user to use Konqueror to do this?

> True.  I guess I was wondering if I could do some sort of hybrid
> Plugin->KPart.  How about this: I write a KPart associated with the
> mimetype for the xml files representing lists of packages that can be
> installed with my program.  I also write a plugin associating the action
> Tools->KDE Update with opening a file of this mimetype.  That should load
> up my KPart when the user clicks Tools->KDE Update, right?

No.  I think you're missing what Plugins are.  KParts::Plugins are "tools"
that interact with VERY SPECIFIC KParts.  They do *NOT* interact with
Konqueror.. they interact with whatever Part Konqueror is using at the
time.

You can verify this emperically.  Open up Konqueror in file browsing mode
and check out the plugins in Tools.  Then switch to web browsing mode
and check the Tools menu.  You'll see that all the plugins changed.  That's
because those plugins worked either on KHTMLPart or on KonqDirPart.. but
not on Konqueror itself.

-- 
Kurt Granroth            | http://www.granroth.org
KDE Developer/Evangelist | SuSE Labs Open Source Developer
granroth@kde.org         | granroth@suse.com
            KDE -- Conquer Your Desktop

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