Try putting your QML files in subfolders. You will probably want to do this sooner or later anyway to keep your source tree manageable as the project grows.
Just beware that you then have to import the folder of the components you are using from within the QML files unless they are in the same folder. IE. import "../Components" from your screen files. -Even -----Original Message----- From: Interest [mailto:interest-bounces+even.kristoffersen=honeywell....@qt-project.org] On Behalf Of Jason H Sent: 4. januar 2017 16:44 To: interestqt-project.org <inter...@qt-project.org>; qt-creator <qt-creator@qt-project.org> Subject: [Interest] QML dir hierarchy I am cross posting this to QtC and Interest because it's a combinational issue. My QML projects are getting sizable, I'd like to start breaking my QML resources down in a hierarchy, but my attempt at that has failed. Given: qml.qrc / - app.js - Screen1.qml - Component1.qml - Screen1.qml - Component3.qml - Component4.qml - Screen1.qml - Component2.qml I'd like to break it down into: qml.qrc / - Screens / -- Screen1.qml -- Screen1.qml -- Screen1.qml - Components / -- Comoponent1.qml -- Comoponent2.qml But I was not able to accomplish this in QtC. So I hacked the QRC file to have two prefix entries: <qresource prefix="/screens"> and <qresource prefix="/components"> However this resulted in errors. Also, in QtC they weren't folderized, they just appeared as screens/Screen1.qml ... components/Component1.qml ... How can I accomplish a folderized QRC? Currently, the filesystem is flat, but I don't mind adding them to actual folders if that would help. _______________________________________________ Interest mailing list inter...@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest _______________________________________________ Qt-creator mailing list Qt-creator@qt-project.org http://lists.qt-project.org/mailman/listinfo/qt-creator
