[Qt5-feedback] Scope of QtQuick features?

[Artur Souza (MoRpHeUz)]

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. 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.

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).

On Wed, May 18, 2011 at 9:03 AM, Stephen Kelly <steveire at gmail.com> wrote:
> What direction is a waste?

I think Mihail was talking about "wasting resources" to work on
QML/Desktop issues (just a guess from what I understood).


Cheers,

-- 
-------------------------------------------------------
Artur Duque de Souza
openBossa
INdT - Instituto Nokia de Tecnologia
-------------------------------------------------------
Blog: http://blog.morpheuz.cc
PGP: 0xDBEEAAC3 @ wwwkeys.pgp.net
-------------------------------------------------------