QML and Qt Quick

OK, got it. I forgot that JavaScript assignment is not a data, but a reference copy (I'm a complete novice in JavaScript, only 3 days). So I just needed to make assignment on checkbox checked: @ property var circle: ({ x: 256, y: 256, r: 64 }) property var ellipse: ({ x: 256, y: 256, width: 64, height: 128 }) property var figure: ellipse ... CheckBox { id: chkCircle text: "Circle" checked: false onCheckedChanged: figure = checked? circle : ellipse; } ... figure.x = parseFloat(text); @ This concrete problem is solved, but I still need dynamic aliases and full bindings between QML objects and JavaScript objects.

[quote author="Tobias Hunger" date="1367658847"]I am not 100% sure, but I remember reading here that the remote compiler was discontinued. Maybe somebody over at developer.nokia.com knows more?[/quote] I found it: http://www.developer.nokia.com/Community/Wiki/Archived:Qt_SDK_Remote_Compiler The message is clear: The Qt Remote Compiler service has been discontinued. Nokia must not be very interested in people using Linux.

I found the solution... @Rectangle { id: rectangle1 x: 0 y: 0 width: 480 height: 620 color: "#ffffff" //source: "background.png" FocusScope { id: focus_object focus : true property int focus_obj : 1 Image { id: rock x: 5 y: 6 fillMode: Image.PreserveAspectFit smooth: true focus:true source: activeFocus || focus_object.focus_obj == 1 ? "Radiobutton_unselected_highlighted.png" : "Radiobutton_unselected.png" //KeyNavigation.right: pop Keys.onRightPressed: { focus_object.focus_obj = 2 pop.forceActiveFocus() } MouseArea { anchors.fill: parent hoverEnabled: true onEntered: { //parent.source = "Radiobutton_unselected_highlighted.png" //parent.focus = true parent.forceActiveFocus() } onExited: { //parent.source : "Radiobutton_unselected.png" switch(focus_object.focus_obj) { case 1: rock.forceActiveFocus() break case 2: pop.forceActiveFocus() break case 3: classic.forceActiveFocus() break } //parent.focus = false } onClicked:{ rock.forceActiveFocus() focus_object.focus_obj = 1 } } } Image { id: pop x: 160 y: 6 width: 64 height: 64 fillMode: Image.PreserveAspectFit smooth: true source: activeFocus || focus_object.focus_obj == 2 ? "Radiobutton_unselected_highlighted.png" : "Radiobutton_unselected.png" //KeyNavigation.left: rock Keys.onLeftPressed: { rock.forceActiveFocus() focus_object.focus_obj = 1 } //KeyNavigation.right: classic Keys.onRightPressed: { classic.forceActiveFocus() focus_object.focus_obj = 3 } MouseArea { anchors.fill: parent hoverEnabled: true onEntered: { //parent.source = "Radiobutton_unselected_highlighted.png" //parent.focus = true parent.forceActiveFocus() } onExited: { //parent.source = "Radiobutton_unselected.png" switch(focus_object.focus_obj) { case 1: rock.forceActiveFocus() break case 2: pop.forceActiveFocus() break case 3: classic.forceActiveFocus() break } //parent.focus = false } onClicked:{ pop.forceActiveFocus() focus_object.focus_obj = 2 } } } Image { id: classic x: 306 y: 6 width: 64 height: 64 fillMode: Image.PreserveAspectFit smooth: true source : activeFocus || focus_object.focus_obj == 3 ? "Radiobutton_unselected_highlighted.png" : "Radiobutton_unselected.png" //KeyNavigation.left: pop Keys.onLeftPressed: { pop.forceActiveFocus() focus_object.focus_obj = 2 } MouseArea { anchors.fill: parent hoverEnabled: true onEntered: { //if (true == focus) //parent.source = "Radiobutton_unselected_highlighted.png" //classic.foucs = true parent.forceActiveFocus() } onExited: { //parent.source = "Radiobutton_unselected.png" //classic.focus = false switch(focus_object.focus_obj) { case 1: rock.forceActiveFocus() break case 2: pop.forceActiveFocus() break case 3: classic.forceActiveFocus() break } } onClicked:{ classic.forceActiveFocus() focus_object.focus_obj = 3 } }//mouse area }//classic }//Focusscope }@

sorry the code is nothing with dynamic listmodel....>"<

Hi, I'm not sure I fully understand your situation. Could you post a sample code that illustrate your question ?

I run the ApplicationTemplate. There are some warnings and the bq. import QtQuick.Layouts 1.0 is underlined (errors during typeinfo files reading), but it works. My test app also works but I had to remove qmlapplicaionviewer folder and copy the main.cpp and .pro file from the example. When I switch into the design mode QtCreator just dies. But at least in Edit mode it's working. So thank you, thank you, thank you! :) Edit: maybe it doesn't work well.. QtCreator slowed down and often dosn't answer. The MenuBar is underlined (Could not resolve the prototype 'MenuBarPrivate' of 'MenuBar' (M301) ), but it builds the application.

I'm still not further, but I have verified that I can run the mesa demos, e.g. glxgears, although very slow. This means opengl is working correctly, right? Does nobody have an idea why the QtQuick app won't run?

any answer?, please

Yes, all QDeclarative* classes have been renamed to either QQuick* classes or QQml* classes. See this "porting guide":http://qt-project.org/doc/qt-5.0/qtquick/qtquick-porting-qt5.html#c-code for a full list. Qt Quick 1 was a new technology and has many limitations as you've found, so the Qt developers redesigned it to produce Qt Quick 2. Qt Quick 1 is now deprecated. Qt Quick Controls brings QWidget-like components to QML (see http://blog.qt.digia.com/blog/2012/06/06/desktop-components-for-qt-5/ ) It will be released with Qt 5.1, which has its beta is scheduled to be ready in a few more weeks. Unfortunately there's no way to incorporate Qt Quick 2 components directly in the Forms window yet. If you want, you can use the bug report's suggestions as a workaround: Create a custom "QWidget which takes a QQuickView":http://blog.qt.digia.com/blog/2013/02/19/introducing-qwidgetcreatewindowcontainer/ and then "promote":http://qt-project.org/doc/qt-4.8/designer-using-custom-widgets.html#promoting-widgets that widget in your Form.

And you have "QT += qml quick qml-private quick-private" in your .pro? You may also need the v8-private (I think that's module name for qmake's purposes, it might be jsbackend-private I don't remember) but I don't really know.

It's not a typo. I don't understand what conditions cause seg faults when I delete scene nodes. I'm pretty confused in general on how to deal with the new scene graph stuff since there's a separate render thread asynchronously doing stuff. If I have some custom opengl rendering in a QSGNode in the preprocess() call, will I get a seg fault when someone changes the QQuickView to another QML file and parts of my scene graph get deleted?

It will be a bad idea not to, especially now that symbian is pretty much a done deal, and Qt itself is portable enough to cover a wider range of much more lucrative mobile platforms.

Ah, didn't realise it was you, Kit :) Feel free to ping on #qt-qml if you have more questions. I'm sure a doc patch would be appreciated. The current docs as far as I know are "here":http://qt-project.org/doc/qt-5.0/qtqml/qtqml-syntax-objectattributes.html#attached-properties-and-attached-signal-handlers (for using attached properties/handlers in general) and "here":http://qt-project.org/doc/qt-5.0/qtqml/qtqml-cppintegration-definetypes.html#providing-attached-objects-for-data-annotations (for how to implement them in C++).

QStringList is a supported type. The subset of types known as "sequence types" have conversions to JS types - although the conversion is "imperfect" (as documented, it doesn't create properly sparse arrays, as C++ has no analogue). Sequence types include QStringList, QList<QString>, QList<QUrl>, QList<int>, QList<real>.

Thanks I didn't have a clue what a singleton was, but after lookign over that second link in the singleton example it makes a lot of sense, and I think that may be what I will ultimately need.

I don't find the correct way to change the QQuickView default framebuffer to an new explicit one.