On 26 Jun 2017, at 19:10, Jean-Michaël Celerier <jeanmichael.celer...@gmail.com<mailto:jeanmichael.celer...@gmail.com>> wrote:
On Mon, Jun 26, 2017 at 6:19 PM, Frederik Gladhorn <frederik.gladh...@qt.io<mailto:frederik.gladh...@qt.io>> wrote: 5.10 is scheduled for the end of this year. I'd rather expect this to be in 5.11 - mid next-year. I hope we'll have something sooner for people to play with though, let's see. Question: why must a single component like this be coupled so tightly to the rest of the framework ? Why does it have to be in the "official" Qt release at all, and not in a separate git repo or something loosely coupled ? Couldn't it be released on a separate channel as a qml extension plugin ? Just trying to understand. The goal is to get the new TableView’s performance on the same level with ListView and GridView. (The old QML-based TableView is from a different planet.) The idea is to base the new TableView on the existing Qt Quick item view framework, and support all same item view transitions, item recycling, and all that. Providing such functionality as a standalone addition outside of Qt Quick is not doable without re-writing or forking the entire Qt Quick item view framework, which is a lot of code and goes into deep internals of libQtQuick and libQtQml. Even though there have been some discussions about re-writing the item view framework from scratch, we don’t plan to do that now as that would take a lot longer than it has taken so far to refactor the existing item view framework to support two-dimensional views. What remains to be done for the view itself is the actual table layout for the visible items. After that, there are a few other things on the TODO-list related to multiple delegate types, multi-selection, and so on (http://lists.qt-project.org/pipermail/development/2017-January/028344.html). -- J-P Nurmi
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
