Using QTreeView instead of QListView for outputview
Andreas Pakulat
apaku at gmx.de
Tue Jun 24 23:22:39 UTC 2008
On 25.06.08 01:13:38, David Nolden wrote:
> Am Mittwoch, 25. Juni 2008 01:07:20 schrieb Andreas Pakulat:
> > I had enough testing myself a few minutes ago. That patch is unbearably
> > slow. So for now we'll have to stick with qlistview and
> > non-wordwrapping, until someone either
> >
> > - writes a new itemview that allows scrollbars+wordwrapping for simple
> > line-lists
> > - puts an itemview API on top of QPlainTextEdit so we don't have to
> > change the outputmodel-approach to QString.
>
> We don't need line-wrapping as long as we have a scrollbar. ;) On my machine,
> I have disabled the "uniformItemSize" option, and now I have a scrollbar. It
> seems a bit slow sometimes, but it works. Maybe we can tweak it somehow so
> it's faster, like for example re-implementing the size-hint function(it
> depends on where the slowness comes from). After all we know that each item
> has the same height, that should be enough knowledge to make the view
> perfectly fast.
Right, I forgot the third option:
- someone figures out how to make it fast with added scrollbars :)
Your idea sounds like a good start, I'll have a try at that tomorrow now
that I've got a reliable test-case (touch a few files in kdevplatform
and then running a make install on it)
Andreas
--
You're definitely on their list. The question to ask next is what list it is.
More information about the KDevelop-devel
mailing list