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

List:       kfm-devel
Subject:    Re: PartChild(Mode)
From:       Simon Hausmann <tronical () gmx ! net>
Date:       1999-02-19 15:18:09
[Download RAW message or body]

On Fri, 19 Feb 1999, Michael Reiher wrote:
>Simon Hausmann wrote:
>> 
>> On Thu, 18 Feb 1999, Michael Reiher wrote:
>> >Simon Hausmann wrote:
>> >>
>> >So all embedded parts that have special konqueror support because they
>> >inherit KonqView won´t cause menu flickering but all others will?
>> 
>> Right.
>> See my reply to Sven's mail for more information
>For smooth integration parts should derive from KonqView anyway, just in
>order to provide a common set of metods such as openURL(). But wouldn´t

Exactly, that's the second big reason for a common KonqView.

>it be better if the menu flickering would be solved already at the
>OpenParts layer? And is it possible to keep a basic set of konqueror

IMHO we would solve the problem at the OpenParts layer by implementing a part
child<->parent hierarchy (see my other mails for further details _why_ I think
this would help) .

>menu-/toolbar items, if a foreign part(ie not derived from KonqView) is
>active? Because menus like File, Options, Help or a menu to list the
>available views types should always stay the same (well, views might add
>something of course).
No, this would be theoretically only possible if we would drop all support for
 a) letting KonqMainView be an embeddable part as well
 b) letting all Konqueror views (KonqView's) be an embeddable part
and instead use a KonqMainWindow (derived from OpenParts::MainWindow) as
big-shell. And even then we'd only be able to completely "control" the
file/help menu, the rest is up the active part.

Ciao,
 Simon
 
--
Simon Hausmann - Tronical^Colorfast - <tronical@gmx.net> - IRCNet #colorfast

we have joy, we have fun, we have linux on our sun

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