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

List:       kfm-devel
Subject:    .kde.html, khtml's embed tag and frames in konqueror
From:       Simon Hausmann <tronical () gmx ! net>
Date:       1999-08-19 11:50:23
[Download RAW message or body]

Hi!

I had look at the old kfm sources, khtml's <embed>-stuff and "old" kfmIII
code (especially kfmbrowser).

In fact Torben's code was able to embed an iconview in any html frameset,
as frame, which is more or less the basic .kde.html feature.

Unfortunately we *currently* can't do this anymore.

I might be wrong, but AFAIK in the old kfmIII code frames were normally
KfmBrowser's, and in case of the <embed>-tag KfmIconView's.

In Konqueror frames are KBrowser's.

I'm a little bit puzzled at the moment, but I have a wild guess /
"experimental proposal" (meaning I didn't think *that* carefully about it,
yet ;)

(please note that this requires adaptions in the OpenParts Part-Child
handling, but it should be possible :-)

(I'm now leaving out the .kde.html feature, but if we manage to get the
stuff below working, then embedding a KonqIconView should be more than
trivial I think)

In case of a frameset, we, the KonqHTMLView, handle frames in two ways:

- from the OpenParts's point of view we embed them as child-parts
  in the KonqHTMLView.

- from the Qt/QWidget/khtml point of view, we have/create KonqHTMLViews as
  children.

So every KonqHTMLView becomes the hosting parent part and child part at
the same time. 

It is either a child part of Konqueror::MainView *or* it is a child part
of another Konqueror::HTMLView.

It is a parent part of frames.

This looks like a *possible* and *very* flexible approach to me, but it
has two disadvantages:

- it creates big overhead, because we deal a lot with CORBA Objects, which
  leads to bloat in somehow. And KonqHTMLView will get pretty large, too.

- it requires tweaky handling in OpenParts, regarding activation of parts.

Advantage:

- we can have every kind of frame, not only htmlviews and iconviews.

So what do you think?

Greetings,
 Simon

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