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

List:       kfm-devel
Subject:    Re: KMultiPanner
From:       Matthias Welk <welk () fokus ! gmd ! de>
Date:       1999-03-11 9:06:02
[Download RAW message or body]

On Wed, 10 Mar 1999, David Faure wrote:
>On Wed, Mar 10, 1999 at 03:46:21PM +0100, Matthias Welk wrote:
>> I have implemented a first version of a KMultiPanner which can be downloaded
>> under:
>> http://www.fokus.gmd.de/research/cc/cats/employees/matthias.welk/private/kmultipanner_0.1.tgz
>> 
>> What is already done:
>> - add children
>> - set active child
>> 
>> What is planned:
>> - remove children (of course)
>> - draw visual feedback of the active child
>
>> Known problems:
>> - rubber band of nested splitters is not drawn
>> - children can only be added to a splitter at first or at last (this is a
>> limitation imposed by the qt-api)
>
>Tried kmultipanner :
>
>I have a big buggy gray area on the top of the window. Doesn't appear in
>your snapshot :)

Which qt-version do you use ? I compiled it with the version from 03-10-99.

>Moving panners give no visual feedback (BTW Qt lets you choose between opaque
>resize or the simple black line moving).

Yes, I used the default (KeepSize). Future versions should be able to let you
choose between KeepSize and Stretch.

 >
>Now the big question : 
>
>You know I implemented in konqueror the use of
>QSplitters, nested just like in the qsplitter example.
>Do we really need our own widget ? Just imagine an icon view in every area
>of your snapshot.
>Each view is just too small for showing a usable icon view. Which means
>that the user will probably never want to do such a complicated setup,
>don't you think ?
>

I started the work, because we discussed about such "complicated" setups (you
remember the beautiful drawings :-)
We also came to the point, that we don't want to restrict the user.
The size - imagine you have a full screen konqueror, then each is not to small
for showing the contents.

>Sorry for this bad welcome to your widget. I think it's a lot better for us 

No problem, we are here to build user friendly applications and therefor it's
needed to discuss about the best solution :-)

 >to use a Qt widget, maintained by TT (hum, and for which I already sent
two  >mails to bugs@troll.no about possible improvements), than our own,
>especially if the user will never use it anyway.
>

Normally I agree with you in using Qt widgets instead of self written ones.
But I thought  simplifying and adding usefull features to the splitter would
help us using nested splitters in konqueror.
BTW how do you add a widget right before/after the active one ? Qt lets you
only use moveToFirst/Last. This will be implemented in KMultiPanner.
What's about the focus stuff ? KMultiPanner will give you a visual feedback of
the active child.

I think other programs can profit from the new widget too.

Why the user shouldn't use KMultipanner ? He is not forced to build complicated
setups, but the widget gives him the possibility to do it. And the programmer
profits from the easy use.

However, I will comply with the majority :-))

Greeting, Matthias.

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