Hi,
Thank you for your feedback. Could you please elaborate what kind of changes you'd like to see to the QQmlComponent API? It is not clear to me what you mean by "compiling loaded QML from a byte array". Similarly, could you please explain what you mean within loading definitions into the component cache? Are you referring to the ability to populate the component cache on application start up? Regarding the qmldir files I conceptually agree that it would be nice to get rid of them, but it is not an easy task and not a task that I think of being of high priority (unless somebody convinces me otherwise). However one thing I would like to see as an initial step in the same direction would be to generate the content of the files automatically from meta-information for example in the build system. Such a step would potentially allow for replacing these files with a superior mechanism. Could you please explain what you mean by an array of plugin bytes? I also don't see a tight coupling between the QML engine and the network access manager. What coupling are you referring to? Is it the ability to compile the engine when the network access manager is disabled from the build? Regarding internationalization support: I invite you to contribute the work towards allowing different mechanisms for translations. It would probably make most sense if you could attend the Qt conference to discuss the topic in person. Simon ________________________________ From: Development <development-bounces+simon.hausmann=qt...@qt-project.org> on behalf of m...@rpzdesign.com <m...@rpzdesign.com> Sent: Thursday, April 21, 2016 3:08 PM To: development@qt-project.org Subject: Re: [Development] [Announce] Qt 5.7.0 Beta released Jani & Tuuka: There is a reference to the upcoming Qt Quick Compiler in 5.8 in the 5.7 beta announcment. http://blog.qt.io/blog/2016/04/21/qt-5-7-beta-released/ Qt 5.7 Beta Released - Qt Blog<http://blog.qt.io/blog/2016/04/21/qt-5-7-beta-released/> blog.qt.io Qt 5.7 Beta is now released and available for your feedback. There is a lot to review – new modules, leveraging C++11 features, and the new unified product ... Where do we send input to the people in charge of making 5.8 design decisions? Since it looks like this is going to a significant re-factor of the base code from 5.7, this is the moment to speak up. I submit that there is a currently a dysfunctional design dependence between a 5.8 Qt Quick Compiler, the requirement of QMLDIR files for plugins, the QR("") Internationalization pattern, and QQmlComponent C++ class. The architecture is cumbersome if you have a project structure that deviates in any way from the classic QRC oriented resource files, you do a lot of work. What I would like to see in 5.8 and beyond. 1) QQmlComponent as the primary QML interface for C++ developers with the QtQuick Compiler optionally compiling loaded QML from a byte array and shipped to a customer in the form of downloadable Compiled QML!!! 2) QQmlComponent able to load definitions into the component cache to be used in qml "Import MyComponent 1.0" 3) Drop QMLDIR files entirely, they are really stupid. They have no place in a dynamic loadable plugin/component architecture. 4) Allow plugins (either C++ or QML) to be loaded by C++ or QQmlComponent.LoadPlugin( array of plugin bytes!, not FILE or URL based!) Right now I am forced to statically link my plugins into the executable for QML to see them and use them. Very clumsy. 5) Decouple the GUI/QML from NetworkResourceManager. The NetworkResourceManager should be an optional component, not required for every project. If you need to download QML using an URL, provide a bridge class to perform that. 6) International Support Decoupled (So I can use my own hooks instead of translation files in Qr(" ") usage pattern I really think that if the architecture and cumulative design choices are reviewed, you can see a lot of legacy decisions that now can get factored out of the design so there is cleanliness and a proper fit for the Qt Quick Compiler in relation to the other QML/C++ constructs. Thanks for listening, Marco On 4/21/2016 4:06 AM, List for announcements regarding Qt releases and development wrote: Hi all, Qt 5.7.0 Beta is released today, see <http://blog.qt.io/blog/2016/04/21/qt-5-7-beta-released/> http://blog.qt.io/blog/2016/04/21/qt-5-7-beta-released/ Big thanks for everyone involved! br, Jani Jani Heikkinen Release Manager The Qt Company Elektroniikkatie 13 90590 Oulu Finland jani.heikki...@qt.io<mailto:jani.heikki...@qt.io> http://qt.io<http://qt.io/> [http://s3-eu-west-1.amazonaws.com/qt-files/logos/qt_logo_with_text_green_rgb_400x141.png]<http://qt.io/> [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_facebook.png]<http://www.facebook.com/Qt> [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_twitter.png] <http://www.twitter.com/qtproject> [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_linkedin.png] <https://www.linkedin.com/company/the-qt-company/> [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_googleplus.png] <https://plus.google.com/104580575722059274792> [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_youtube.png] <https://www.youtube.com/QtStudios> _______________________________________________ Announce mailing list annou...@qt-project.org<mailto:annou...@qt-project.org> http://lists.qt-project.org/mailman/listinfo/announce _______________________________________________ Development mailing list Development@qt-project.org<mailto:Development@qt-project.org> http://lists.qt-project.org/mailman/listinfo/development
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
