kdiroperator detail view

Peter Penz peter.penz at gmx.at
Sat Oct 13 17:37:15 BST 2007


On Saturday, 13. October 2007 17:26, Anders Lund wrote:
[...]
> > From my point of view for KDE 4.0 we should consider using one of the
> > following approaches:
> >
> > A) Just let QTreeView do the job of resizing the columns. Don't try to
> > stretch the columns ourselves in the resizeEvent()... This makes it easy
> > to enable the resize mode QHeaderView::Interactive, so that the user can
> > adjust the width if wanted. I think his approach would be the same as we
> > have in KDE 3.
> >
> > B) Go back to the original approach where we stretched the columns to the
> > available width of the viewport. But in this case
> > QHeaderView::Interactive could not been activated in an easy manner... I
> > think this approach worked very well in the file-dialog, but as you said
> > in Kates sidebar a custom resizing of columns might really be useful,
> > which is not offered here...
> >
> > C) Combine the benefits of A + B, but this might be really time consuming
> > and tricky to implement (although I'm sure this is possible :-)).
> >
> > Honestly speaking I fear I have no time for implementing C for KDE 4.0.
> > Personally I'd go for approach B, but no matter whether we go for A or B:
> > I think the behavior should be consistent and not depend on the cache or
> > the directory content.
> >
> >
> > Do you have a suggestion which way we should consider?
>
> B is not usable in the case of kates sidebar, a widget which was copied by
> at least 4 other applications during kde3.
>
> So I'm for A, in fact I think that B is so bad that if it is chosen, I
> can't use the widget but will have to fork it.

OK, then I'll assure that approach A is included for KDE 4.0. I'll let you 
know if I have an update for this. Please give me some time, as I've some 
other higher priority issues to fix at the moment :-)

Best regards,
Peter




More information about the kde-core-devel mailing list