[Development] QStandardPath search paths
Hausmann Simon
Simon.Hausmann at digia.com
Wed Jul 31 18:33:31 CEST 2013
Sounds like a good idea to me. The two features (QStandardPaths and search dirs in QFile/QDir) were developed separately (the former after the latter).
If we are serious about promotional the search paths then this is probably the way to go :)
I wonder what Filesystem folks think about it (especially Andreas, who was around when I added the search dirs with Girish)
Simon
Fra: Alan Alpert
Sendt: 02:45 onsdag 31. juli 2013
Til: development
Emne: [Development] QStandardPath search paths
I was just adding the cross-platform asset directory as a search path
(https://codereview.qt-project.org/#change,61859 , with functionality
as discussed as part of adaptable UI) and the question arose: Why
aren't all (or at least some) standard paths available as search
paths?
Self documenting examples of what this would look like:
QFile ("tmp:/tmpfile");
QFile ("appData:dataFile");
QQmlApplicationEngine("assets:/main.qml");
It would be a nice developer convenience, and easy for me to implement
along with asset:. But it's not needed in the same way that asset: is,
which is so that you can write asset: paths outside of #ifdef
Q_OS_ANDROID blocks.
Does anyone have an opinion on whether I should or should not add all
the other QStandardPaths along with assets?
--
Alan Alpert
_______________________________________________
Development mailing list
Development at qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20130731/e38da62c/attachment.html>
More information about the Development
mailing list