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

List:       kfm-devel
Subject:    Re: using qcom interfaces wit parts (was Re: Plugins for non-major Parts)
From:       Waldo Bastian <bastian () kde ! org>
Date:       2001-09-14 20:30:22
[Download RAW message or body]

On Friday 14 September 2001 09:16 am, Kurt Granroth wrote:
> On Thursday 13 September 2001 03:13 pm, Waldo Bastian wrote:
> > But isn't "kpart/part.h" or e.g. "ktexteditor.h" the interface of the
> > part?
>
> Okay, time for some very concrete examples :-)

> Narrowed down even more, in order to access the KHTMLPart's DOM tree, the
> Dom Tree Viewer plugin *needs* a handle on an actual KHTMLPart.  Therefore,
> the plugin needs to #include <khtml_part.h> and link to libkhtml

It needs to include the header-file, but doesn't necasserily need to link 
libkhtml.

But that's very basic, isn't it, in order to use a certain interface you will 
need to know how it looks like, and it is up to the part to decide whether it 
wants to expose an interface beyond the generic kpart interface.

That must be a deliberate decision, because by exposing an interface you will 
become responsible for it as well, in terms of BC across versions.

Cheers,
Waldo
-- 
And there went out another horse that was red: and power was given to him 
that sat thereon to take peace from the earth, and that they should kill
one another: and there was given unto him a great sword. (Rev 6:4)

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