QML and Qt Quick

You rule portoist

Filed it already, thanks for your help. Hope that Qt5 could become more stable with every release

OK. Parsing the QML is an option, but probably too cumbersome. You would need to do it before loading the QML. Once you load it, it will throw errors on properties that were not included, which is not what you want. What about a "just in time" property inclusion? Instead of adding numerous Q_PROPERTYies, provide an object with something like: @ Q_INVOKABLE QVariant getProperty(const QString &propertyName); Q_INVOKABLE void setProperty(const QString &propertyName, QVariant value); @ But this way you will loose all the NOTIFY goodness. Or you could divide your properties into modules and include them in QML using import statements.

So, in new qt qiuck2 .0from qt 5.1 i can use qmlRegisterType or not? Can't find information about it. :{ edit: http://doc-snapshot.qt-project.org/qt5-stable/qtquickdialogs/qml-qtquick-dialogs1-filedialog.html

You're welcome :) Yeah, the "best" code architecture can be different for different purposes. I don't have any direct ideas for now, sorry. But keep learning and asking. Good luck!

Never mind. It is working now, don't know what happened (I did "clean", and then "build" in both DLL and application).

thank you .Sorry...

thx for answer. i solved this problem by setting the context property each time i update it. i mean @ //helper class.. void onMapUpdated() { this->_viewer->rootContext()->setContextProperty("theMap", theMap); } @ i passed the ApplciaitonViewer object as a paramter to the helper class constructor. it is working now. but im worried about its drawbacks. what can they be? do u have an opinion?

"onClicked" not "onClicke[drive]" @ MouseArea { anchors.fill: parent onClicked: { Qt.quit(); } } @

Thanks, I haven't noticed I could use clip to achieve it

Thanks for your helps

Majority of Android users are still running Android 2.3.x. I'm not entirely up-to-date with Qt on Android, so I can't say much about it. It is based on NDK, though, so Qt should not care too much for the SDK. Run SDK manager and download additional SDKs if you need to.

Hi Slerdizlo, Recently i got a solution for the question that i have asked and I want to write it in here. May be some others are also got this issue, I got the solution from the Qt forum, http://qt-project.org/forums/viewthread/7047 Thanks to Denis Kormalev, Volker and Brucewuu for solving this problem. If you can go through this link, you can easily understand it. For accessing any file outside QRC, use "absolute filepath" of the file. For example: In main.cpp file; QString path = QDir::currentPath(); //path where the exec is present if your file is in src/file.qml of exec folder, then you can access it like (path += "/src/file.qml";), now path is the absolute file path for file.qml. You can access it in any of the QRC file. QQuickView view; view.rootContext()->setContextProperty("myFile", path); view.setSource("qrc:/main.qml"); In main.qml file: Loader { id: loadItem source: myFile } Item { Component.onCompleted: loadItem.item } Regards Ansif

Thanks to both of you and sorry that I haven't mentioned my intentions clearly. when the image is too large,I want to handle the view with two ways 1: when the fillMode is Pad, I could use the scrollView or flickable to view the whole image 2: when the fillMode is PreserveAspectFit, the image will shrink to appropriate size Since it is impossible to do it with Flickable or ScrollView, I would find another solutions, like create a new component, with two Images, when the fillMode is PreserveAspectFit, I show the Image with ScrollView or Flickable; change it back to normal Image when it is other fillMode

Hi, Thanks, setting the rendertype to native fixed the problem! I'm not keen on trying to install a separate Qt from the one that comes from the Ubuntu repository, which lags a bit behind. Nice to know there's some performance gains still to come. Regards

Possibly. However, there are no plans to deprecate or remove it. Sleep safe :) IMO, it's ready. People have different opinions here, though, and it depends on your use case. Definitely, both Widgets and Quick have their benefits, so it's best to pick whatever suits your project best. From my own experience, I'll say that QML and declarative mindset is the way to go. It's just so easy to build the UI this way :) QtQuick1 uses QGraphicsView, QtQuick2 uses Scene Graph - both are available in Qt5. Again, this is up for a debate, but scene graph is rather potent in power :) Functionality of scenegraph and QGraphicsView does not fully overlap, so they can't really be objectively compared without going into specific details. If your project will be used by other people, stick with Qt4 for a while, as Qt5 is still not in all repos.