QML and Qt Quick

The Designer for Qt5 is still under development ;)

This is true. The closest you can get to re-using widget code is to port your QWidget into QQuickPaintedItem. This will at least allow you to re-use your qpainter drawing code. We are working on making it possible to embed qtquick 2 inside QWidget. This would make it possible to at least partially make use of qt quick in your application. This is will happen in 5.1 earliest.

We really havent tried to integrate the components into qt creator designer yet. First we need to get qt designer to properly support qt quick 2.0. I would recommend not using the designer until it officially supported with desktop components.

You will need to write it by your own

You may put your ListView in another container such as Item, which will be vertically centered in main Container from picture. And don't forget to set inner Item height to -listView.height- and width to parent.width. UPD use listView.contentHeight instead of listView.height. Of maybe you will need their combination. I can't test it now, but it should works.

Use Path, or Canvas elements for a curve. Use a thin Rectangle for a line.

see my reply in http://qt-project.org/forums/viewthread/21485/

The discussion really gave me better insight to the concepts :)

"Developer-Guides":http://qt-project.org/wiki/Developer-Guides under "Particles and Graphics Effects in Qt Quick 2". Download link: "here":http://get.qt.nokia.com/developerguides/qteffects/particles_src.zip.

thks

Thanks, yes importing JS file in every Qml file would mean initialising this JS file every time Qml is instantiated. If that would be the only option, it makes it impossible to access properties of different QML files from one JF function. I can understand this, there might be a problem with same property names in several different files, but you cann still access them via id of the different QMl files, which have to be different. @ ... firstPageId.foo secondPageId.foo ... @ So I still have hope, it is possible to import JS only once and access Qml properties of all QMLs from one function :-) Another option is .pragma library which would NOT access ANY Qml properties. cheers simon

Its a Qt Quick project, so I only have a .project file. As it stands, I don't have any C++ files with this project at the moment

Strange choice. What I do in my project is to give buttons their own MouseAreas, and place the buttons above (using 'z' value) the background (which also has a MouseArea). This way, when user clicks on a button, I can handle the action for this button, while the main MA remains untouched. If user does not click on the button, though, main MA kicks in. Anyway, obviously you know your project better, maybe your solution is better in your case. The two ways to achieve this that I provided should work, after some adjustments.

Thanks! I have allready seen this tutorial, but there is no discription how to install the plugins with qt5 & QTCreator. My main Problem is, that the plugin is not installed ( my be i have to set the plugin dir - but i don't know how )

You may need to consider doing some easier examples at the beginning. Here is what your constructor probably looks like: @ XmlListModel2::XmlListModel2(QDeclarativeItem *parent) : QDeclarativeItem(parent) { test(); // just add this line } @

You need to submit code through "Gerrit":http://wiki.qt-project.org/Main_Page. A more detailed intro is available from "a post by Tucnak":http://qt-project.org/forums/viewthread/22650/.

I can add single elements to the listmodel clicking the single delegate @onClicked: listmodel.app(name, age)@ But I can't select all elements and add them

[quote author="aekam" date="1355393909"] Does this mean that in QtQuick 1.0 whenever there is change in property of multiple elements simulteneoiusly, each and every element calls its paint method individually and more over sequencially, one by one.???[/quote] In QtQuick 1.0 all the visual elements are QGraphicsItems. Whenever you change a property that changes the visual appearance of an item the item usually calls QGraphicsItem::update on itself (see for example QDeclarativeRectangle::setColor()). This tells the graphics view framework that this item is dirty and should be repainted. Which items' paint() functions then get called depends on the viewport update mode of your QGraphicsView/QDeclarativeView. Check out http://qt-project.org/doc/qt-4.8/qgraphicsview.html#ViewportUpdateMode-enum for description of the different modes. When you use QDeclarativeView, the default is BoundingRectViewportUpdate.