QML and Qt Quick

Rre you looking for "this?":http://doc.qt.digia.com/qt/qdeclarativemodels.html

Are you building for ubuntu itself or do you want to build a Qt for some other platform using a cross-compiler?

[quote author="dmcr" date="1352988312"]You have many ways to interact with QML. The two main ones are : A Context* myContext which is a QObject, which could be an object that keeps all the data you want to share with QML. and inside it have some properties like : @ Q_PROPERTY(int progressBarDuration READ getProgressBarDuration WRITE setProgressBarDuration NOTIFY progressBarDurationChanged)@ then with @yourDeclarativeView->rootContext()->setContextProperty("Context", myContext);@ and inside you can access throught Context.progressBarDuration A QDeclarativeItem is rarely created in Cpp, but you could, however. You could also declare it, and then using in QML like any other component with some import. In your example i think the first approach may be better, ie using a kind of Context.logViewerManager. Then, if you have some lists, use setContextProperty(my model.... However everything is in the doc :) [/quote] Thanks! It's exactly what I need! Thanks for the help!

Can't seem to load a module on Qt 4.8.3 for now. So: I flattened my module directory. Copy / pasted all the qml files in the same folder. Exported that folder into a qrc file. It works just fine.

Thanks sierdzio

Don't know who wrote :"the best pieces i code i am proud of are not the ones i made in front of my computer, but under my shower!" :)

Check this link "Installation Guide":http://doc.qt.digia.com/qtmobility-1.0-tp/installation.html Thanks & Regards

You can define which QNetworkAccessManager the engine uses to request stuff. If you have a custom QNAM which resolves things in the way you want, that might solve your issue.

Hi, Check out the qv8qobjectwrapper.cpp: static v8::Handlev8::Value ToString(QV8Engine *engine, QObject *object, int, v8::Handlev8::Object) You can modify that to call the toString() function of object if it exists (eg, via QMetaObject::invokeMethod() after first doing a QMetaObject::property() lookup and determining if it's a function). Cheers, Chris.

Hello, In fact such a solution is clearly a fast one, one you use if you are sure that your list won't have too many things to manage. As your case seems to be a more complete one, you should use a real list model in my opinion. Here is an excellent "how to":http://cdumez.blogspot.fr/2010/11/how-to-use-c-list-model-in-qml.html Good luck!

Ok. I will try to explain a bit. QML runs as C++ code. All QML widgets and objects. But QML does not support that functionality C++ has. So, in this case QML has interface to work with C++ code. Learn about C++ and QML linkage

No worries :) As a tiny improvement, it's good practice to name context properties with a small first letter to be able to distinguish them from classes/QML components. So instead of "MyClass", name it "myClass" - you could access enums for instance from QML with "MyClass.enumName" then, and so don't mix it up with a context property access. Also, the data-signal could be renamed to dataChanged, as it is probably reflects more what it does. But that's syntactic sugar, just a suggestion..