Qml/Js/Vm vs. Upgraded C++ GUI API with Bindings
-
the other poll brought the irrelevant Desktop Components into the mix. they don't factor in because they are obviously the next logical step along the path that has already been created: QtQuick -> JS/VM -> QML -> Desktop Components. Desktop Components stole the last poll.
tried to be as un-biased as possible (even though that's an impossible task) -
There is already another "poll":http://qt-project.org/forums/viewthread/16465/ (including an extensive discussion) on this topic. I don't think there is any reason to go through this exhausting subject again.
-
[quote author="Lukas Geyer" date="1336733332"]There is already another "poll":http://qt-project.org/forums/viewthread/16465/ (including an extensive discussion) on this topic. I don't think there is any reason to go through this exhausting subject again.[/quote]
That one's biased, and the newer one is skewed.
-
While I understand your motivation and goals, I don't think these polls get you anywhere closer to where you want to go. The only serious option I can identify is to persuade developers and maintainers via the mailing-list. As far as I can see, you are already working on this.
I don't see how this poll makes a big difference to the last one, you can't keep polling until you get the result you want to see. Even if you managed to post an unbiased poll, which is an art in itself.
And don't get me wrong, I don't even have a stake in how Qt is developed: I'm not using it. :P
Conclusion: I'm closing this thread since it won't add anything and duplicates other efforts.