Hi Guiseppe, > (The topic is still "how to port Qt to another platform".)
It is in the nature of discussions, that they might change direction - like it happened with the AGILE side track. > (Yes, I 100% agree that QtQuick could be modularized much further, e.g. > drop its dependency from QtQml altogether, expose C++ APIs for the > QtQuick items, offer ready-made "rich" scene graph items, have clear and > explicit support for more than just OpenGL. A good summary of my point of view - even if the last one was not on my list so far and I would add "being more careful with resources". > But I don't want to start this conversation in this thread, let's have > it in the right places.). You might have access to these "right places", public forums is all what I have. Actually we already made a presentation at the QtCon 2016 ( https:// conf.qtcon.org/en/qtcon/public/events/428.html ) without seeing much of an effect. Showing an implementation is probably my best option to fuel the discussion. If you are trying to improve things from the inside and you are interested in experiences on our journey - don't hesitate to contact me. ciao, Uwe _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest