[Qt5-feedback] Scope of QtQuick features?

[Stephen Kelly]

Artur Souza (MoRpHeUz) wrote:

> On Wed, May 18, 2011 at 8:50 AM, Stephen Kelly <steveire at gmail.com> wrote:
>> I've seen some efforts and research in the direction of dealing with
>> these kinds of issues, but is it the intention to go back to the drawing
>> board of QML/QtQuick to deal with this stuff properly and at the right
>> abstraction level, or to try to shoehorn 'traditional' concepts into QML
>> as it currently exists and implementing stuff like the QML TableView
>> does? If the scope of QML changes, the design and tradeoffs probably
>> should too.
> 
> I've seen this efforts too (you can find some drag&drop code for QML
> if you search Google), but this seems out of scope for NQDF.

Why do you say it's out of scope? That's surprising.

> The main
> problem for me is that *today* this means that it would be incredible
> hard to have anything desktop related into QML but I hope that with
> open governance and Qt Summit we can talk about having this kind of
> work being done even outside of Nokia and merged into QtQuick.

Sure, there can be collaboration and goals, but NQDF remaining the 
maintainer of those parts of Qt mean they set the goals.

But, yes, that stuff will only become clear after open governance causes 
devel lists to be open etc.

> 
> I have talked with some customers and most of them are developing
> desktop applications using Qt and they love QML but when they see the
> lack of features like the one you mentioned, they just give up using
> QML (we can talk about rewriting the UIs but the reality for customers
> is much different as this means a waste of time/money without
> financial return).

Indeed. I think KDE will have the same issue with it.