setBaseUrl() problem

[ugluk]

My directory tree is like this:

root
  assets
  content
  skins
    default
  test
    main.cpp

root
  assets
  content
  skins
    default
  test
    main.cpp

To copy to clipboard, switch view to plain text mode 

// I do this in test/main.cpp:
  view.engine()->setBaseUrl(QUrl::fromLocalFile(
    QCoreApplication::applicationDirPath() + "/../"));
 
// I do this to a QQuickView instance:
setSource(QUrl::fromLocalFile("skins/default/main.qml"));

// I do this in test/main.cpp:
  view.engine()->setBaseUrl(QUrl::fromLocalFile(
    QCoreApplication::applicationDirPath() + "/../"));

// I do this to a QQuickView instance:
setSource(QUrl::fromLocalFile("skins/default/main.qml"));

To copy to clipboard, switch view to plain text mode 

main.qml loads OK, but cannot reference assets in the assets subdirectory as, "assets/someimage.png", but needs to do "../../assets/someimage.png", also I cannot import as 'import "content"', but need to do 'import "../../content"', whereas I'd like to do 'import "content"'. Does there exist a workaround?

[wysota]

Where is the final binary located?

[ugluk]

In test. Do I need to write a custom filesystem provider?

[wysota]

In "test" or in some "debugsomethingsomething" directory? Please check where the binary really resides. Also make sure you resolve file paths in QML using Qt.resolvedUrl().

[ugluk]

Yes, in test, this is built on linux with the new Qt5 beta 2. On windows it usually is in test/debug.

Component.onCompleted: console.log(Qt.resolvedUrl("assets/image.png"))

Component.onCompleted: console.log(Qt.resolvedUrl("assets/image.png"))

To copy to clipboard, switch view to plain text mode 

outputs

file:///home/user/root/skins/default/assets/image.png

Could this be a Qt5 bug?

[wysota]

I'm beginning to think that setBaseUrl() does not involve resolving files from within QML itself.

[ugluk]

For real? Did you test with QtQuick 1? A workaround might be a filesystem provider, say "assets://image.png". I've seen such a thing on the Blackberry.

[wysota]

For real? Did you test with QtQuick 1?

No, only on QtQuick 2.0 since that's what you said you were using. Qt.resolvedUrl() docs claim to resolve the url relative to the QML file so the output you get is correct. One would have to check how it behaves when resolvedUrl() is not called.

A workaround might be a filesystem provider, say "assets://image.png". I've seen such a thing on the Blackberry.

Or an image provider.

[ugluk]

One more question on URLs, wysota. Does the import statement accept an URL to import from, or does the argument have to be a local pathname? What I am looking at is, whether the import statement can load a QML from a website or from a filesystem provider.

[wysota]

Does the import statement accept an URL to import from, or does the argument have to be a local pathname?

If you are talking about javascript files then it can be whatever QNetworkAccessManager supports, so http URLs should be fine.

What I am looking at is, whether the import statement can load a QML from a website or from a filesystem provider.

I have no idea how it behaves for QML files because for QML you don't pass URLs but rather package names. You'd probably have to try with qmldir files if it works or not.