QML and Qt Quick

cmer4's solution worked for me. Mobility doesn't seem to work in the desktop mode (it's not mobile, go figure), but it works perfect when I build for Android. I bet there is a way to make Mobility work for desktop though...

Thank to ZapB and Lukas Geyer.

Hi! First, thank you for the quick answer ^^ Timer is just what I was looking for ;) I did what I wanted and I event put a little animation :) Thanks a lot. I have just a quick question about another thing, if you don't mind: How should I comment my QML files if I use doxygen documentation? I mean, what syntax should I use in order to make doxygen recognise it? thank you again ;)

What's up with this: https://qt.gitorious.org/qt/qtdeclarative/blobs/75445c228476e4905cef3fb89a849f93f33e768f/src/quick/items/qquickwindow.cpp

Thank you alot....:)

Got it! I think now I've changed the QT version to 5, I have the option to create a 'Qt Quick 2 Application'. Creating a new project, I can see a different entry in the .pro file. Copying this accross to my old project: @ Please do not modify the following two lines. Required for deployment. include(qtquick2applicationviewer/qtquick2applicationviewer.pri) qtcAddDeployment()@ fixes it.

thanks, I just want to use as soon as possible [quote author="Jens" date="1356695140"]I can assure you we are completely aware of that. It was just not possible to complete it in time for the release. It is scheduled for 5.1. For the time being you can still use Qt Quick 1.0 if you need this functionality in Qt 5.[/quote]

I have not tried so I cannot offer detailed help but keep in mind that QtQuick 2.0 is not using QGraphicsView as it's base any more so it is likely to be a bit more difficult to get it to working on top of GraphicsView than it was in Qt 4. This is part of the reason why all of QtQuick 1 is still included in Qt5. If you can find a working example with Qt4, you should be able to port it fairly easily to Qt5 by using the QtQuick 1.0 compatibility module.

The API of the WebView type in QtWebKit 3.0 is completely different to the previous version. See http://doc-snapshot.qt-project.org/5.0/qtwebkit/qtwebkit-index.html for information, and see http://doc-snapshot.qt-project.org/5.0/qtwebkitexamples/qtwebkitexamples-index.html for examples using the WebView type. From what I can see, the new API is simpler, but possibly allows less introspection and binding capability, than the previous version. It could be that inspecting the DOM or calling JS functions directly on a WebView is not possible with the new API. You can, of course, use QWebElement and friends, but you might have to write some custom wrappers to expose its functionality to QML. I don't really know the WebKit code at all, so I can't really say for sure, to be honest. Cheers, Chris.

That's good info to know. If my QML app were to @import FileIO 1.0@ as in "this example":http://www.developer.nokia.com/Community/Wiki/Reading_and_writing_files_in_QML, I'd imagine an attacker could intercept and change the QML and/or JavaScript during the internet transaction and wreak havoc. Suppose the C++ end of my QML app does not contain any of the FileIO modifications like in "that example":http://www.developer.nokia.com/Community/Wiki/Reading_and_writing_files_in_QML. Suppose my app is based strictly on an entry level QML example where the C++ merely implements a QML view. What sort of damage could an attacker do? Another way to ask the same question: What sort of control do I have over the user's system if I start a new QML app in Qt Creator and write strictly QML/JavaScript without writing any C++ code?

That works, except that it creates an additional window with the tray icon.

Pleasure :-) I was afraid my last post could be a bit too enigmatic, but had no time to write more. Anyway, it works for you, so we're all happy.

QML works using meta-object information only. You can pass a QObject pointer between methods and then use qobject_cast<>() to get an object of your A class (or, if you prefer, you can simply use the meta information to interact with the QObject).

They are working fine with QtQuick 2.0. But you cannot use a Window or an ApplicationWindow in a QtQuickView so if you want to use Gallery.qml, you have to change the root item to be a Rectangle first. The reason for the error message is that Window is not a QQuickItem itself. The QQuickView is a window that is owned by C++ and cannot be controlled by QML. You can alternatively use a QQmlEngine and pass it Gallery.qml to avoid this conflict. This is what qmlscene does when the root item is a Window.

Ok. Thanks. I think the solution is (and maybe for others with the same issue) to create an interface class that handles the communication between the C++ (classes) and the QML GUI. That way at least the C++ is free of version specific hookins, and can remain unchanged when porting to QML2.

Hello All, Thanks for the reply. But i have already used XMLListModel at lots of places !! so i know the simplest use of it. I am not a XPath Expert, so i want to understand can i get an array of the RouteLinks tag ?? along with other tags in the xml shown.