[SPLIT] Future of Widgets in Qt
-
I'm too kinda disappointed with Qt focusing so much in QML and forgeting about QWidgets, which are the base of desktop applications..
QML could never replace QWidgets, in fact I think they be focusing on make QWidgets work in QML instead of making a brand new set of QML Widgets. >.< -
I feel somewhat alarmed that such issues are closed as "out of scope" with the recommendation to solve it using QML.
We started to use Qt some years ago, since it is kinda stable and don't think our development team would be happy if the future of UI development is only with QML.
Maybe we should start to write our alternatives-plan if QML is really the way of Qt in near future...
-
Yeah right. But what I meant is that it's alarming enough to close the issue because it is out of scope, because it's not considered important.
It makes me think about the behaviour of the maintenance team here at work... if we tell the customer that a bug "is not considered important enough to be fixed at the moment" this usually means something like "hey, we're going to release a new cool feature so you won't need this old and grumpy feature anymore" :)
-
[quote author="Andre" date="1295439915"]That QML recommendation was given in the mailinglist thread, not in the closing comment on the bugreport. But still, I found it worrysome (and wrote so in a reply in that thread).[/quote]
The recommendation is even in the bug-reports, I just got the following for http://bugreports.qt.nokia.com/browse/QTBUG-9826:
[quote]
Widgets in general is no longer within our scope, especially not widgets with graphics effects, and we strongly recommend using Qt Quick as a replacement for that. Qt Quick 2.0 will have way better support for hw accelerated effects. Hence closing this issue as out-of-scope.[/quote]While it pertains to QGraphicsEffects on QWidgets in a scroll area, Quick/QML might be more suited to that specifically, but shifting to QML for our entire app isn't really an option.
Yes, I am worried too...
-
Hey, this entire thread does not mention digia once. As I understand it, it is up to digia to maintain Qt widgets and fix related bugs.
-
@Andre: I see.
-
@unclewerwerner: Any ideas on how Digia will handle bug reports from the community? qt.digia.com only wants my money. ;)
-
Bug reports from the community should go into the "public bug tracker":http://bugreports.qt.nokia.com
-
There's a quite interesting article "here":http://zrusin.blogspot.com/2010/11/2d-musings.html about some of the advantages of moving to a QML / scenegraph based model for widgets in the future.
I think the qt-components project is going to be very important. Having a good collection of common widgets implemented in qml will go a long way to smoothing the development of consistent UIs for the next generation of devices and applications.
-
[quote author="Volker" date="1304346935"]Bug reports from the community should go into the "public bug tracker":http://bugreports.qt.nokia.com[/quote]
[quote author="Alexandra" date="1304346935"]Nothing changes regarding maintainership etc. until we have the Open Governance processes in place.[/quote]
Ok. In that case, I hope someone will go through the out-of-scope tickets and review/flag them as "desktop issues" instead, as it might be important stuff in there that's useful for whoever will decide to maintain that part in the future.
The out-of-scope labeling is a bit disheartening tho, but I suppose we all have to wait a bit and see how it pans out. (Very neat website this though. ;) )
