David Faure faure at kde.org
Mon Jan 2 10:51:20 GMT 2006

On Sunday 01 January 2006 16:24, Till Adam wrote:
> - there's quite a bit of duplication between KListBox and KIconView, shall we 
> try to merge those into one class, not unlike QListWidget/View does? 
> KListWidget, then? 
> - If we change the name anyhow, would it be easier to leave the old classes as 
> is, put them into kdesupport and write a new one implementing the features 
> mentionend above in it? 

Sounds good to me.
But don't we need both a View and a Widget to provide this functionality?

Providing an all-in-one KListWidget isn't enough, for the case where we want
to provide our own model and not use ListWidgetItems.

I don't see how we can do this without duplicating all the kde-specific code,
or duplicating all the stuff that QListWidget adds on top of QListView -
but we probably need to do that anyway in order to define our own KListViewItems.
I think you forgot to look at the item classes.
K[3]IconViewItem provides:
- more readable word-wrapping
- custom pixmap size per-item

Hmm. Maybe this can be done in KListView/Widget or in a KListItemDelegate 
without reimplementing the item class themselves.

But the problem remains anyway: how to provide both a View and a Widget
to KDE code.

David Faure, faure at kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).

More information about the kde-core-devel mailing list