On Tuesday 27 August 2013 08:47:18 Juergen Bocklage-Ryannel wrote:
> or the alternative of deprecating search paths. Anyone have an opinion here?
> > My opinion is to deprecate search paths. That's what
> > QStandardPaths::locate is for.
>
> If this is about QDir::addSearchPath read on:
>
> We us
or the alternative of deprecating search paths. Anyone have an opinion here?
> My opinion is to deprecate search paths. That's what QStandardPaths::locate is
> for.
>
>
If this is about QDir::addSearchPath read on:
We use it for embedded projects to easily change asset paths between
developer
On segunda-feira, 19 de agosto de 2013 17:15:31, Alan Alpert wrote:
> The discussion has moved on a bit since, but I don't think we really
> answered this question (one person said "sounds good", before Thiago's
> email). Asset paths are probably going to be treated slightly
> differently now, but
On Wed, Jul 31, 2013 at 10:55 AM, Thiago Macieira
wrote:
> On quarta-feira, 31 de julho de 2013 16:33:31, Hausmann Simon wrote:
>> I wonder what Filesystem folks think about it (especially Andreas, who was
>> around when I added the search dirs with Girish)
>
> My opinion is that the search path f
On sábado, 3 de agosto de 2013 10:34:41, David Faure wrote:
> On Friday 02 August 2013 12:56:31 Thiago Macieira wrote:
> > On sexta-feira, 2 de agosto de 2013 11:50:57, David Faure wrote:
> > > > QStandardPaths returns "paths that are standard in this system". If
> > > > one
> > > > of
> > > > them
On sexta-feira, 2 de agosto de 2013 11:50:57, David Faure wrote:
> > QStandardPaths returns "paths that are standard in this system". If one
> > of
> > them is a Qt file engine, then I don't see a problem in it returning
> > "assets:/main.qml".
>
> There's standard-for-Qt and standard-for-the-OS
On quinta-feira, 1 de agosto de 2013 10:55:46, David Faure wrote:
> It breaks opening such things with other means than QFile (e.g. native
> APIs).
>
> It ties in two features together (QStandardPaths and QFile's file engines)
I've made my position clear that I dislike the file engines and search
On quarta-feira, 31 de julho de 2013 11:18:38, Alan Alpert wrote:
> On Wed, Jul 31, 2013 at 11:13 AM, Thiago Macieira
>
> wrote:
> > On quarta-feira, 31 de julho de 2013 11:05:56, Alan Alpert wrote:
> >> Search paths make "asset:/main.qml" work on all platforms. I don't see
> >> how QStandardPath
On quarta-feira, 31 de julho de 2013 11:05:56, Alan Alpert wrote:
> Search paths make "asset:/main.qml" work on all platforms. I don't see
> how QStandardPaths::locate would work here other than
>
> #ifndef Q_OS_ANDROID
> QStandardPaths::locate(AssetPath, "main.qml");
> #else
> "asset:/main.qml";
On quarta-feira, 31 de julho de 2013 16:33:31, Hausmann Simon wrote:
> I wonder what Filesystem folks think about it (especially Andreas, who was
> around when I added the search dirs with Girish)
My opinion is that the search path feature is at the wrong level of
abstraction. It's also a potenti
(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
11 matches
Mail list logo
