Hi,
Didn’t think about your error yet, but from those two import clauses, the first one is correct. MeeGo is not Nokia only, that’s why com.meego :)

it depends on the location of your plugins/qml documents. com.meego is mapped to import/com/meego while com.nokia.meego is mapped to import/com/nokia/meego

guoqing wrote:

it depends on the location of your plugins/qml documents. com.meego is mapped to import/com/meego while com.nokia.meego is mapped to import/com/nokia/meego

Yes, this is the QML based detailed answer – this is where QML loads the plugins i.e. Qt Components.

But this doesn’t answer my question from a Harmattan Qt Component’s user point of view. Both can be right, depending on the deployment, but there is just one deployment of Harmattan on the device.

It seems Nokia is using one alternative in their example code and Qt Creator is giving me another one. More interestingly the solution that Nokia is using works worse for me, although their examples run fine on the device.

Confusing.

I am getting the same error message when changing from “import com.meego 1.0” to “import com.nokia.meego 1.0”…the related lines of code are:

fwiw I’m using

And yes, the hobbyist developer in me is also confused. :)

FWIW is ended up using only “import com.meego 1.0” and I forgot about this issue altogether. But it’s still confusing.

I can guess this is related to the fact that the device has an older version of Qt Components (1.0) while we are looking at the source of QmlComponentsGallery that uses a newer version of it (1.1). It would be nice to get a comment from someone who knows what’s going on, but I think we just have to wait for the final release of Harmattan SDK and an update for the N950 with Qt Components 1.1.

Both com.meego and com.nokia.meego work on the device, and AFAIK there is no difference between them functionality-wise. However, you cannot mix the two namespaces in one application: You have to use just one all over the place, otherwise you get runtime errors. (The problem seems to be that both directories contain a copy of the same C++ library, while only one library can be loaded at runtime.)

In the end we settled on com.nokia.meego, and I fixed the wizard for Qt Creator 2.3 accordingly. I’m sorry for the confusion, I personally learned about the com.nokia.meego namespace just a few days ago.

So… for those of us developing Harmattan apps as we speak: should we move to

in order to be on the safe side?

Yes, I suggest using “com.nokia.meego 1.0” all over the place.

But “com.nokia.meego 1.0” still gives the error the op and others experience…would be nice to get this issue solved before recommending folks moving to it…

awiese2007, please make sure that you’ve really no import ‘com.meego 1.0’ any more in any .qml file used by your application (might also be qml import libraries). If the error is still there, please file a bug report with enough details to reproduce it.

Change to com.nokia.meego made [gitorious.org] and indeed everything seems to work just like before. Thanks!

I get the following error if I use com.nokia.meego 1.0 as stated in my original post.

file:///usr/lib/qt4/imports/com/meego/PageStack.js:144: Error: Cannot assign QObject* to PageStack_QMLTYPE_24*

That one import line is the only change I do to trigger this. Any ideas why this would happen?

@Kypeli, I guess you use “com.meego 1.0” somewhere in your application, too. If you define the QML_IMPORT_TRACE environment variable before launching the application you should be able to see that.

if i import com.nokia.meego 1.0, i am getting error “Package not found”. what shall i do?