[Qt5-feedback] Item Views Next Gen

[Stephen Kelly]

Artur Souza (MoRpHeUz) wrote:

> On Wed, May 18, 2011 at 7:58 AM, Stephen Kelly <steveire at gmail.com> wrote:
>> Did the code also move to the qt-components repo or was it abandoned?
>>
>> I can't find any files from the itemviews-ng repo in the qt-components
>> repo.
> 
> There weren't many "files" in itemviews-ng repo. 

Seems there's quite a few actually.

kde-devel at bishop:~/dev/src/playground/itemviews-ng/src{master}$ ls *.h
qdataroles_p.h         qgraphicsscrollbar_p.h  qlistcontroller.h         
qlistmodeladaptor_p.h      qsectionspans_p.h       qtablemodelinterface.h      
qtreecontroller_p.h    qtreeselectionmanager.h
qgraphicsheader.h      qgraphicstableview.h    qlistcontroller_p.h       
qlistmodelinterface.h      qtablecontroller.h      qtableselectionmanager.h    
qtreedefaultmodel.h    qtreeselectionmanager_p.h
qgraphicsheader_p.h    qgraphicstableview_p.h  qlistdefaultmodel.h       
qlistselectionmanager.h    qtablecontroller_p.h    
qtableselectionmanager_p.h  qtreemodeladaptor.h    qtreewidgetng.h
qgraphicslistview.h    qgraphicstreeview.h     qlistfromtreeadaptor.h    
qlistselectionmanager_p.h  qtabledefaultmodel.h    qtablewidgetng.h            
qtreemodeladaptor_p.h  qtreewidgetng_p.h
qgraphicslistview_p.h  qgraphicstreeview_p.h   qlistfromtreeadaptor_p.h  
qlistwidgetng.h            qtablemodeladaptor.h    qtablewidgetng_p.h          
qtreemodelbase.h
qgraphicsscrollbar.h   qitemviewsglobal.h      qlistmodeladaptor.h       
qlistwidgetng_p.h          qtablemodeladaptor_p.h  qtreecontroller.h           
qtreemodelinterface.h

The code is a new set of classes for lists tables and trees of data, and a 
new class for handling selection in views of that data, and some new views 
and compatibilty classes.

If QAIM is not the future and itemviews-ng is not in Qt components, is there 
a replacement for the InterView system? 

> Most of the files
> were related to business logic that we removed from QWidgets (the plan
> initially was to share the business logic for components that would be
> present in QWidgets and QML - like a slider for example). 

Yes, I understand that that is the concept of QtComponents. Having 'a model 
of a slider' be a stand alone thing that can be used by both QSlider and 
whatever the QML equivalent would be. I don't think that's what the op is 
asking about though, and I think the mention of qt-components might just 
have added confusion.

> When the
> qt-components repository was created we imported this code but it
> changed a lot during the development phase (mostly because the team
> didn't want to follow the strategy mentioned above anymore).
> 

You mean the strategy of 'a model of a slider' etc? Is there a new strategy?

Cheers,

Steve.