On Friday, 7 de October de 2011 20:08:55 Samuel Rødal wrote: > > Agreed, animating stuff, drawing custom widgets etc. is indeed much > > easier in QML. But to repeat: I don't want to animate, I don't want > > custom widgets (and I am talking about the "ordinary" and typical user > > interface elements such as buttons, comboboxes, not about "custom > > widgets" such as graphs, stock tickers or what not). > > > > So all this doesn't bring me any value. > > It's not necessarily about glaring animations, rather of subtle fading > etc (which granted can be done with QWidgets as well, but in a way > that's less easy to experiment with and tweak for a designer). See the > YouTube video in this blog post to see the possibilities: > > http://labs.qt.nokia.com/2011/03/10/qml-components-for-desktop/
Till, I think Samuel's words here are the issue that you're missing. The main message of your email seemed to be "I can do my UI today with Qt 4, therefore I will be able to do that for the next 5 years". That strikes me as rather naïve... You're assuming that either: a) the UIs of 5 years from now will be remarkably similar to today's, so the needs in the architecture won't be too different b) the architecture is so impressive that it will be able to handle the requirements of UIs 5 years from now or c) the architecture will evolve and will be able to support the new UI requirements My sending of a screenshot of a Qt-based KDE screenshot of 14 years ago is to show that UIs change quite a lot. The change is constant, it's not one major change at a fixed point in time. And even if we could predict when exactly a new architecture needs to be ready, we still need to research, test, mature and productise this architecture. That's what Qt Quick is supposed to be: the foundation of our needs for a long time. Maybe we're wrong, but this is our opinion based on our understanding of today. Please note what Samuel said: it's not about wobbly windows or drop shadows outside your window. It's about subtle animations, fading effects, transitions, proper anti-aliasing, etc. *inside* your window. And that's to match the native look and feel that you're looking for: if the native look and feel has them, so should Qt and then those technologies will be required. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel Open Source Technology Center PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Qt5-feedback mailing list Qt5-feedback@qt.nokia.com http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback